[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AAAA on various websites, but they all forgot to enable them on their nameservers....



Hi.

The main objective for today is to access the web services, that's why you
can't reach a AAAA record for a DNS query for a given NS server.


; <<>> DiG 9.5.1-P3 <<>> www.google.com aaaa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40029
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 4

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

;; ANSWER SECTION:
www.google.com.        532907    IN    CNAME    www.l.google.com.
www.l.google.com.    150    IN    AAAA    2001:4860:4002:802::1010

; <<>> DiG 9.5.1-P3 <<>> www.yahoo.com aaaa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60816
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 2, ADDITIONAL: 2

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

;; ANSWER SECTION:
www.yahoo.com.        284    IN    CNAME    fpfd.wa1.b.yahoo.com.
fpfd.wa1.b.yahoo.com.    6    IN    AAAA    2001:4998:f00c:1fe::3001
fpfd.wa1.b.yahoo.com.    6    IN    AAAA    2001:4998:f011:1fe::3001
fpfd.wa1.b.yahoo.com.    6    IN    AAAA    2001:4998:f011:1fe::3000
fpfd.wa1.b.yahoo.com.    6    IN    AAAA    2001:4998:f00d:1fe::3001
fpfd.wa1.b.yahoo.com.    6    IN    AAAA    2001:4998:f00d:1fe::3000
fpfd.wa1.b.yahoo.com.    6    IN    AAAA    2001:4998:f00c:1fe::3000
; <<>> DiG 9.5.1-P3 <<>> www.facebook.com aaaa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12079
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

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

;; ANSWER SECTION:
www.facebook.com.    8    IN    AAAA    2620:0:1c00:0:face:b00c:0:1



; <<>> DiG 9.5.1-P3 <<>> www.unam.mx aaaa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42381
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5

;; QUESTION SECTION:
;www.unam.mx.            IN    AAAA

;; ANSWER SECTION:
www.unam.mx.        6031    IN    AAAA    2001:1218:1:6:d685:64ff:fec4:720b

You see? there's a lot of IPv6 activity since a few weeks ago. xD




----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 08 Jun 2011 11:28:40 +0200
> From: Jeroen Massar <jeroen at unfix.org>
> Subject: AAAA on various websites, but they all forgot to enable them
>        on their        nameservers....
> To: nanog <nanog at nanog.org>
> Message-ID: <4DEF40C8.3020502 at unfix.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> It is really nice that folks where able to put AAAA records on their
> websites for only 24 hours, but they forgot to put in the glue on their
> nameservers.
>
> As such, for the folks testing IPv6-only, a lot of sites will fail
> unless they use a recursor that does the IPv4 for them.
>
> The root is there, .com does it mostly too (well, a+b have IPv6), but
> most sites don't. Thus maybe that can be done next year on the next IPv6
> day? :)
>
> At least one step closer, now lets hope that sites also keep that IPv6
> address there.
>
> Greets,
>  Jeroen
>
> --
>
> $ dig @d.gtld-servers.net ns1.google.com aaaa
>
> ; <<>> DiG 9.7.3 <<>> @d.gtld-servers.net ns1.google.com aaaa
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16030
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4
> ;; WARNING: recursion requested but not available
>
> ;; QUESTION SECTION:
> ;ns1.google.com.                        IN      AAAA
>
> ;; AUTHORITY SECTION:
> google.com.             172800  IN      NS      ns2.google.com.
> google.com.             172800  IN      NS      ns1.google.com.
> google.com.             172800  IN      NS      ns3.google.com.
> google.com.             172800  IN      NS      ns4.google.com.
>
> ;; ADDITIONAL SECTION:
> ns2.google.com.         172800  IN      A       216.239.34.10
> ns1.google.com.         172800  IN      A       216.239.32.10
> ns3.google.com.         172800  IN      A       216.239.36.10
> ns4.google.com.         172800  IN      A       216.239.38.10
>
> ;; Query time: 123 msec
> ;; SERVER: 192.31.80.30#53(192.31.80.30)
> ;; WHEN: Wed Jun  8 11:26:35 2011
> ;; MSG SIZE  rcvd: 164
>
> $ dig @d.gtld-servers.net ns1.cisco.com aaaa
>
> ; <<>> DiG 9.7.3 <<>> @d.gtld-servers.net ns1.cisco.com aaaa
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55271
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
> ;; WARNING: recursion requested but not available
>
> ;; QUESTION SECTION:
> ;ns1.cisco.com.                 IN      AAAA
>
> ;; AUTHORITY SECTION:
> cisco.com.              172800  IN      NS      ns1.cisco.com.
> cisco.com.              172800  IN      NS      ns2.cisco.com.
>
> ;; ADDITIONAL SECTION:
> ns1.cisco.com.          172800  IN      A       128.107.241.185
> ns2.cisco.com.          172800  IN      A       64.102.255.44
>
> ;; Query time: 126 msec
> ;; SERVER: 192.31.80.30#53(192.31.80.30)
> ;; WHEN: Wed Jun  8 11:28:14 2011
> ;; MSG SIZE  rcvd: 95
>
>
>
> ------------------------------
>
-- 
*Daniel Espejel P?rez
Universidad Nacional Aut?noma de M?xico.
Direcci?n General de C?mputo y Tecnolog?as de la Informaci?n y Comunicaci?n.
Laboratorio de Tecnolog?as Emergentes de Red (NetLab).
GT - IPv6 UNAM , GT - IPv6 CLARA
http://www.netlab.unam.mx/*