[nsd-users] trouble getting secondary axfr with 4.1.0
Niall O'Reilly
niall.oreilly at ucd.ie
Thu Jun 9 13:56:47 UTC 2016
On 9 Jun 2016, at 14:35, John Griessen wrote:
> DNS seems OK with one server, but attempting to us buddyns.com as
> secondary fails.
Could you be more explicit about the failure symptoms?
> zone:
> # this server is master, 104.245.34.178 is a secondary
> name: cibolo.us
> zonefile: cibolo.us.zone
> provide-xfr: 104.245.34.178 NOKEY
> # notify: 104.245.34.178 NOKEY
> # allow ALL the following addresses! BuddyNS employs them all.
> # notify: 173.244.206.26 NOKEY
> provide-xfr: 173.244.206.26 NOKEY
> # notify: 88.198.106.11 NOKEY
> provide-xfr: 88.198.106.11 NOKEY
If the failure mode you're concerned about is that the slave does
not pick up zone immediately, this could be because you've
suppressed the 'notify:' directives.
If you haven't already done so, I'ld suggest using Zonemaster or
DNSViz to verify nameserver function and identify problems.
Here are some recent results from these tools:
https://zonemaster.net/test/45360dcda345a580
http://dnsviz.net/d/cibolo.us/V1l0DQ/dnssec/
Best regards,
Niall O'Reilly
More information about the nsd-users
mailing list