Public DNS64

Mon May 30 02:01:34 UTC 2016

IP6.ARPA lookups aren't working.  Adobe.com doesn't have AAAA record
so it correctly returns a DNS64 mapped AAAA record.  However when
you attempt to do a IP6.ARPA lookup on that address it does not
follow the synthesised CNAME record as you would expect from a
recursive DNS64 server.

Mark

; <<>> DiG 9.11.0a2 <<>> aaaa adobe.com @2001:4860:4860::6464
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16081
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;adobe.com.			IN	AAAA

;; ANSWER SECTION:
adobe.com.		10799	IN	AAAA	64:ff9b::c096:1075

;; Query time: 435 msec
;; SERVER: 2001:4860:4860::6464#53(2001:4860:4860::6464)
;; WHEN: Mon May 30 11:55:56 EST 2016
;; MSG SIZE  rcvd: 66

; <<>> DiG 9.11.0a2 <<>> -x 64:ff9b::c096:1075 @2001:4860:4860::6464
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16070
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;5.7.0.1.6.9.0.c.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.9.f.f.4.6.0.0.ip6.arpa. IN PTR

;; ANSWER SECTION:
5.7.0.1.6.9.0.c.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.9.f.f.4.6.0.0.ip6.arpa. 10799	IN CNAME 117.16.150.192.in-addr.arpa.

;; Query time: 355 msec
;; SERVER: 2001:4860:4860::6464#53(2001:4860:4860::6464)
;; WHEN: Mon May 30 11:56:12 EST 2016
;; MSG SIZE  rcvd: 138

; <<>> DiG 9.11.0a2 <<>> ptr 117.16.150.192.in-addr.arpa @2001:4860:4860::6464
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 93
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;117.16.150.192.in-addr.arpa.	IN	PTR

;; ANSWER SECTION:
117.16.150.192.in-addr.arpa. 10532 IN	PTR	www.wip4.adobe.com.

;; Query time: 338 msec
;; SERVER: 2001:4860:4860::6464#53(2001:4860:4860::6464)
;; WHEN: Mon May 30 11:56:36 EST 2016
;; MSG SIZE  rcvd: 88

In message <CAE_ug16_y+Ww8B3vkh-V4RNgGJyGcT9GH65z7uYpf_-XuR_ReA at mail.gmail.com>
, Tim Durack writes:
> For the record:
> 
> Tim,
> 
> I'm not on the NANOG lists and I don't see how I can respond to this thread:
> 
>     https://mailman.nanog.org/pipermail/nanog/2014-August/069267.html
> 
> but I figured I'd let you know that:
> 
>     https://developers.google.com/speed/public-dns/docs/dns64
> 
> is now available for testing.  Perhaps it will be some use.
> 
> Regards,
> -Erik
> 
> On Fri, Aug 15, 2014 at 2:29 PM, Tim Durack <tdurack at gmail.com> wrote:
> 
> > Anyone know of a reliable public DNS64 service?
> >
> > Would be cool if Google added a Public DNS64 service, then I could point
> > the NAT64 prefix at appropriately placed boxes in my network.
> >
> > Why? Other people are better than me at running DNS resolvers :-)
> >
> > --
> > Tim:>
> >
> 
> 
> 
> -- 
> Tim:>
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org