[Buildbot] #3151: host reverse DNS

Buildbot trac trac at buildbot.net
Sat Jan 24 19:51:24 UTC 2015


#3151: host reverse DNS
-------------------+--------------------------------
Reporter:  dustin  |       Owner:  dustin
    Type:  task    |      Status:  assigned
Priority:  major   |   Milestone:  sys - on-bb-infra
 Version:          |  Resolution:
Keywords:          |
-------------------+--------------------------------

Comment (by dustin):

 OK, tracking this down from the top level.  The first few are boring:

 {{{
 dustin at euclid ~ $ dig @a.root-servers.net -tptr +norecurse -4
 243.224-255.128-255.10.211.140.in-addr.arpa.
 ;; AUTHORITY SECTION:
 in-addr.arpa.           172800  IN      NS      f.in-addr-servers.arpa.
 in-addr.arpa.           172800  IN      NS      e.in-addr-servers.arpa.
 in-addr.arpa.           172800  IN      NS      d.in-addr-servers.arpa.
 in-addr.arpa.           172800  IN      NS      c.in-addr-servers.arpa.
 in-addr.arpa.           172800  IN      NS      b.in-addr-servers.arpa.
 in-addr.arpa.           172800  IN      NS      a.in-addr-servers.arpa.

 dustin at euclid ~ $ dig @a.in-addr-servers.arpa. -tptr +norecurse -4
 243.224-255.128-255.10.211.140.in-addr.arpa.
 ;; AUTHORITY SECTION:
 140.in-addr.arpa.       86400   IN      NS      y.arin.net.
 140.in-addr.arpa.       86400   IN      NS      t.arin.net.
 140.in-addr.arpa.       86400   IN      NS      r.arin.net.
 140.in-addr.arpa.       86400   IN      NS      w.arin.net.
 140.in-addr.arpa.       86400   IN      NS      x.arin.net.
 140.in-addr.arpa.       86400   IN      NS      u.arin.net.
 140.in-addr.arpa.       86400   IN      NS      v.arin.net.
 140.in-addr.arpa.       86400   IN      NS      z.arin.net.

 dustin at euclid ~ $ dig @y.arin.net. -tptr +norecurse -4
 243.224-255.128-255.10.211.140.in-addr.arpa.
 ;; AUTHORITY SECTION:
 211.140.in-addr.arpa.   86400   IN      NS      ns1.nero.net.
 211.140.in-addr.arpa.   86400   IN      NS      ns2.nero.net.
 211.140.in-addr.arpa.   86400   IN      NS      phloem.uoregon.edu.

 dustin at euclid ~ $ dig @ns1.nero.net. -tptr +norecurse -4
 243.224-255.128-255.10.211.140.in-addr.arpa.
 ;; AUTHORITY SECTION:
 128-255.10.211.140.in-addr.arpa. 259200 IN NS   ns3.auth.osuosl.org.
 128-255.10.211.140.in-addr.arpa. 259200 IN NS   ns2.rtems.org.
 128-255.10.211.140.in-addr.arpa. 259200 IN NS   ns1.auth.osuosl.org.
 128-255.10.211.140.in-addr.arpa. 259200 IN NS   ns2.auth.osuosl.org.
 128-255.10.211.140.in-addr.arpa. 259200 IN NS   ns1.rtems.org.
 }}}

 OK, so we have four hosts that are authoritative for the 128-255
 subdomain.  So they should all give the same answers.  But they don't!
 The RTEMS servers give:
 {{{
 dustin at euclid ~ $ dig @ns1.rtems.org. -tptr +norecurse -4
 243.224-255.128-255.10.211.140.in-addr.arpa.

 ; <<>> DiG 9.9.5 <<>> @ns1.rtems.org. -tptr +norecurse -4
 243.224-255.128-255.10.211.140.in-addr.arpa.
 ; (1 server found)
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19118
 ;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1

 ;; OPT PSEUDOSECTION:
 ; EDNS: version: 0, flags:; udp: 4096
 ;; QUESTION SECTION:
 ;243.224-255.128-255.10.211.140.in-addr.arpa. IN        PTR

 ;; ANSWER SECTION:
 243.224-255.128-255.10.211.140.in-addr.arpa. 86400 IN PTR
 ftp.buildbot.net.

 ;; AUTHORITY SECTION:
 224-255.128-255.10.211.140.in-addr.arpa. 7200 IN NS c.ns.buddyns.com.
 224-255.128-255.10.211.140.in-addr.arpa. 7200 IN NS f.ns.buddyns.com.
 224-255.128-255.10.211.140.in-addr.arpa. 7200 IN NS ns1.rtems.org.
 224-255.128-255.10.211.140.in-addr.arpa. 7200 IN NS ns1.darkbeer.org.

 ;; Query time: 80 msec
 ;; SERVER: 140.211.10.139#53(140.211.10.139)
 ;; WHEN: Sat Jan 24 14:38:46 EST 2015
 ;; MSG SIZE  rcvd: 202
 }}}

 The PTR record isn't on the osuosl servers, but the NS records (authority
 section) should be.  It's not:

 {{{
 dustin at euclid ~ $ dig @ns1.auth.osuosl.org. -tptr +norecurse -4
 243.224-255.128-255.10.211.140.in-addr.arpa.

 ; <<>> DiG 9.9.5 <<>> @ns1.auth.osuosl.org. -tptr +norecurse -4
 243.224-255.128-255.10.211.140.in-addr.arpa.
 ; (1 server found)
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7047
 ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

 ;; QUESTION SECTION:
 ;243.224-255.128-255.10.211.140.in-addr.arpa. IN        PTR

 ;; AUTHORITY SECTION:
 128-255.10.211.140.in-addr.arpa. 86400 IN SOA   ns1.rtems.org.
 abuse.rtems.org. 43 10800 3600 604800 600

 ;; Query time: 81 msec
 ;; SERVER: 140.211.166.140#53(140.211.166.140)
 ;; WHEN: Sat Jan 24 14:38:39 EST 2015
 ;; MSG SIZE  rcvd: 116
 }}}

 Both sets of hosts appear to have the same serial (43) for the 128-255
 zone, but are giving different answers.

--
Ticket URL: <http://trac.buildbot.net/ticket/3151#comment:16>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation


More information about the bugs mailing list