[Buildbot] #3133: DNS primaries don't update

[Buildbot trac]

#3133: DNS primaries don't update
---------------------+--------------------------
Reporter:  dustin    |       Owner:  dustin
    Type:  defect    |      Status:  new
Priority:  critical  |   Milestone:  sys - other
 Version:  0.8.10    |  Resolution:
Keywords:            |
---------------------+--------------------------

Comment (by dustin):

 http://www.zytrax.com/books/dns/ch7/xfer.html says

 ---

  notify yes | no | explicit;

 notify behaviour is applicable to both master zones (with 'type master;')
 and slave zones (with 'type slave;') and if set to 'yes' (the default)
 then, when a zone is loaded or changed, for example, after a zone
 transfer, NOTIFY messages are sent to the name servers defined in the NS
 records for the zone (except itself and the 'Primary Master' name server
 defined in the SOA record) and to any IPs listed in any also-notify
 statement.

 ---

 The primary in the soa is ns1.he.net.  Here's the situation:
 {{{
                                 SOA     NS      NOTIFY
 ns1.he.net       216.218.130.2  Y       Y       (on restart)
 ns2.he.net       216.218.131.2          Y
 ns3.he.net       216.218.132.2          Y       Y
 ns4.he.net       216.66.1.2             Y
 ns5.he.net       216.66.80.18           Y       Y
 slave.dns.he.net 216.218.133.2
 }}}

 So that's not really doing what it says..

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