Greetings ...
Just a few quick questions ... The "bogus-priv" option, does this query
the kernel IP routing table, or just the interface or subnet the IP
address or figure out what is private and which is not?
The reason I ask, is that on my firewall, I have a few subnets which I
have all bind ( no pun intended ), together with dnsmasq. Now I
currently hash out "bogus-priv" to get dns working to them, even through
I have ...
server=/nasrec.leenx.corp/10.1.1.1
server=/1.1.10.in-addr.arpa/10.1.1.1
But my route table looks like ...
10.2.2.254 0.0.0.0 255.255.255.255 UH 0 0 0
ippp2
10.1.17.248 0.0.0.0 255.255.255.248 U 0 0 0 eth1
10.1.17.240 10.1.17.250 255.255.255.248 UG 0 0 0 eth1
10.1.17.0 10.1.17.250 255.255.255.128 UG 0 0 0 eth1
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.2.2.0 10.0.0.254 255.255.255.0 UG 0 0 0 eth0
10.2.3.0 10.0.0.254 255.255.255.0 UG 0 0 0 eth0
10.1.0.0 10.0.0.254 255.255.0.0 UG 0 0 0 eth0
With six subnets under 10.1.0.0/16 ... Could, or does dnsmasq
understand or accept that 10.1.0.0/16 should be a non-bogus private
address space ...
Thanks
Mailed
Lee
