The symptoms are that, for some minutes, any call to nslookup fails with error messages such as this one: C:\> nslookup –vc dc.domain.loc Server: UnKnown Address: 192.168.12.11 *** dc.domain.loc wurde von The answer to you question is there is nothing obvious blocking communication between this server and DNS. If you start from a cold boot everything is fine for a while. Who handles the firewalls?

Feds Walk Into A Building, Demand Everyone's Fingerprints To Open Phones [Security] by Itguy2016286. The DNS settings are correct on the server and no other servers are having problems. What could be the issue? Compare this config with other servers. 2) Are you able to reach them without any issues? 3) IS this server in site which doesnt have DCassociated with that site?

Less Common Tasks12.8. Browse other questions tagged domain-name-system windows-server-2008-r2 nslookup or ask your own question. This causes nslookup to print out the query messages it sent, as well as printing out when the query timed out and was retransmitted:

% nslookup -d2 ------------ SendRequest( ), len What maybe occuring with truncation, is due to EDNS0 not enabled, and possibly TCP is disabled, but that would be a first for me to hear that one, because if UDP

Other servers are not exhibiting the same problems. conf file for lookups so I dont think looking at nsswitch.conf will help. What could be the issue? THis is evident in zone data responses that have a larger than 512 bytes in the answer.

This further suggests that the problem isn't in the DC for this domain. If you use nslookup to look up a type of data for a domain name, and the domain name exists, but no data of the type you're looking for exists, you'll This is proven by the NSLookup and in fact why I used NSLookup -- to prove connectivity to the DNS server. Authoritative answers can be found from: (root) nameserver = NS.NIC.DDN.MIL (root) nameserver = B.ROOT-SERVERS.NET (root) nameserver = E.ROOT-SERVERS.NET (root) nameserver = D.ROOT-SERVERS.NET (root) nameserver = F.ROOT-SERVERS.NET (root) nameserver = C.ROOT-SERVERS.NET (root)

Without the debugging output, you won't see anything printed to your screen for 75 seconds; it'll look as if nslookup has hung. 11.7.7 Unspecified Error You can run into a rather zairah replied Jun 17, 2008 check ur /etc/nsswitch.conf. If it is losing connectivity intermittently, there could be an issue with network? We had one of our Exchange 2010 servers running Windows 2008 R2 lose DNS resolution capability entirely, even with redundant DNS servers configured.

What causes a 20% difference in fuel economy between winter and summer What does "Rx accounts" mean? You are correct in that it cannot find the SRV records but the issue here is why it can't find them. nslookup doesn't necessarily look up anything when it starts up. It's only when you try to look something up that you find out there is no name server responding.

What i can figure out is, server is unable to contact \\domain\sysvol whnever this is happening, hence policies are not applying properly. If you request A records for a Domain which has a lot of A records it will get the Truncated/Error message regardless of which DNS server you select. The GPO error message indicated a possible DNS problem and further investigation did show there was a problem.When you use NSLookup and set debug on and look up the domain you In your caseits AD integrated DNS.

Hard to compute real numbers more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / In other words, nslookup couldn't find the name for 192.249.249.3, its name server host. In other words, nslookup couldn't map 192.249.249.3, the address of its name server, to a domain name. We had a second nameserver directive in resolv.conf, though, and the second server did respond.

Was EDNS0 ever disabled on the domain controllers or any machine? Looking Up the Right Data This isn't really a problem per se, but it can be awfully confusing. But didn't we just say that nslookup doesn't look up anything when it starts up? All product names are trademarks of their respective companies.

The second one is another domain. After all, there is a name server there to say the address doesn't exist. The third possibility is both the above. More on EDNS0: What is EDNS0? (Extension mechanisms for DNS) http://msmvps.com/blogs/acefekay/archive/2010/10/11/edns0-extension-mechanisms-for-dns.aspx Ace Ace Fekay MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise

If you see that the address of your server is 0.0.0.0, nslookup grabbed the system's host name (what the hostname command returns) for the server field and gave you its prompt. You'll see it if you create too many NS records for a zone, so don't create too many. (Advice like this makes you wonder why you bought this book, right?) How Roger Monday, December 19, 2011 10:04 PM Reply | Quote Answers 0 Sign in to vote It seems that EDNS is blocked so while that could cause a problem, it doesn't Only then does the "default servers are not available" message make sense. 12.7.4.

So for now, the issue can be closed. I will try and track down the right group but it will take a while. All rights reserved. Edited by Ace Fekay [MCT]MVP Wednesday, December 21, 2011 10:13 PM Wednesday, December 21, 2011 10:12 PM Reply | Quote 0 Sign in to vote Excellent Ace.

It can also talk to other DNS servers if you explicitly select them in NSLookup. Not an IP to be given to be use as a server IP address Charles Grady Senior Solaris Unix Systems Administrator (913) 375-2357 Top Best Answer 0 Mark this reply We'll cover a few odd problems here. 11.7.1 Looking Up the Right Data This isn't really a problem, per se , but it can be awfully confusing. The site has its own DCs although again I am pretty sure this isn't a DC problem.

At 4.9.3, support for inverse queries was dropped, which broke old nslookup s. In this /etc/resolv.conf is defined and name servers are pingable. EDNS0 allows larger than UDP 512 bytes to return for a query. Restarting the DNS Client service did not resolve the issue.

If you read my first line, you could see "trying to figure out why this server is losing communications with DC's. sandeep sudeep replied Jun 20, 2008 Zairah, I verified it now. All rights reserved. Log In E-mail or User ID Password Keep me signed in Recover Password Create an Account Blogs Discussions CHOOSE A TOPIC Business RogerRoger Marked as answer by Rick TanModerator Thursday, January 05, 2012 5:32 AM Wednesday, January 04, 2012 3:55 PM Reply | Quote All replies 0 Sign in to vote Hi, Basically

One otherpossibility I believe is EDNS0 is limited between the client and DNS server.

One reason could be that DNS service is not running on these DNS servers. The NSLookup debug showed that it was because it could not even enumerate the A records. I look at this way, please correct me if im wrong, after 90 minutes or so , say after sometime, server is losing connectivity with DNS/DC's and policies are not applying For example, I could retrieve the TXT and AAAA record for the domain. Administrator - Server Support Tuesday, December 20, 2011 12:43 PM Reply | Quote 0 Sign...

JFK to New Jersey on a student's budget A penny saved is a penny Thesis reviewer requests update to literature review to incorporate last four years of research. It generally answers only with decreased TTLs when providing answers based on non-authoritative, cached data obtained from other DNS servers during recursive lookups. Best regards, Susie Marked as answer by TakeIX Monday, November 18, 2013 2:47 PM Thursday, November 14, 2013 5:29 AM Reply | Quote Moderator 1 Sign in to vote Ace Fekay...

I know now that you have it configured correctly(assuming)after my recommendations, but I'm just hoping now that this can easily be fixed. Marco J.L. Ace Fekay MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP - Directory Services Technical Blogs Add a PTR record3. Note : To show the server name a... This also benefits others if they were to come across this thread if they hav...