Problems with DNS...

[Bruce Dawson]

Well, with lots of help from MV and lots of reading of dig(1) and
host(1) manual pages, we finally saw that there were trailing dots on
the IP addresses in the NS RR's. We changed the IP addresses to domain
names, and now things are working. We figure that IP addresses were
inserted for the NS records when registering the domain.

The IP addresses don't appear in the output below, but they do appear
when I use host's -r and -v options (-r: stop recursive lookups; -v:
verbose output). I had to "run out of options" before thinking of
looking at the man pages for more ways to use the commands to get more
"debugging" output. Sigh.

Can you imagine trying to diagnose this on a commercial operating
system? (I'm not thinking of a Unix based system. :-)

--Bruce
PS: We may also have uncovered some inconsistencies in IPV6 name
resolution, but we're not interested in solving that problem - at least
not tonight.

Bruce Dawson wrote:
> OK, I'm sorta embarrassed to say this, but I'm having problems with DNS
> and can't figure out what I'm missing - maybe someone can give me a clue.
>
> I recently registered a domain (loudonag.org), and the root name servers
> know about it...
>
>     jbd at bruce:~$ whois loudonag.org
>     NOTICE: Access to .ORG WHOIS information is provided to assist
>     persons in ...
>
>     Domain ID:D157281062-LROR
>     Domain Name:LOUDONAG.ORG
>     Created On:07-Oct-2009 00:12:38 UTC
>     Last Updated On:07-Oct-2009 00:12:40 UTC
>     Expiration Date:07-Oct-2010 00:12:38 UTC
>     Sponsoring Registrar:Tucows Inc. (R11-LROR)
>     Status:CLIENT TRANSFER PROHIBITED
>     Status:CLIENT UPDATE PROHIBITED
>     Status:TRANSFER PROHIBITED
>     ...
>     Name Server:199.125.75.9
>     Name Server:199.125.75.14
>     ...
>     DNSSEC:Unsigned
>
> The authorative servers know about it...
>
>     jbd at bruce:~$ host -v loudonag.org 199.125.75.14
>     Trying "loudonag.org"
>     Using domain server:
>     Name: 199.125.75.14
>     Address: 199.125.75.14#53
>     Aliases:
>
>     ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15507
>     ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
>
>     ;; QUESTION SECTION:
>     ;loudonag.org.                  IN      A
>
>     ;; ANSWER SECTION:
>     loudonag.org.           3600    IN      A       199.125.76.131
>
>     ;; AUTHORITY SECTION:
>     loudonag.org.           3600    IN      NS      simon.codemeta.com.
>     loudonag.org.           3600    IN      NS      river.codemeta.com.
>
>     ;; ADDITIONAL SECTION:
>     simon.codemeta.com.     300     IN      A       199.125.75.14
>     river.codemeta.com.     300     IN      A       199.125.75.9
>
>     Received 130 bytes from 199.125.75.14#53 in 31 ms
>     Trying "loudonag.org"
>     Using domain server:
>     Name: 199.125.75.14
>     Address: 199.125.75.14#53
>     Aliases:
>
>     ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65239
>     ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
>     ;; QUESTION SECTION:
>     ;loudonag.org.                  IN      AAAA
>
>     ;; AUTHORITY SECTION:
>     loudonag.org.           604800  IN      SOA     simon.codemeta.com.
>     jbd.codemeta.com. 2009102001 86400 1800 3600000 604800
>
>     Received 88 bytes from 199.125.75.14#53 in 30 ms
>     Trying "loudonag.org"
>     Using domain server:
>     Name: 199.125.75.14
>     Address: 199.125.75.14#53
>     Aliases:
>
>     ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55291
>     ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
>
>     ;; QUESTION SECTION:
>     ;loudonag.org.                  IN      MX
>
>     ;; ANSWER SECTION:
>     loudonag.org.           3600    IN      MX      10 simon.codemeta.com.
>
>     ;; AUTHORITY SECTION:
>     loudonag.org.           3600    IN      NS      simon.codemeta.com.
>     loudonag.org.           3600    IN      NS      river.codemeta.com.
>
>     ;; ADDITIONAL SECTION:
>     simon.codemeta.com.     300     IN      A       199.125.75.14
>     river.codemeta.com.     300     IN      A       199.125.75.9
>
>     Received 130 bytes from 199.125.75.14#53 in 30 ms
>
> But no one else appears to know about it...
>
>     jbd at bruce:~$ host -v loudonag.org
>     Trying "loudonag.org"
>     ;; connection timed out; no servers could be reached
>
>
> The last message (no servers could be reached) is the most frustrating
> because I was able to "reach" the server in the previous command (host
> -v loudonag.org 199.125.75.14).
>
> And, using the Comcast server:
>
>     jbd at bruce:~$ host -v loudonag.org 68.87.71.230
>     Trying "loudonag.org"
>     Using domain server:
>     Name: 68.87.71.230
>     Address: 68.87.71.230#53
>     Aliases:
>
>     Host loudonag.org not found: 2(SERVFAIL)
>     Received 30 bytes from 68.87.71.230#53 in 16 ms
>
>
> Does anyone know what's going wrong?
>
> --Bruce
>
>
>
>
>
>
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
>