Replaced a domain controller that was also the primary DNS server.
Now when I NSlookup from a workstation OR from the DC itself, nslookup resolves the FQDN exactly 50% of the time (every other query)
To wit...:
C:\>nslookup
Default Server: ourdomain.k12.oh.us
Address: 10.5.41.11
> exit
C:\>nslookup
Default Server: crldc02.ourdomain.k12.oh.us
Address: 10.5.41.11
> exit
C:\>nslookup
Default Server: ourdomain.k12.oh.us
Address: 10.5.41.11
> exit
C:\>nslookup
Default Server: crldc02.ourdomain.k12.oh.us
Address: 10.5.41.11
> exit
C:\>nslookup
Default Server: ourdomain.k12.oh.us
Address: 10.5.41.11
> exit
C:\>nslookup
Default Server: crldc02.ourdomain.k12.oh.us
Address: 10.5.41.11
> exit
C:\>nslookup
Default Server: ourdomain.k12.oh.us
Address: 10.5.41.11
> exit
C:\>nslookup
Default Server: crldc02.ourdomain.k12.oh.us
Address: 10.5.41.11
It is ALWAYS finding the address, but it is not resolving to the server but 50% of the time.
When I set the secondary DNS server as primary on the workstation, it gets it 100% of the time...
This does not seem to be a workstation configuration issue, since the same behavior exhibits itself on the Domain Controller as well....
I have cleared DNS cache on workstation and server.
Thanks for your insight, experts!
If so, you need to update your DHCP scope options to remove the old server and add the new one for DHCP clients. Servers that have statically assigned IP information will need to be updated manually.