Tim Retout wrote: > Package: dnsmasq > Version: 2.35-1 > Severity: wishlist > > 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 > > > -- System Information: > Debian Release: 4.0 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.18-5-amd64 > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > > Versions of packages dnsmasq depends on: > ii adduser 3.102 Add and remove users and groups > ii libc6 2.3.6.ds1-13etch4 GNU C Library: Shared libraries > ii libdbus-1-3 1.0.2-1 simple interprocess messaging > syst > ii netbase 4.29 Basic TCP/IP networking system > > dnsmasq recommends no packages. > > -- no debconf information > > >
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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
