[dns-operations] .pro oddities

[Roy Arends]

On Sep 4, 2006, at 1:53 PM, James Raftery wrote:

> On Sun, Sep 03, 2006 at 09:15:33AM +0200, Florian Weimer wrote:
>> The .pro operator uses some very strange DNS setup.  A query for
>> law.pro/IN/SOA returns NOERROR and a SOA RR for law.pro.
>
> But NXDOMAIN for law.pro/NS:
>
> ; <<>> DiG 9.3.2 <<>> @a.gtld.pro. law.pro. ns +norec
> ; (1 server found)
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11414
> ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;law.pro.                       IN      NS
>
> ;; AUTHORITY SECTION:
> law.pro.                14400   IN      SOA     a.gtld.pro.  
> hostmaster.registrypro.pro. 2006090117 28800 7200 604800 300
>
> ;; Query time: 129 msec
> ;; SERVER: 192.149.62.10#53(192.149.62.10)
> ;; WHEN: Mon Sep  4 12:43:54 2006
> ;; MSG SIZE  rcvd: 91
>
>
> Returning an authoritative SOA in response to a law.pro/SOA query but
> NXDOMAIN for law.pro/NS is broken. FWIW, fpdns says a.gtld.pro is
> running `bboy MyDNS'.


registry pro's nameserver fingerprint gives a false positive for bboy  
MyDNS. MyDNS does not have the above issue, and upon further  
investigation, registry pro's nameserver behaves differently. So, it  
is either heavily patched, or build from the ground up.

Roy