[dns-operations] IM. TLD

[Mitchell Kuch]

Shane -

I appreciate everyones effort in supporting IPv6 DNS. Continued
communication is key and we have seen great strides with
implementations - in part because of this forum.

I've too have attempted to work with the TLDs to flush out their IPv6
implementations. It is a bit strange the oddities that one can stumble
across.

Take the im. TLD as an example.

im. 172800  IN      NS      ns4.ja.net
.
im. 172800  IN      NS      hoppy.iom.com
.
im. 172800  IN      NS      barney.advsys.co.uk
.
im. 172800  IN      NS      pebbles.iom.com
.

Only ns4.ja.net
. has a AAAA record.

ns4.ja.net
. 86400   IN      A       193.62.157.66
ns4.ja.net
. 86400   IN      AAAA    2001:630:0:47::42

and only ns4.ja.net.provides AAAA glue records for im. domains

$ dig +additional @ns4.ja.net
. ns1.im

.

; <<>> DiG 9.8.3-P1 <<>> +additional @ns4.ja.net
. ns1.im

.
; (1 server found)
;; global options: +cmd

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42217
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 5
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;ns1.im

.                                IN      A


;; AUTHORITY SECTION:
ns1.im

. 259200  IN      NS      ns1.im

.
ns1.im

. 259200  IN      NS      ns0.im

.
ns1.im

. 259200  IN      NS      ns2.im

.

;; ADDITIONAL SECTION:
ns1.im

. 43200   IN      A       85.159.233.58
ns1.im

. 43200   IN      AAAA    2604:9a00:2100:a000:3::6
ns0.im

. 43200   IN      A       50.7.96.170
ns2.im

. 43200   IN      A       108.59.1.205
ns2.im

. 43200   IN      AAAA    2604:9a00:2100:a001:2::1

;; Query time: 179 msec
;; SERVER: 193.62.157.66#53(193.62.157.66)
;; WHEN: Thu Sep 10 14:13:24 2015
;; MSG SIZE  rcvd: 178


$ dig +additional @hoppy.iom.com
. ns1.im

.

; <<>> DiG 9.8.3-P1 <<>> +additional @hoppy.iom.com
. ns1.im

.
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8399
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;ns1.im

.                                IN      A

;; AUTHORITY SECTION:
ns1.im

. 259200  IN      NS      ns0.im

.
ns1.im

. 259200  IN      NS      ns2.im

.
ns1.im

. 259200  IN      NS      ns1.im

.

;; ADDITIONAL SECTION:
ns0.im

 43200   IN      A       50.7.96.170
ns2.im

. 43200   IN      A       108.59.1.205
ns1.im

. 43200   IN      A       85.159.233.58

;; Query time: 148 msec
;; SERVER: 217.23.163.140#53(217.23.163.140)
;; WHEN: Thu Sep 10 14:13:43 2015
;; MSG SIZE  rcvd: 122


While ns4.ja.net
. servers IPv6 records for the im. zone and delegates
(via both IPv4 and IPv6) the other TLD names servers do not.

 - - Mitchell

----- Original Message -----
From: "Shane Kerr" <shane at time-travellers.org>
To: "Jim Reid" <jim at rfc1035.com>
Cc: dns-operations at dns-oarc.net
Sent: Wednesday, September 9, 2015 2:04:43 AM
Subject: Re: [dns-operations] Enabling the IPv6-only Internet: the Final TLDs

> My proposal is "try to do something to help". You idea is that this is wrong, and therefore we should... not?