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.
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.
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.
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:
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.
