Finding "Name Servers" (not NS records) of domain name
Hello everyone I was dealing with a case where there's a mismatch in nameserver of a domain (nameservers set at registrar) and NS record on the delegated servers. Now NS on delegated servers are good and I am trying to create list of domains using wrong nameservers at registrar. Now as you would be knowing if I do regular dig with ns, it provides NS records. However I was able to find nameservers by digging gTLD root for gTLD based domains. This works for .com/net/org etc but again fails for say .us, .in etc. I was wondering if there's an easy way to do it rather then running script on thousands of domain names again & again digging registry specific nameservers? May be does someone knows/runs any simple server which can be whois'ed for some basic regular output which can be printed. Regular whois output for domain names seems hard to parse. Thanks. -- Anurag Bhatia anuragbhatia.com Linkedin <http://in.linkedin.com/in/anuragbhatia21> | Twitter<https://twitter.com/anurag_bhatia>| Google+ <https://plus.google.com/118280168625121532854>
On Wed, Aug 15, 2012 at 6:10 PM, Anurag Bhatia <me@anuragbhatia.com> wrote:
Hello everyone
I was dealing with a case where there's a mismatch in nameserver of a domain (nameservers set at registrar) and NS record on the delegated servers. Now NS on delegated servers are good and I am trying to create list of domains using wrong nameservers at registrar.
so you tested this with: dig +trace <domain> ? or dig NS domain @TLD.server && matched against dig NS domain @domain-ns-server ? (you didn't give much info to go on here...)
Now as you would be knowing if I do regular dig with ns, it provides NS records. However I was able to find nameservers by digging gTLD root for gTLD based domains. This works for .com/net/org etc but again fails for say .us, .in etc. I was wondering if there's an easy way to do it rather then running script on thousands of domain names again & again digging registry specific nameservers?
+trace
May be does someone knows/runs any simple server which can be whois'ed for some basic regular output which can be printed. Regular whois output for domain names seems hard to parse.
participate in weirds... try to make 'whois' better.
Thanks.
--
Anurag Bhatia anuragbhatia.com
Linkedin <http://in.linkedin.com/in/anuragbhatia21> | Twitter<https://twitter.com/anurag_bhatia>| Google+ <https://plus.google.com/118280168625121532854>
On Wed, Aug 15, 2012 at 06:10:25PM -0400, Anurag Bhatia wrote:
Now as you would be knowing if I do regular dig with ns, it provides NS records. However I was able to find nameservers by digging gTLD root for gTLD based domains. This works for .com/net/org etc but again fails for say .us, .in etc. I was wondering if there's an easy way to do it rather then running script on thousands of domain names again & again digging registry specific nameservers?
I religiously use http://squish.net/dnscheck/ the moment I suspect *any* sort of DNS hinkiness. Verbose, but *damn* if it doesn't hand me the answer practically every time. - Matt
On 17 August 2012 13:14, Matthew Palmer <mpalmer@hezmatt.org> wrote:
On Wed, Aug 15, 2012 at 06:10:25PM -0400, Anurag Bhatia wrote:
Now as you would be knowing if I do regular dig with ns, it provides NS records. However I was able to find nameservers by digging gTLD root for gTLD based domains. This works for .com/net/org etc but again fails for say .us, .in etc. I was wondering if there's an easy way to do it rather then running script on thousands of domain names again & again digging registry specific nameservers?
I religiously use http://squish.net/dnscheck/ the moment I suspect *any* sort of DNS hinkiness. Verbose, but *damn* if it doesn't hand me the answer practically every time.
It doesn't say anything about both of the servers for your domain currently being broken ;) http://nswalk.com/?hostname=hezmatt.org&type=A - Mike
On 8/17/2012 at 10:14 PM Matthew Palmer wrote: | |I religiously use http://squish.net/dnscheck/ the moment I suspect *any* |sort of DNS hinkiness. Verbose, but *damn* if it doesn't hand me the |answer practically every time. Looks like a nice site, but I couldn't get past the captcha. "rn" looks way too much like "m" and vice versa.
----- Original Message -----
From: "Matthew Palmer" <mpalmer@hezmatt.org>
I religiously use http://squish.net/dnscheck/ the moment I suspect *any* sort of DNS hinkiness. Verbose, but *damn* if it doesn't hand me the answer practically every time.
We have three of those on the Tools page at wiki.outages.org: http://wiki.outages.org/index.php/Network_tools They optimize for different things, and have differing levels of verbosity, but they are all useful tools. Submissions of other such useful tools are always welcome (though the wiki is moving to larger hosting this week, and may be in read-only mode if you go there right now. ;-) There's also a collection of system/network status page links there: http://wiki.outages.org/index.php/Main_Page#Outage_Resources I hope to find a few free hours this weekend to clean that page up a bit; link rot is no less prevalent for us than anywhere else. Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274
On Fri, 17 Aug 2012, Matthew Palmer wrote:
I religiously use http://squish.net/dnscheck/ the moment I suspect *any* sort of DNS hinkiness. Verbose, but *damn* if it doesn't hand me the answer practically every time.
http://dnscheck.iis.se It's not as verbose and provides more direct diagnosis and recommendations on what needs fixing. Antonio Querubin e-mail: tony@lavanauts.org xmpp: antonioquerubin@gmail.com
Thanks for helpful replies everyone! I missed to understand Owen's reply here but he was kind and helpful enough to explain me when I met him last week! So simple logic of reading given name from right to left looking for specific pattern (my old nameservers). I didn't realized that reading from right to left digging NS for each zone coming in can pretty much solve the issue. On Mon, Aug 20, 2012 at 6:08 PM, Antonio Querubin <tony@lavanauts.org>wrote:
On Fri, 17 Aug 2012, Matthew Palmer wrote:
I religiously use http://squish.net/dnscheck/ the moment I suspect *any*
sort of DNS hinkiness. Verbose, but *damn* if it doesn't hand me the answer practically every time.
It's not as verbose and provides more direct diagnosis and recommendations on what needs fixing.
Antonio Querubin e-mail: tony@lavanauts.org xmpp: antonioquerubin@gmail.com
-- Anurag Bhatia anuragbhatia.com Linkedin <http://in.linkedin.com/in/anuragbhatia21> | Twitter<https://twitter.com/anurag_bhatia>| Google+ <https://plus.google.com/118280168625121532854>
participants (7)
-
Antonio Querubin -
Anurag Bhatia -
Christopher Morrow -
Jay Ashworth -
Matthew Palmer -
Mike Jones -
Mike.