On 12/03/18 02:08 PM, Lew Wolfgang wrote:
What exactly is in your /etc/resolv.conf? it is generated by the Networkmanager
The only nameserver entry should be:
nameserver localhost
You should put "nameserver 8.8.8.8" into another file, maybe /etc/resolv.wan, then point to that file in /etc/dnsmasq.conf:
resolv-file=/etc/resolv.wan
Instead of it using /etc/resolv.conf ? The MAN page says -r, --resolv-file=<file> Read the IP addresses of the upstream nameservers from <file>, instead of /etc/resolv.conf. Are you trying to say that the resolution path, when called by an application, goes gethostbyname -> /etc/resolv.conf -> localhost -> (alias) 127.0.0.1 -> DNSMasq listens on 127.0.0.1 -> DNSmasq gets file /etc/resolv.wan -> 8.8.8.8 Sorry, I don't see the point of the extra indirection. I note that the *applications* are guided by /etc/nsswitch.conf Mabye that is what matters?
But why not just put your "127.0.0.1 server-13-33-160-47.ord50.r.cloudfront.net" directly into /etc/hosts? That should work well, no muss nor fuss.
Along with the other 24619 addresses that I currently have, seperately, in /etc/dnsmasq.d/block.hosts.txt ? No, I don't think so. And anyway, it gets clobbered on reboot by NetworkManager.
But what happens when your advert supplier moves to a different host? Have you tried uBlock Origin in your browser?
Regards, Lew
-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org