On Tue, Nov 26, 2019 at 06:18:02AM -0500, Brian J. Murrell wrote: > On Tue, 2019-11-26 at 07:52 +0100, Which Nameserver wrote: > > > } But NOT what might be causing the inconsistancy. > > 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. >
If hidding inconsistency in NM makes one happy, then is one happy. Feel free to report the strange inconsistency again. Karma bonuspoints for querying the nearby NS. Groeten Geert Stappers -- Leven en laten leven _______________________________________________ Dnsmasq-discuss mailing list [email protected] http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
