On 2018-03-12 19:47, Anton Aylward wrote:
On 12/03/18 01:50 PM, Per Jessen wrote:
Anton Aylward wrote:
...
and you have 127.0.0.1 as the nameserver in /etc/resolv.conf?
No. NetworkManager generates that file and that isn't in it. If I put it in there manually then when DNSMasq starts it throw it out, as I said in my original post:
In one machine (the server) I have: ... ### Please remove (at least) this line when you modify the file! search Valinor #nameserver 192.168.1.16 nameserver 127.0.0.1 and it is working, but it doesn't use network manager. In YaST network settings, I said to use "127.0.0.1", but I think I edited that file manually as well, in which case I should edit out one line - doing it now.
Mar 12 12:15:09 main.HOME.SystemI.ca dnsmasq[8005]: ignoring nameserver 127.0.0.1 - local interface
That only means that dnsmasq itself will not query 127.0.0.1 On /etc/dnsmasq.conf I have this line somewhere: #CER server=192.168.1.1 And that's it. dnsmasq queries my router for information. I might instead check what the router queries and do it myself instead: 80.58.61.250 80.58.61.254 My router has set static DNS servers, anyway, not taken from the WAN info. Done. On my laptop I have: minas-tirith:~ # cat /etc/resolv.conf # Generated by NetworkManager search valinor nameserver 127.0.0.1 minas-tirith:~ # Ie, the entire file. I don't remember if I configured network manager to do that, and I'm not in that room - I'll check later. On /etc/dnsmasq.conf I have: #CER server=8.8.8.8 server=8.8.4.4 which I do not like, but I did as I move the laptop with different ISP. The assignment to dnsmasq should be dynamic. I did that temporarily to think about later, but I forgot. The trick would be, perhaps, in this: # Change this line if you want dns to get its upstream servers from # somewhere other that /etc/resolv.conf #resolv-file= That file should list the external dns servers that dns would query, and it would be wonderful if network manager wrote it. We might also do this: # If you don't want dnsmasq to read /etc/resolv.conf or any other # file, getting its servers from this file instead (see below), then # uncomment this. #CER #no-resolv which would avoid the message about the 127.0.0.1 being ignored - but I worry about the "any other file" thing. My initials there may mean that I tried, then undid. I saw this: # Add domains which you want to force to an IP address here. # The example below send any host in double-click.net to a local # web-server. #address=/double-click.net/127.0.0.1 -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)