#461054 dnsmasq: bogus-priv option could exempt forwarding to private nameservers

Package:
dnsmasq
Source:
dnsmasq
Submitter:
Tim Retout
Date:
2010-01-16 00:18:26 UTC
Severity:
wishlist
#461054#5
Date:
2008-01-16 10:50:48 UTC
From:
To:
We have nameservers handling separate private subnets, and 'server'
lines in dnsmasq.conf to forward requests to them, like:

	server=/2.168.192.in-addr.arpa/192.168.2.1
	server=/company.lan/192.168.2.1

However, to get reverse lookups working for this private subnet, I have
to turn off the 'bogus-priv' option. I expect this means that reverse
lookups for other private ranges could get forwarded to external DNS
servers.

It might be better if the bogus-priv option took account of any 'server'
in-addr.arpa lines for private subnets, and allowed forwarding in these
cases.

There was a similar request on the dnsmasq-discuss mailing list in 2005:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2005q2/000272.html
#461054#10
Date:
2008-01-16 14:34:26 UTC
From:
To:
Tim Retout wrote:

It is possible to get the same effect for the unwanted private ranges
like so:

local=/127.in-addr.arpa/
local=/10.in-addr.arpa/
local=/16.172.in-addr.arpa/
local=/17.172.in-addr.arpa/
local=/18.172.in-addr.arpa/
.
.
local=/31.172.in-addr.arpa/
local=/254.169.in-addr.arpa/


A little clumsy, but a reasonable workaround for a fairly rare situation.

Cheers,

Simon.