Microsoft
Software
Hardware
Network
Question : DNS Fails to resolve URLs, NSLOOKUP times out
This morning it seems DNS has taken a nosedive. No changes have been made on my end, and my set-up has for for two years with no problems. This morning however, no one is able to browse the Internet.
www.google.com
will return address invalid, however, 74.125.100.27 will pull up the google homepage. NSLOOKUP times out for any external IP address, works fine for internal FQDN. I am able to ping by name/ip any internal address, but only by IP to anything on the net. I called my isp they are having no issues with their DNS servers. I tried changing the IP of the forwarders I was using but I get the same results as above. I am not sure where to go from here as far as trouble shooting. One strange thing is that Netdiag runs and returns pass on one of the DC, on the other one however, it keeps returning netdiag is not a recognized command etc... Netdiag is installed on that machine I can see it under c -> program files -> resource kit -> netdiag.exe. When I try to tun it from that location I get an error that says The proceedure entry point DnsGetPrimaryDomainName_UT
F8 could not be located in the dynamic link library DNSAPI.dll. Any guidence on resolving the above problems would be greatly appreciated.
Answer : DNS Fails to resolve URLs, NSLOOKUP times out
I would look at your router and ISP.
Random Solutions
more then one ip
Unable to browse resources in a trusted domain from XP and 2003 clients
Home network Windows 98 to XP
How to configure subnetting on vmware
Exchange 2003 Front-End/Back-End Licensing Scenario
MX records - secondary mailhost - how long to switch over
I need change SMTP configuration from my ISP to My SMTP
Help in setting up or re-working Home Network between a New Vista Machine and an Old XP Machine and to Share One Printer (From XP) - Re-Submittal Question
How do I setup DNS so that it works internally for remote VPN users using RRAS to connect?
Can I delete all tmp files safely?