The clients on the network have static IP addresses and have DNS servers configured using the addresses of the...
two servers: 192.168.0.11 and 12. Both the DNS servers have been configured to use DNS forwarders (the ones my ISP have). Both the servers have loopback addresses in DNS servers list. Every thing works fine (ADS, Internet access, etc.) till the first server goes down.
I tried changing the operations master from the first server to the second server, made both the servers Global Catalog servers and added an additional IP address (192.168.0.1) to the second server. Still, Internet name resolution fails when the first server is down.
Then I came to notice that the second server's default server is one of my ISP's servers (using NSlookup). The first server's DNS server address is still 127.0.0.1. So I changed the second server's default server to 127.0.0.1, thinking I could fix the problem.
When I run NSlookup on client machines, it shows the first server as the default server, but when the first server is down, I can resolve Internet hosts using the second server using NSlookup, the second server as the default server and the command "server 192.168.0.1," but I can't resolve it using other programs.
Please help me fix the problem.
The gateway entry on the clients is the network interface card (192.168.0.11). The first server is set to forward requests that are not found in its records to the Internet (i.e., the ISP's DNS). The only entry in the DNS setup on the primary server would be itself. The loopback address (127.0.0.1, also known as "Home") is a red herring in this case and not appropriate in either listing. The second server should have its DNS entries listing the first server and on the ISP servers. Then if the first server is not available, the clients still get forwarded. Note that when you switch the ISP cable to the first server because the second has failed, you will have to update the gateway entry on the clients.
My usual recommendation is to use a firewall box as the ISP connector, in which case the gateway doesn't change.
Dig Deeper on Windows Server Troubleshooting
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.