The DNS server is not responding to clients. What I suggest to troubleshoot it is to try to narrow down the issue when it occurs. One computer on the network (and domain) can ping the server 25% of the time, also when I try to ping it's own hostname it also does not work. timeout was 2 seconds. http://sevevb.com/dns-server/dns-server-windows-server-2008-not-working.html
Note that this isn’t a problem for most Windows Server 2008 R2 member servers. The computer that cannot ping the server is setup to use the DNS server running on the server only (secondary dns points to nothing) and it will resolve the hostname of MS never ceases to amaze me. And note if anyone asks, my firewall and AV were not running at the time of the test. ============================== C:\>nslookup Default Server: vnsc-bak.sys.gtei.net Address: 126.96.36.199 > www.microsoft.com Server: vnsc-bak.sys.gtei.net Address: 188.8.131.52
Robert Hines - Thursday, January 19, 2012 11:17:31 AM Man this has been wrecking my head and as really put my work back. Just as it is possible that your local PC has network info (including DNS server IP Addresses), it is also possible that your router has bad info. However another computer that is on the domain can ping it fine, and another computer on the network but not domain can ping fine as well. Thus, to carry out this test, you would have to have a network diagram or, like many network admins do, just have the IP address of a common host memorized.
OWScott - Sunday, November 1, 2009 6:19:42 PM Thank you so much. For more information, see Troubleshooting DNS Clients Cause: The DNS server does not resolve names for computers or services outside your immediate network, for example, the names of computers or services that Either use the MrFixIt link, or follow the steps to do it manually. Troubleshooting Dns Issues Windows Server 2008 R2 More specifics here (scroll down to that section): The DNS Client Side Resolver algorithm.
i.e. Ace Fekay MVP, MCT, MCITP Enterprise Administrator, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft nslookup -debug www.microsoft.com. 192.168.0.50 Cheers, Lain Thursday, March 22, 2012 1:08 PM Reply | Quote 0 Sign in to vote Hi Lain Let me just say that I really appreciate what Now the DNS server works and I have made no other changes.
Recursion is used in most DNS configurations to resolve names that are not located within the configured DNS domain name that is used by the DNS servers and clients. Dns Problem Windows 7 So is it that it DOES get a response, but not the response it wanted?? Ace Fekay MVP, MCT, MCITP Enterprise Administrator, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft A cache of namespace information is amassed on this DNS server, and the need for recursion is decreased.Instead of using conditional forwarders, some admins choose to implement stub zones on the
try to disable IPV6 on all servers involved. https://community.spiceworks.com/topic/349243-windows-server-2008-r2-dns-issues In terms of running a test, launch nslookup again while on the server and set the server as you did before (to 192.168.0.50 - and this time it should come back Troubleshoot Dns Server Not Responding Note If you disable recursion on the DNS server, you will not be able to use forwarders on the same server. Dns Server Not Resolving External Names Quick Rant: I don't understand how the latest service pack should make any difference.
Default Server: [184.108.40.206] Address: 220.127.116.11 Not sure what that means as I have little experience with nslookup. check over here He holds several certifications including VCP5, VCAP-DCA, CCIE #9369, and has been awarded the VMware vExpert award 5 years running. If the DNS server is located on another network and is reachable only through an intermediate host (such as a packet-filtering router or proxy server), the DNS server might use a Delivered Fridays Subscribe Latest From Tech Pro Research System monitoring policy Hiring kit: Microsoft Power BI developer Research: Automation and the future of IT jobs Interview questions: iOS developer Services About Dns Troubleshooting Tools
I have completely disabled the windows firewall and there are no firewall rules on the router except for the RDP port 3389. gave a result. If so, the problem could be related to a router failure or a DHCP configuration error. 4: See whether the DNS server is performing load balancing Organizations hosting high demand Web his comment is here EDns is a relatively new DNS protocol extension that is still coming of age.
Brian - Friday, October 16, 2009 6:00:03 AM I was just beating my head against the desktop. Computerworld Article 2545365 Networking Fix Your Dns Problems This at least will clear up that one cosmetic issue. Server: UnKnown Address: ::1 DNS request timed out.
Thanx Randy Baker - Wednesday, September 30, 2009 1:37:24 PM Wow thanks a lot. I agree with Ace in that you should re-enable IPv6. How do I fix this... Dns Server Failure Response If you do not have other DNS servers on your network but you still need to resolve Internet DNS names, you can use the default root hints file, which includes a
Try using the nslookup command to test whether the server can respond to DNS clients. Yes No Do you like the page design? And below shows using DIG with the same results. ============================== C:\DIG>dig @18.104.22.168 www.microsoft.com ; <<>> DiG 9.8.0 <<>> @22.214.171.124 www.microsoft.com ; (1 server found) ;; global options: +cmd ;; connection timed weblink Tip explains how to get manually created replication connection objects in an Active Directory Forest...
I would actually use 126.96.36.199 and 188.8.131.52 and forget about those two. See more RELATED PROJECTS Server refresh Hardware at head office 5 years old, Data usage has grown and backup system no longer sufficient. You should verify that your DNS suffix is correct. 6.Make sure that your DNS settings are configured to pull the DNS IP from the DHCP server It is likely that you Edited by Ace Fekay [MCT]MVP Thursday, March 22, 2012 3:55 AM Thursday, March 22, 2012 3:55 AM Reply | Quote 0 Sign in to vote Hi Lian Both the telnet and
All other DNS settings are default after adding the DNS role. I thought they might have been private iiNet servers, so I tested from home and that checked out (as I'm with iiNet), but they also resolve from work, and we're with ISP's perhaps? I can ping both the gateway and 184.108.40.206.
timeout was 2 seconds. *** Request to UnKnown timed-out Thanks Wednesday, March 21, 2012 4:18 PM Reply | Quote 0 Sign in to vote I just tested 220.127.116.11 and 18.104.22.168. Solution: Check whether server root hints are valid. Do you have another firewall or router to swap out? . Solution: Test for connectivity to the root servers.
Next, try pinging by computer name and by the server's fully qualified domain name. The most trusted on the planet by IT Pros Which is your preferred network administration tool? I've spent half a day trying to get DNS to work before I found your article!!! Funny thing is, some of the articles I read said "use Hotfix xxxxx"...
Does anyone have any ideas on how to fix this? We were getting time outs with DNS Guard and eDNS implemented concurrently.