Hey Greg, just curious are you seeing any issues with rr.com up there? we have an office in Tampa and since last week are getting really weird connectivity coming out of roadrunner, and today we couldnt even email rr.com from down here I was getting no route to host ... we have 3 connections with this client, a T1 from Paetec, a Cable from Comcast, and a 10mb fiber from Host.Net and all are having weird routing/locating issues with roadrunner ...
I dont know if that might shed some light on your situation either.. -----Original Message----- From: Greg Sweers [mailto:[email protected]] Sent: Monday, November 28, 2011 5:55 PM To: NT System Admin Issues Subject: RE: 2008 R2 DNS strangeness Thx Ben. I will get to test some more in the morning. I had to move them all to another DNS server in the office for some major projects today and they were flipping out. Tomorrow most of them are out so I will let you know. Thx Greg Sweers CEO ACTS360.com P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Monday, November 28, 2011 10:35 AM To: NT System Admin Issues Subject: Re: 2008 R2 DNS strangeness On Mon, Nov 28, 2011 at 9:51 AM, Greg Sweers <[email protected]> wrote: > Sorry should have been more clear. The NSlookup is to the internal DC > server. When you try and query it comes up with service failure or > timeout. Right, but the question is, do you get different behaviors depending on what name you query. If my DC/DNS server is 192.0.2.10, and my AD domain is <example.net.>, I would compare: nslookup example.net. 192.0.2.10 with nslookup google.com. 192.0.2.10 I'd also check a site unlikely to be cached, such as: nslookup purple.com. 192.0.2.10 I'd also run a query against an external resolver: nslookup google.com. 8.8.8.8 I'd also avoid NSLOOKUP and use DIG (you can get it from the ISC BIND distribution). NSLOOKUP is historically prone to giving bad diagnostics. I don't know if Microsoft has fixed their version, but DIG gives better information than NSLOOKUP even when both are working correctly. Example syntax: dig example.net. @192.0.2.10 > When you try and query it comes up with service failure or timeout. Be aware that SERVFAIL is an actual DNS result code from a nameserver, while a timeout is NSLOOKUP getting tired of waiting for the nameserver to respond. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
