Windows 2000 Client DNS Problem 1

[mixmastermike]

We are currently running a 2k AS to serve a computer lab, which has about 20 2k pro clients. However, the DNS server is located off site, and we also have to add our server's DNS to the client's list, so we can apply Group Policies.

The addresses for the offsite DNS are:
172.22.2.10
172.22.2.11

My server's IP is
10.71.26.52

Currently, on the client's list, it goes in the order:
172.22.2.10
10.71.26.52
172.22.2.11

However, oftentimes the DNS resolution fails to work on the client side. All we have to do to fix this, is to go to the network properties and move one DNS down the list, and then back up (doing absolutely nothing). We continue to click 'ok' and everything ends up working...

This is really quite a nuisance as we have to log a user out, and relogin as an admin to fix the internet.

 

[FilthPig]

Set up your local DNS server as the only DNS server the clients use. On your local DNS set up your offsite DNS servers as forwarders. In the DNS console, right-click the server, choose properties. Click on the forwarders tab, check enable forwarders enter the IPs of the external DNS servers and add them. That will cause lookup requests for zones that are not locally hosted get passed on to the servers specified as forwarders. Marc Creviere

 

[GlenJohnson]

FilthPig is right. I learned this trick a while back and have all my network set up this way. Makes the name resolution much faster. What happens in this setup is when a pc tries to go to

http://www.whoever.com,

if the onsite server has the name in cache, it takes it there. If it doesn't have it in cache, it goes to the offsite server, gets it there, then places it in cache so the next time the user tries to go there, it's much faster. If you have offsites dns server listed on the clients, if it has to go the offsite dns server, it automatically upgrades that to the primary, so your name resolution is always going to be slower because then it's bypassing the local dns server, and may cause timeouts. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"I grow old learning something new everyday".
Solon (640-558 BC); Greek legislator.

 

[mixmastermike]

I just tried that. When I try to change the forwarder, it was greyed out, saying that my server was root. Thanks.

 

[GlenJohnson]

I don't know about the forwarder, but FilthPig was right about how to set the dns settings in TCP/IP properties on the locals and servers. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"I grow old learning something new everyday".
Solon (640-558 BC); Greek legislator.

 

[FilthPig]

Ok, delete the "." zone from your forward lookup zones. Marc Creviere

 

[GlenJohnson]

I'm glad I didn't set up the dns on our servers. I just try and tweak them. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"I grow old learning something new everyday".
Solon (640-558 BC); Greek legislator.

 

[mixmastermike]

Thanks a lot guys, i appreciate it. I'll give it a try tomorrow, and we'll see how it goes! Thanks again