[Dnsmasq-discuss] Bug report: authoritative zone transfers for PTR domains

Daniel Bromberg daniel at basezen.com
Fri Jan 31 19:52:55 GMT 2020

Hello from a list new-comer.

Consider running on the network, serving DHCP on that subnet, and wishing to publish both the forward and reverse zones to secondary caching servers: example.com <http://example.com/> and

While dnsmasq creates and serves individually the necessary PTR records given an auth-zone option:


it does not believe it's authoritative for the PTR zone.

The workaround is to add:

The logic in the startup code is simple: the authoritative zones are exactly the set encountered in the options file; nothing else is implied. What results is inconsistency, because dnsmasq essentially lies by supplying an authoritative claim via NS and SOA records on 0.0.10.in <http://0.0.10.in/>-addr.arpa then refuses to do a zone transfer.

There seems to be little interest in reverse DNS zone transfers; this workaround is not found in the manage or anywhere I could find.

On ServerFault: https://serverfault.com/questions/929891/how-to-let-dnsmasq-transfer-a-reverse-zone/1001286#1001286 <https://serverfault.com/questions/929891/how-to-let-dnsmasq-transfer-a-reverse-zone/1001286#1001286>

Kind regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20200131/f53ee013/attachment.html>

More information about the Dnsmasq-discuss mailing list