https://inventory.mozilla.org/en-US/mozdns/record/update/A/18762/ record was added 2013-07-11 06:13:41, about 4.5h ago. It resolves on 10.22.75.40, but not 10.26.75.40: [root@cruncher.srv.releng.scl3 ~]# dig dev-linux64-ec2-yurenju1.dev.releng.use1.mozilla.com ; <<>> DiG 9.7.3-P3-RedHat-9.7.3-8.P3.el6_2.2 <<>> dev-linux64-ec2-yurenju1.dev.releng.use1.mozilla.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2390 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;dev-linux64-ec2-yurenju1.dev.releng.use1.mozilla.com. IN A ;; AUTHORITY SECTION: mozilla.com. 1800 IN SOA ns.mozilla.org. sysadmins.mozilla.org. 2013062325 180 86400 1209600 1800 ;; Query time: 7 msec ;; SERVER: 10.26.75.40#53(10.26.75.40) ;; WHEN: Thu Jul 11 07:40:46 2013 ;; MSG SIZE rcvd: 130 [root@cruncher.srv.releng.scl3 ~]# dig @10.22.75.40 dev-linux64-ec2-yurenju1.dev.releng.use1.mozilla.com ; <<>> DiG 9.7.3-P3-RedHat-9.7.3-8.P3.el6_2.2 <<>> @10.22.75.40 dev-linux64-ec2-yurenju1.dev.releng.use1.mozilla.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39832 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 ;; QUESTION SECTION: ;dev-linux64-ec2-yurenju1.dev.releng.use1.mozilla.com. IN A ;; ANSWER SECTION: dev-linux64-ec2-yurenju1.dev.releng.use1.mozilla.com. 3600 IN A 10.134.52.40 ;; AUTHORITY SECTION: mozilla.com. 600 IN NS ns3.mozilla.org. mozilla.com. 600 IN NS ns1.mozilla.org. mozilla.com. 600 IN NS ns2.mozilla.org. ;; ADDITIONAL SECTION: ns1.mozilla.org. 60 IN A 63.245.215.5 ns2.mozilla.org. 60 IN A 63.245.218.7 ns3.mozilla.org. 60 IN A 63.245.212.5 ;; Query time: 3 msec ;; SERVER: 10.22.75.40#53(10.22.75.40) ;; WHEN: Thu Jul 11 07:40:57 2013 ;; MSG SIZE rcvd: 199

Releng name servers weren't receiving updates due to differences in semantics between namedctl and /root/bin/update-named. The mechanism is scheduled to be replaced this weekend and it will no longer be an issue. Some reverse DNS entries added during that time generated the following warning which caused propagation delays on hosts with update-named: invzones/reverse/in-addr.arpa/52.134.10.in-addr.arpa.private:13: TTL set to prior TTL (3601)