[Dnsmasq-discuss] Zone transfer fails without any error
Simon Kelley
simon at thekelleys.org.uk
Fri Aug 3 15:24:55 BST 2018
On 03/08/18 13:16, Wojtek Swiatek wrote:
>
>
> Le ven. 3 août 2018 à 14:06, Simon Kelley <simon at thekelleys.org.uk
> <mailto:simon at thekelleys.org.uk>> a écrit :
>
>
> What's the result of doing
>
> dig @192.168.0.10 <http://192.168.0.10> SOA swtk.info <http://swtk.info>
>
>
> It looks like that could be what's failing, rather than the actual zone
> transfer.
>
>
> Hello Simon
>
> After one night spent on the subject I finally managed this morning to
> have it working (and finally read the man page from beginning to end :))
>
> I think that what worked was to add to the config file
>
> auth-zone=swtk.info <http://swtk.info>
> auth-sec-servers=rpi-dmz
>
> and define rpi-dmz in /etc/hosts
>
> Before I had only
>
> auth-sec-servers=192.168.0.13
>
> which was probably not enough on its own (the docs suggested that
> parameter for zone transfers).
>
> The transfer works but unfortunately the serial is not updated when I
> make changes (by adding hosts to /etc/hosts for instance, and maybe when
> the IPs provided by dnsmasq change (I do not know yet)). It stays at 1.
> I have to manually delete the zone on the slave to have it
> re-transferred upon changes.
>
> Not being sure of the right etiquette for this list: should i send a new
> email with that question?
>
> Thank you for your help!
> Wojtek
>
>
I'm happy to answer the second question here.
After you've made changes to /etc/hosts, you need to send SIGHUP to the
dnsmasq process to get it to re-read the file. That should also
increment the serial. Changes to DHCP allocated addresses should also
increment the serial.
Cheers,
Simon.
More information about the Dnsmasq-discuss
mailing list