DNS Issue
I have a 2003 Domain Controller holding FSMO roles. I have another 2003 Domain Controller. DHCPs DNS settings refers to both. When I reboot the 2003/DC/FSMO server, I completely lose DNS until it comes back up. The 2nd 2003DC servers DNS looks fine but why isn't it used?
Joshua Grantom
your computers must have the 2nd DC as there secondary DNS for it to be used when the 1st one isn't available. This could be set in DHCP server option 6 or under scope options. It depends on your setup.
ASKER
This is how I am setup....but it still isnt working...
what are the primary and secondary dns servers set to on the 2nd DC?
What I want to know is what are the forwarders set to in DNS on the 2nd DC?
That's what I asked in my last post?
Sorry, I would have read that you were asking what the DNS was set to on the NIC without "forwarders" in the mix.
Use nslookup to make sure the second DC is actually listening and doesn't have port 53 blocked by a firewall or something like that. Try looking up the name of a machine inside your network and the name of a website:
nslookup <internal_machine_name> <second_dc_ip_address>
nslookup www.google.com <second_dc_ip_address>
If neither command works, the second DC may be firewalled or not listening with the correct adapter. If the first works but the second doesn't, the forwarders on the second DC may not be configured correctly.
nslookup <internal_machine_name> <second_dc_ip_address>
nslookup www.google.com <second_dc_ip_address>
If neither command works, the second DC may be firewalled or not listening with the correct adapter. If the first works but the second doesn't, the forwarders on the second DC may not be configured correctly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So technically dipersp and I did ask the correct question which would have solved your problem.
We asked what your Secondary DC (2003/DC) DNS settings were. You just stated that your DNS settings were not correct and did not point back to the localhost on (2003/DNS) which caused logons to fail. We were on the right track.
We asked what your Secondary DC (2003/DC) DNS settings were. You just stated that your DNS settings were not correct and did not point back to the localhost on (2003/DNS) which caused logons to fail. We were on the right track.
ASKER
All the answers supplied were great but didn't meet my situation because, in the end my question was flawed. Imade a statement in my question that was not true, throwing everyone off. I not looking for points. I just don't know how to eliminate the question.