|
How to check ROOT DNS servers for authoritative DNS servers. |
|
|
|
|
Written by Eric
|
|
Saturday, 14 February 2009 06:42 |
|
You may need to confirm what a domains DNS servers are because the whois information provided on the domain is innacurate.
The method of finding the real DNS servers used on the public ROOT DNS servers is simple.
First run the command dig without passing anything to it. You will get output similar to the following. ;; ANSWER SECTION: . 42295 IN NS C.ROOT-SERVERS.NET. . 42295 IN NS D.ROOT-SERVERS.NET. . 42295 IN NS J.ROOT-SERVERS.NET. . 42295 IN NS A.ROOT-SERVERS.NET. . 42295 IN NS I.ROOT-SERVERS.NET. . 42295 IN NS K.ROOT-SERVERS.NET. . 42295 IN NS E.ROOT-SERVERS.NET. . 42295 IN NS B.ROOT-SERVERS.NET. . 42295 IN NS M.ROOT-SERVERS.NET. . 42295 IN NS H.ROOT-SERVERS.NET. . 42295 IN NS L.ROOT-SERVERS.NET. . 42295 IN NS F.ROOT-SERVERS.NET. . 42295 IN NS G.ROOT-SERVERS.NET.
Now we can dig these ROOT servers to get the tld ROOT DNS servers for the domain you are checking by doing a dig on one of these DNS servers like the following example.
dig @J.ROOT-SERVERS.NET uhgbug.com
The output gives you the .net tld ROOT DNS servers. This is example output. ;; AUTHORITY SECTION: com. 172800 IN NS M.GTLD-SERVERS.NET. com. 172800 IN NS A.GTLD-SERVERS.NET. com. 172800 IN NS B.GTLD-SERVERS.NET. com. 172800 IN NS C.GTLD-SERVERS.NET. com. 172800 IN NS D.GTLD-SERVERS.NET. com. 172800 IN NS E.GTLD-SERVERS.NET. com. 172800 IN NS F.GTLD-SERVERS.NET. com. 172800 IN NS G.GTLD-SERVERS.NET. com. 172800 IN NS H.GTLD-SERVERS.NET. com. 172800 IN NS I.GTLD-SERVERS.NET. com. 172800 IN NS J.GTLD-SERVERS.NET. com. 172800 IN NS K.GTLD-SERVERS.NET. com. 172800 IN NS L.GTLD-SERVERS.NET.
Now we can dig these DNS servers to get the domains NS records found on the .net tld ROOT DNS servers.
dig @H.GTLD-SERVERS.net cpanel.net NS
;; AUTHORITY SECTION: uhgbug.com. 172800 IN NS ns1.nextbesthost.com. uhgbug.com. 172800 IN NS ns2.nextbesthost.com.
This helps when you need to confirm whether or not domain resolution issues are due to incorrectly assigned DNS servers for a domain.
|
|
Last Updated on Saturday, 14 February 2009 06:48 |