Hugo Mills wrote:
> $ dig NS baiterpowerkites.co.uk
> [...]
> ;; ANSWER SECTION:
> baiterpowerkites.co.uk. 86369 IN NS ns2.tsohost.co.uk.
> baiterpowerkites.co.uk. 86369 IN NS ns1.tsohost.co.uk.
Just to nit-pick, this is not how to find out the DNS servers hosting a
domain. These NS records are served by one of the authoritative
nameservers, and no real use is made of the NS records apart from in
replication configurations (afaik). You see, it's working out ONE of the
servers it should be able to ask, and then asks that server what it
thinks the other servers are. Actual DNS lookup uses the list from the
parent domain instead. It's quite easy for there to be a
misconfiguration so that the lists don't match.
To see the list of nameservers that are actually used in lookups, you
need to ask the .uk nameservers. (the .co bit is run by the .uk people
so there is no need for separate nameservers for .co.uk).
To do this you can use 'dig +trace baiterpowerkites.co.uk' which tells
you which nameservers it has been given at each level as it performs a
real lookup of the domain. You can also use 'whois
baiterpowerkites.co.uk' which a lot of people find easier to use, but
not every TLD supports WHOIS.
Dan
