0x20 support....

[Nicholas Weaver]

I'm still not seeing 0x20 support from Google public DNS reaching our
authority:

dig entropy.aa.netalyzr.icsi.berkeley.edu @8.8.8.8

; <<>> DiG 9.5.1-P2-RedHat-9.5.1-2.P2.fc10 <<>>
entropy.aa.netalyzr.icsi.berkeley.edu @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16329
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;entropy.aa.netalyzr.icsi.berkeley.edu. IN A

;; ANSWER SECTION:
entropy.aa.netalyzr.icsi.berkeley.edu. 1 IN CNAME status.pt=40931-
end.ad=74-125-154-94-end.id=18762-end.
0x20=F.done.aa.netalyzr.icsi.berkeley.edu.
status.pt=40931-end.ad=74-125-154-94-end.id=18762-end.
0x20=F.done.aa.netalyzr.icsi.berkeley.edu. 1 IN A 10.1.2.3

(translation of the CNAME:
UDP source port used 41931
Source address of request 74.125.154.94
query ID 18762
0x20 not seen
)


Yet its clearly passing capitalization:
dig entropy.aA.netalyzr.icsi.berkeley.edu @8.8.8.8

; <<>> DiG 9.5.1-P2-RedHat-9.5.1-2.P2.fc10 <<>>
entropy.aA.netalyzr.icsi.berkeley.edu @8.8.8.8
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58603
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;entropy.aA.netalyzr.icsi.berkeley.edu. IN A

;; ANSWER SECTION:
entropy.aA.netalyzr.icsi.berkeley.edu. 1 IN CNAME status.pt=46155-
end.ad=74-125-154-94-end.id=48852-end.
0x20=T.done.aA.netalyzr.icsi.berkeley.edu.
status.pt=46155-end.ad=74-125-154-94-end.id=48852-end.
0x20=T.done.aA.netalyzr.icsi.berkeley.edu. 1 IN A 10.1.2.3

(the algorithm for 0x20 is if ALL lower case or all upper case, return
F, otherwise return T, so a mixed-case request clearly returns true)


What is the algorithm which google public DNS uses to assume that an
authority supports 0x20?

[Nicholas Weaver]

Its now correctly using 0x20 in contacting our authority, but the
question remains: what is the algorithm used to determine if an
authority is 0x20 capable?

Thanks.

[Alex Nizhner]

Its now correctly using 0x20 in contacting our authority, but the
question remains: what is the algorithm used to determine if an
authority is 0x20 capable?

We periodically do a (offline) scan and probe of all nameservers we've seen.  This generally covers the majority of our outbound traffic, but the process does occasionally get behind and/or miss 0x20-capable nameservers.  This will get better soon.

Alex
 

Thanks.

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================

[mankow]

How do you scan for a 0x20 name server? What tests are done?