Mailing List Archive

prompt$ dig +short @publicdns64.google.com -t AAAA www.rt.com
64:ff9b::cff4:50a6

On 7 July 2016 at 12:22, Ca By <cb.list6@gmail.com> wrote:
> Anyone have a contact at www.rt.com that can encourage them to to delete
> their bad aaaa ?
>
> This is breaking nat64 users who see a aaaa so no dns64 is being done.
>
> Shared from ISC Dig for iOS
>
> ; <<>> DiG 9.10.4 <<>> @fe80::4c60:deff:fee6:b019 @192.168.1.1 www.rt.com
> aaaa +sit +dnssec +noqr +multiline
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4367
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags: do; udp: 512
> ;; QUESTION SECTION:
> ;www.rt.com. IN AAAA
>
> ;; ANSWER SECTION:
> www.rt.com. 10 IN AAAA ::ffff:37.48.108.112
>
>
> ;; Query time: 298 msec
> ;; SERVER: 192.168.1.1#53(192.168.1.1)
> ;; WHEN: Wed Jul 06 20:19:34 PDT 2016
> ;; MSG SIZE rcvd: 67
>

https://tools.ietf.org/html/rfc6147#section-5.1.4

Thought technically it's just a SHOULD, I recall implementing
something about this.


On 7 July 2016 at 13:00, Erik Marcus Kline <ek@google.com> wrote:
> prompt$ dig +short @publicdns64.google.com -t AAAA www.rt.com
> 64:ff9b::cff4:50a6
>
> On 7 July 2016 at 12:22, Ca By <cb.list6@gmail.com> wrote:
>> Anyone have a contact at www.rt.com that can encourage them to to delete
>> their bad aaaa ?
>>
>> This is breaking nat64 users who see a aaaa so no dns64 is being done.
>>
>> Shared from ISC Dig for iOS
>>
>> ; <<>> DiG 9.10.4 <<>> @fe80::4c60:deff:fee6:b019 @192.168.1.1 www.rt.com
>> aaaa +sit +dnssec +noqr +multiline
>> ; (1 server found)
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4367
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>>
>> ;; OPT PSEUDOSECTION:
>> ; EDNS: version: 0, flags: do; udp: 512
>> ;; QUESTION SECTION:
>> ;www.rt.com. IN AAAA
>>
>> ;; ANSWER SECTION:
>> www.rt.com. 10 IN AAAA ::ffff:37.48.108.112
>>
>>
>> ;; Query time: 298 msec
>> ;; SERVER: 192.168.1.1#53(192.168.1.1)
>> ;; WHEN: Wed Jul 06 20:19:34 PDT 2016
>> ;; MSG SIZE rcvd: 67
>>

I’m not getting consistent AAAA responses from publicdns64.google.com for www.rt.com.
It isn’t always mapping to 37.48.108.112 whereas the A record seems to consistently point at that IPv4.


dig @publicdns64.google.com aaaa www.rt.com

; <<>> DiG 9.8.3-P1 <<>> @publicdns64.google.com aaaa www.rt.com
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56562
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.rt.com. IN AAAA

;; ANSWER SECTION:
www.rt.com. 9 IN AAAA 64:ff9b::cff4:50a6

;; Query time: 84 msec
;; SERVER: 2001:4860:4860::6464#53(2001:4860:4860::6464)
;; WHEN: Thu Jul 7 06:37:24 2016
;; MSG SIZE rcvd: 56

dig @publicdns64.google.com aaaa www.rt.com

; <<>> DiG 9.8.3-P1 <<>> @publicdns64.google.com aaaa www.rt.com
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26971
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.rt.com. IN AAAA

;; ANSWER SECTION:
www.rt.com. 9 IN AAAA 64:ff9b::2530:6c70

;; Query time: 84 msec
;; SERVER: 2001:4860:4860::6464#53(2001:4860:4860::6464)
;; WHEN: Thu Jul 7 06:41:08 2016
;; MSG SIZE dcvd:
56

On 7 Jul 2016, at 05:02, Erik Marcus Kline <ek@google.com> wrote:

https://tools.ietf.org/html/rfc6147#section-5.1.4

Thought technically it's just a SHOULD, I recall implementing
something about this.


On 7 July 2016 at 13:00, Erik Marcus Kline <ek@google.com> wrote:

prompt$ dig +short @publicdns64.google.com -t AAAA www.rt.com
64:ff9b::cff4:50a6

On 7 July 2016 at 12:22, Ca By <cb.list6@gmail.com> wrote:

Anyone have a contact at www.rt.com that can encourage them to to delete
their bad aaaa ?

This is breaking nat64 users who see a aaaa so no dns64 is being done.

Shared from ISC Dig for iOS

; <<>> DiG 9.10.4 <<>> @fe80::4c60:deff:fee6:b019 @192.168.1.1 www.rt.com
aaaa +sit +dnssec +noqr +multiline
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4367
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
www.rt.com. 10 IN AAAA ::ffff:37.48.108.112


;; Query time: 298 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Wed Jul 06 20:19:34 PDT 2016
;; MSG SIZE rcvd: 67

Apologies, just saw a A record for 207.244.80.166 after querying for www.rt.com 8 times in a row.


> On 7 Jul 2016, at 06:50, Ross Chandler <ross@eircom.net> wrote:
>
> I’m not getting consistent AAAA responses from publicdns64.google.com for www.rt.com.
> It isn’t always mapping to 37.48.108.112 whereas the A record seems to consistently point at that IPv4.
>
>
> dig @publicdns64.google.com aaaa www.rt.com
>
> ; <<>> DiG 9.8.3-P1 <<>> @publicdns64.google.com aaaa www.rt.com
> ; (2 servers found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56562
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;www.rt.com. IN AAAA
>
> ;; ANSWER SECTION:
> www.rt.com. 9 IN AAAA 64:ff9b::cff4:50a6
>
> ;; Query time: 84 msec
> ;; SERVER: 2001:4860:4860::6464#53(2001:4860:4860::6464)
> ;; WHEN: Thu Jul 7 06:37:24 2016
> ;; MSG SIZE rcvd: 56
>
> dig @publicdns64.google.com aaaa www.rt.com
>
> ; <<>> DiG 9.8.3-P1 <<>> @publicdns64.google.com aaaa www.rt.com
> ; (2 servers found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26971
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;www.rt.com. IN AAAA
>
> ;; ANSWER SECTION:
> www.rt.com. 9 IN AAAA 64:ff9b::2530:6c70
>
> ;; Query time: 84 msec
> ;; SERVER: 2001:4860:4860::6464#53(2001:4860:4860::6464)
> ;; WHEN: Thu Jul 7 06:41:08 2016
> ;; MSG SIZE dcvd:
> 56
>
>
>
>> On 7 Jul 2016, at 05:02, Erik Marcus Kline <ek@google.com> wrote:
>>
>> https://tools.ietf.org/html/rfc6147#section-5.1.4
>>
>> Thought technically it's just a SHOULD, I recall implementing
>> something about this.
>>
>>
>> On 7 July 2016 at 13:00, Erik Marcus Kline <ek@google.com> wrote:
>>> prompt$ dig +short @publicdns64.google.com -t AAAA www.rt.com
>>> 64:ff9b::cff4:50a6
>>>
>>> On 7 July 2016 at 12:22, Ca By <cb.list6@gmail.com> wrote:
>>>> Anyone have a contact at www.rt.com that can encourage them to to delete
>>>> their bad aaaa ?
>>>>
>>>> This is breaking nat64 users who see a aaaa so no dns64 is being done.
>>>>
>>>> Shared from ISC Dig for iOS
>>>>
>>>> ; <<>> DiG 9.10.4 <<>> @fe80::4c60:deff:fee6:b019 @192.168.1.1 www.rt.com
>>>> aaaa +sit +dnssec +noqr +multiline
>>>> ; (1 server found)
>>>> ;; global options: +cmd
>>>> ;; Got answer:
>>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4367
>>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>>>>
>>>> ;; OPT PSEUDOSECTION:
>>>> ; EDNS: version: 0, flags: do; udp: 512
>>>> ;; QUESTION SECTION:
>>>> ;www.rt.com. IN AAAA
>>>>
>>>> ;; ANSWER SECTION:
>>>> www.rt.com. 10 IN AAAA ::ffff:37.48.108.112
>>>>
>>>>
>>>> ;; Query time: 298 msec
>>>> ;; SERVER: 192.168.1.1#53(192.168.1.1)
>>>> ;; WHEN: Wed Jul 06 20:19:34 PDT 2016
>>>> ;; MSG SIZE rcvd: 67
>>>>
>