mydomain.com 123.45.67.89
. 98.76.54.32
When it's set up this way, anytime they try to access a site on the
mydomain.com domain, it will use the 123.45.67.89 DNS server. Everything
else it uses the 98.76.54.32 one. If this secondary server goes down, they
won't be able to look up any URL's outside of mydomain.com. You need to
set them up like this:
mydomain.com 123.45.67.89
. 123.45.67.89
. 98.76.54.32
Tim
At 04:32 PM 5/26/99 , Matt Hadlock wrote:
>Hello all, I have a very bizarre problem.
>
>Up until about 5 days ago all of my customers with Mac OS 7.5 using MacTCP
>have been working flawlessly. Now they can dial in just fine but they cannot
>browse to anything beyond our local subnet. ALL other platforms are working
>perfectly including Macs using Open Transport. I have not changed any
>configuration for the last 2 months the problem is the same for both my
>PM25r and my PM3 RAS servers. Has anyone ever seen anything like this?
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>