DNS timeout issue.
Ok. At work, when someone enters a domain name in the browser, it times out. But when they try that same domain name immediately after, it resolves it fine. When people are VPN'ed into our network, they have to enter the domain name 3 times, and then it resolves.
Ok.
At work, when someone enters a domain name in the browser, it times out. But when they try that same domain name immediately after, it resolves it fine.
When people are VPN'ed into our network, they have to enter the domain name 3 times, and then it resolves.
All of our machines are pointed toward our w2k3 server for DNS, and that server is set up with multiple fowarders.
Any idea what could be causing the problem?
Thanks!
At work, when someone enters a domain name in the browser, it times out. But when they try that same domain name immediately after, it resolves it fine.
When people are VPN'ed into our network, they have to enter the domain name 3 times, and then it resolves.
All of our machines are pointed toward our w2k3 server for DNS, and that server is set up with multiple fowarders.
Any idea what could be causing the problem?
Thanks!
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
People who set up servers and networks are awfully sensitive about unsollicited advice. Two things you can look for or try:
1) a potential cause of this problem occurs when a network card is installed in addition to the satellite receiver adapter or another NIC. If not properly configured, the domain name resolution requests may occur over the network card instead of the satellite receiver adapter or the wrong NIC. Advanced users may wish to use the Route utility provided by Windows to manipulate the network routing tables. In any case what may be happening is that the first time you type in the domain name it "hits" the wrong card.
2) you can do this if the above is not a problem: run the NSLOOKUP program from the command prompt. It tries to attach your computer to the name server listed in PRIMARY DNS Server settings in IP Properties. If you get an error indication at that point you need to verify that the machine you're on has the correct Primary dns ip and that the primary dns server has a correct "NS" record and a correct "A" record that points to itself. If nslookup connects properly then from within the nslookup program you can try resolving names from there. If you can't resolve the names from within the NSLOOKUP program, then the configuration of the dns server is incorrect. If this local DNS server is configured to be a SLAVE then the Master DNS server should be checked to verify that it will supply the new DNS server with the records from that domain.
Take these suggestions with a huge grain of salt because sorting out DNS names can get very messed up.
1) a potential cause of this problem occurs when a network card is installed in addition to the satellite receiver adapter or another NIC. If not properly configured, the domain name resolution requests may occur over the network card instead of the satellite receiver adapter or the wrong NIC. Advanced users may wish to use the Route utility provided by Windows to manipulate the network routing tables. In any case what may be happening is that the first time you type in the domain name it "hits" the wrong card.
2) you can do this if the above is not a problem: run the NSLOOKUP program from the command prompt. It tries to attach your computer to the name server listed in PRIMARY DNS Server settings in IP Properties. If you get an error indication at that point you need to verify that the machine you're on has the correct Primary dns ip and that the primary dns server has a correct "NS" record and a correct "A" record that points to itself. If nslookup connects properly then from within the nslookup program you can try resolving names from there. If you can't resolve the names from within the NSLOOKUP program, then the configuration of the dns server is incorrect. If this local DNS server is configured to be a SLAVE then the Master DNS server should be checked to verify that it will supply the new DNS server with the records from that domain.
Take these suggestions with a huge grain of salt because sorting out DNS names can get very messed up.
