[Buildbot] #3133: DNS primaries don't update
Buildbot trac
trac at buildbot.net
Thu Jan 1 01:00:21 UTC 2015
#3133: DNS primaries don't update
---------------------+-------------------------
Reporter: dustin | Owner: dustin
Type: defect | Status: new
Priority: critical | Milestone: sys - other
Version: 0.8.10 | Keywords:
---------------------+-------------------------
From tcpdump, when running `rndc notify buildbot.net`:
{{{
00:55:15.429274 IP 140.211.10.236.53378 > 216.218.132.2.53: 5429 notify
[b2&3=0x2400] [1a] SOA? buildbot.net. (84)
00:55:15.429446 IP 140.211.10.236.53378 > 216.66.80.18.53: 18120 notify
[b2&3=0x2400] [1a] SOA? buildbot.net. (84)
}}}
which is certainly not the entire set of notifies it should be sending -
it's 2 out of the 6.
I'm not sure why this would be the case, as the config says
{{{
acl "buildbot.net-upstream" {
// slave address -- slave.dns.he.net
// per dns.he.net documentation
216.218.130.2;
216.218.131.2;
216.218.132.2;
216.218.133.2;
216.66.1.2;
216.66.80.18;
};
zone "buildbot.net" {
type master;
file "/usr/local/etc/namedb/master/buildbot.net";
allow-transfer {
"buildbot.net-upstream";
};
notify explicit;
also-notify {
216.218.130.2;
216.218.131.2;
216.218.132.2;
216.218.133.2;
216.66.1.2;
216.66.80.18;
};
};
}}}
(incidentally, we should probably configure those using something similar
to the `secondaries` variable -- or remove the `secondaries` variable)
I'm sure there's some BINDish reason for this -- I just don't know what it
is.
--
Ticket URL: <http://trac.buildbot.net/ticket/3133>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the bugs
mailing list