Previous Next
Host Example (cont. 3) 
me@myhost:~$ host -t ns clue.denver.co.us. dns0.techangle.com
Using domain server:
Name: dns0.techangle.com
Address: 199.239.19.9#53
Aliases: 

clue.denver.co.us name server dns0.techangle.com.
clue.denver.co.us name server kessel.techangle.com.
clue.denver.co.us name server corelia.techangle.com.
clue.denver.co.us name server coruscant.techangle.com.

me@myhost:~$ host clue.denver.co.us. dns0.techangle.com
Using domain server:
Name: dns0.techangle.com
Address: 199.239.19.9#53
Aliases: 

clue.denver.co.us has address 199.239.19.17

me@myhost:~$
© 2002 David Anselmi

Almost done.

dns0.techangle.com tells us we've hit the end of the trail–no new name servers to discover.

Finally we ask for the (default) address record (rather than name server) and get the address.

As you follow this trail, if something is broken you'll find NS records that lead to name servers that are unreachable or don't know about the domain they've been delegated (lame delegation). Depending where the problem is you now know where to complain, or how long to wait to try again.

Does anyone see the problem with the CLUE delegation?