DNS lookup/IPv6 help

DStrout

Me again with more IPv6 stuff. I contacted my domain registrar, Namecheap, to add IPv6 glue records to my domain so that I could fully set up IPv6 AAAA DNS records. They said the records were added, and I configured BIND accordingly, but there seems to be a hitch somewhere along the way. What do I mean? See for yourself. From one of your IPv6-enabled servers (you do have one, right?), ping6 (or anything that will look up and return the IPv6 address associated with) ns1.dstrout.net AND ns2.dstrout.net. Chances are, one of them will work but not the other. It seems to be the case with all my IPv6 servers, as well as various other IPv6 ping services online.

So, any idea why? I've mentioned the problem to Namecheap, but they'll undoubtedly have to check with eNom, their upstream provider (which they had to do to set the records in the first place), so I was hoping someone here could help me. I suppose it's not really that big a deal, any computer doing an IPv6 lookup should fail over to whichever nameserver it can reach, but I want this to work properly.

dmmcintyre3

ns2.dstroute.net doesn't return any AAAA records.

bash-3.2$ dig AAAA ns1.dstrout.net @72.11.156.164

; <<>> DiG 9.6-ESV-R4-P3 <<>> AAAA ns1.dstrout.net @72.11.156.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38562
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;ns1.dstrout.net.               IN      AAAA

;; AUTHORITY SECTION:
dstrout.net.            86400   IN      SOA     ns1.dstrout.net. webmaster.dstrout.net.dstrout.net. 2013031401 10800 1800 604800 86400

;; Query time: 100 msec
;; SERVER: 72.11.156.164#53(72.11.156.164)
;; WHEN: Mon Mar 18 01:23:55 2013
;; MSG SIZE  rcvd: 91

bash-3.2$ dig AAAA ns2.dstrout.net @72.11.156.164

; <<>> DiG 9.6-ESV-R4-P3 <<>> AAAA ns2.dstrout.net @72.11.156.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63138
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;ns2.dstrout.net.               IN      AAAA

;; AUTHORITY SECTION:
dstrout.net.            86400   IN      SOA     ns1.dstrout.net. webmaster.dstrout.net.dstrout.net. 2013031401 10800 1800 604800 86400

;; Query time: 99 msec
;; SERVER: 72.11.156.164#53(72.11.156.164)
;; WHEN: Mon Mar 18 01:24:04 2013
;; MSG SIZE  rcvd: 95

bash-3.2$ dig AAAA ns2.dstrout.net @192.73.237.132

; <<>> DiG 9.6-ESV-R4-P3 <<>> AAAA ns2.dstrout.net @192.73.237.132
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23180
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;ns2.dstrout.net.               IN      AAAA

;; ANSWER SECTION:
ns2.dstrout.net.        86400   IN      AAAA    2607:fcd0:100:b00::5927:9b86

;; AUTHORITY SECTION:
dstrout.net.            86400   IN      NS      ns1.dstrout.net.
dstrout.net.            86400   IN      NS      ns2.dstrout.net.

;; ADDITIONAL SECTION:
ns1.dstrout.net.        86400   IN      A       192.73.237.132
ns1.dstrout.net.        86400   IN      AAAA    2604:180::b532:7d90
ns2.dstrout.net.        86400   IN      A       72.11.156.164

;; Query time: 62 msec
;; SERVER: 192.73.237.132#53(192.73.237.132)
;; WHEN: Mon Mar 18 01:24:15 2013
;; MSG SIZE  rcvd: 153

bash-3.2$ dig AAAA ns1.dstrout.net @192.73.237.132

; <<>> DiG 9.6-ESV-R4-P3 <<>> AAAA ns1.dstrout.net @192.73.237.132
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64813
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;ns1.dstrout.net.               IN      AAAA

;; ANSWER SECTION:
ns1.dstrout.net.        86400   IN      AAAA    2604:180::b532:7d90

;; AUTHORITY SECTION:
dstrout.net.            86400   IN      NS      ns2.dstrout.net.
dstrout.net.            86400   IN      NS      ns1.dstrout.net.

;; ADDITIONAL SECTION:
ns1.dstrout.net.        86400   IN      A       192.73.237.132
ns2.dstrout.net.        86400   IN      A       72.11.156.164
ns2.dstrout.net.        86400   IN      AAAA    2607:fcd0:100:b00::5927:9b86

;; Query time: 60 msec
;; SERVER: 192.73.237.132#53(192.73.237.132)
;; WHEN: Mon Mar 18 01:24:18 2013
;; MSG SIZE  rcvd: 153</pre>

tehdan

as @dmmcintyre3 says ns2 doesn't have AAAA records for ns1/2 - this won't help things.

Looking at your SOA there's a couple of problems

dstrout.net. 86400 IN SOA ns1.dstrout.net. webmaster.dstrout.net.dstrout.net. 2013031401 10800 1800 604800 86400

firstly your RP needs to be set as either 'webmaster' or 'webmaster.dstrout.net.' but not 'webmaster.dstrout.net' (this is not critical but it looks silly...)

secondly I notice you haven't updated your zone serial number since the 14th (assuming you're using dates like most people...). Maybe you have set AAAA records but forgotten to increment the serial no?

DStrout

I had made changes to the zone file and updated the serial, but I guess it didn't take effect for some reason. The name servers are running Ubuntu 12.04, and after making changes to the zone file on the master I ran

service bind9 reload

Should I have run a restart instead? Either way, I just did - it can't hurt.

emg

Monday, 18 March 2013, 9:30 AM MDT
I tried ping6 to both of your nameservers and the domain itself, and all returned "unknown host." The same host sending ping6 to known names (ipv6.google.com and ipv6-test.com) worked correctly.

tehdan

@DStrout I suspect you've broken your zonefile and bind is skipping it - check syslog, looks like the records on ns2 are now completely expired

a reload is sufficient to read an updated zonefile (as long as its valid!)

tehdan

Or, run named-checkzone over your zonefile...

DStrout

@tehdan said: run named-checkzone over your zonefile

Thanks for that tip, I got back the error "bad dotted quad", and after some looking, I found that I'd marked what should have been an AAAA record as an A record. Fixed and reloaded, now to twiddle my thumbs while I wait for everything to propagate again.

tehdan

Now looking good from here, geting AAAA records from both servers

DStrout

Yup, working for me too. Thanks for the advice @dmmcintyre3 and @tehdan!

emg

A ping6 of ns1.dstrout.net and ns2.dstrout.net now get good responses. Both have very different IPv6 addresses. A ping6 of "dstrout.net" still returns "unknown host", which is probably what you expect.

DStrout

@emg said: very different IPv6 addresses

Two different providers on two different sides of the country.