Fubyou
asked on
DNS update problem
Quite some time now our DNS servers have not been updating there records properly. We have a 500 client network with 2 domain controller, (primary and secondary). We noticed this when trying to use remote desktop connecting via computer name and was connected to a different computer than what we had typed in. Where do i start looking to solve this problem specifically.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
why is lmhosts and wins a problem?
Hello,
You are probably addressing that question towards chadder.
I don't know why they would be a problem
Besides that question
How did everything go for you...whats the latest ?
You are probably addressing that question towards chadder.
I don't know why they would be a problem
Besides that question
How did everything go for you...whats the latest ?
Sorry, couldn't respond sooner...busy with Sar-Ox compliance.
There is no problem with LMHosts or WINS, but if they are enabled and they have an invalid entry your systems could resolve a name improperly. For example, let's say you have a computer named server and it has an IP address of 192.168.1.1. In DNS it should register as 192.168.1.1, but if a client has a hosts file that says server=192.168.1.2 then the name could resolve to 192.168.1.2 instead of 192.168.1.1. Same with WINS if it has a static mapping on the WINS server.
The idea is to eliminate any possible conflicts, not to imply that WINS or HOSTS has a problem. I will make the comment though that you should try to use only one name resolution system on your network unless you have extenuating circumstances.
Could you elaborate on the DNS server setup. Specifically, do you have two or more DNS servers that are not sync'ing or is it simply that clients are not updating their IP addresses in DNS?
You can also try to force DNS update by using the following command on your systems that are not updating their records:
ipconfig /registerdns
There is no problem with LMHosts or WINS, but if they are enabled and they have an invalid entry your systems could resolve a name improperly. For example, let's say you have a computer named server and it has an IP address of 192.168.1.1. In DNS it should register as 192.168.1.1, but if a client has a hosts file that says server=192.168.1.2 then the name could resolve to 192.168.1.2 instead of 192.168.1.1. Same with WINS if it has a static mapping on the WINS server.
The idea is to eliminate any possible conflicts, not to imply that WINS or HOSTS has a problem. I will make the comment though that you should try to use only one name resolution system on your network unless you have extenuating circumstances.
Could you elaborate on the DNS server setup. Specifically, do you have two or more DNS servers that are not sync'ing or is it simply that clients are not updating their IP addresses in DNS?
You can also try to force DNS update by using the following command on your systems that are not updating their records:
ipconfig /registerdns
this will get rid of all the old DNS records stored localy. also, you can use the same command with a /registerDNS on the computer you are trying to connect to. (for troubleshooting)
BTW, more commands that could be useful: nslookup
will let you query DNS on the Fly, be shure to use the fully qualified name if your not on a domain or dont have DNS suffix supplyed via DHCP.