DNS issue/question

[ltwally]

When Windows detects a dead DNS server it seems to mark it as "dirty" and stops even trying to use it. This is all well and good, since you don't want your machines waiting for a DNS server to time-out before trying the next DNS server in line every time you need to do a lookup.

Does anyone know of a way to "de-list" that DNS server from this "dirty" / "dead" list, and get Windows using that DNS server again...? A way without re-initializing the network connection (which fixes the issue, but isn't always convenient)...?

Thanks

 

[chev65]

When Windows detects a dead DNS server it seems to mark it as "dirty" and stops even trying to use it. This is all well and good, since you don't want your machines waiting for a DNS server to time-out before trying the next DNS server in line every time you need to do a lookup.

Does anyone know of a way to "de-list" that DNS server from this "dirty" / "dead" list, and get Windows using that DNS server again...? A way without re-initializing the network connection (which fixes the issue, but isn't always convenient)...?

Thanks

The page in the link below covers most of the useful IP commands and what they do when you send them. To flush the DNS > ipconfig /flushdns typed into a command prompt.

ipconfig - Windows Command Line Utility

 

[ltwally]

ipconfig /flushdns does not re-enable a DNS server that has been marked as "down".

The problem isn't an incorrect DNS cache, but that Windows has stopped using the primary DNS server due to it not being available for a time. When it comes back online, Windows has no method of realizing this (at least not in a timely manner) and resuming use of that DNS server.

Resetting the NIC or rebooting does do the trick, but both solutions obviously disrupt the network connection. I was hoping for a more elegant solution.

Thanks