janhoedt
asked on
Windows 2008R2 DNS on domain, 2nd DNS doesn't take over (?)
Hi,
I have a domain with 2 DNS servers. I rebooted 1 of both, but meanwhile, the 2nd doesn't take over (?).
When I do a nslookup, it just timesout on default dns while there is a second one, which it just doesn't query(?)
Note: dns settings of dns servers theirselves is 127.0.0.1 as default, then the ip address of the second one as secondary. That's right ... right?
But however, it shouldn't matter in this case.
Why my second dns isn't queried ...?
J.
I have a domain with 2 DNS servers. I rebooted 1 of both, but meanwhile, the 2nd doesn't take over (?).
When I do a nslookup, it just timesout on default dns while there is a second one, which it just doesn't query(?)
Note: dns settings of dns servers theirselves is 127.0.0.1 as default, then the ip address of the second one as secondary. That's right ... right?
But however, it shouldn't matter in this case.
Why my second dns isn't queried ...?
J.
Do your clients point to both DCs?
Do you have both DNS servers listed in your DHCP config? If not, the clients won't know to look for the second one.
Make sure your clients point to both of them (the Internal DNS servers) and not to another outside DNS server.
ASKER
???
With all do respect, I didn't see an update which is worth answering ....
With all do respect, I didn't see an update which is worth answering ....
Meaning you've already checked these things or have no idea what we are talking about?
If you do an ipconfig -all from a client, does it list one or both DNS servers? If it is only listing one, then you might only have one DNS server being pushed out by your DHCP server. It doesn't matter if your DNS servers point to each other if your clients are only looking at your primary.
If you do an ipconfig -all from a client, does it list one or both DNS servers? If it is only listing one, then you might only have one DNS server being pushed out by your DHCP server. It doesn't matter if your DNS servers point to each other if your clients are only looking at your primary.
You mentioned that nslookup doesn't query the second server. This is normal behavior. Nslookup only queries one server - the preferred server. If you want it to use the alternate server (or a completely different one), you have to explicitly tell it to do so. In interactive mode, use the server <address> command to do so. In non-interactive mode, run nslookup <host> <server> to specify <server> as the one to use to look up the record for <host>.
ASKER
Ok, but how can I test redundancy. My default DNS is down and my clients don't resolve DNS, how to check they go for second & third DNS in line/config?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That's where I was looking for!
Glad to help.