[Dnsmasq-discuss] inconsistent use of a server=/example.com/<ip_addr> specification

Brian J. Murrell brian at interlinx.bc.ca
Tue Nov 26 11:18:02 GMT 2019


On Tue, 2019-11-26 at 07:52 +0100, Which Nameserver wrote:
> 
> I hope that OP digs deeper.

Probably not.  I moved the desired behaviour to somewhere where it
works reliably, up to NetworkManager.

example.com is the domainname of a VPN connection and 10.75.22.247 is
the DNS server for that domain on that VPN.

Since NM has the ability to learn about domainnames and DNS servers
from VPN connections, and to route requests for lookups in that domain
(and the reverse domains) to the specified DNS, I just moved this
setting out of the dnsmasq configuration into the NM configuration.

The funny part is that NM is just poking these into dnsmasq using DBus:

Nov 25 17:53:00 vpn-client.example.com dnsmasq[129564]: setting upstream servers from DBus
Nov 25 17:53:00 vpn-client.example.com dnsmasq[129564]: using local addresses only for domain ilinx
Nov 25 17:53:00 vpn-client.example.com dnsmasq[129564]: using nameserver 10.75.22.247#53 for domain example.com
Nov 25 17:53:00 vpn-client.example.com dnsmasq[129564]: using nameserver 10.75.22.247#53 for domain 0.8.10.in-addr.arpa
Nov 25 17:53:00 vpn-client.example.com dnsmasq[129564]: using nameserver 10.75.22.247#53 for domain 22.75.10.in-addr.arpa

but this is working consistently and reliably where:

server=/example.com/10.75.22.247

is not.

Cheers,
b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20191126/bba61aa9/attachment-0001.sig>


More information about the Dnsmasq-discuss mailing list