My laptop is running bionic, was running artful and I completed a full upgrade via apt a few weeks ago and everything is working as expected, but when I try and connect to my nas the FQDN is not resolved, I can connect via IP etc. I have done a fair amount of reading, had to catch up on the huge changes that have happened to Linux since I last worked with redhat linux in 2003.
So we now have network manager and systemd, these are pretty big changes from the old unix way of doing things and I can see the reasons for the evolution that has taken place, just makes it tricky to trouble shoot if you are an older Unix person ;-) The systemd resolver can be swapped out for dnsmasq and network manager has a plugin that works with dnsmasq, ok get all of the that no problem. What I can't fathom is, why out of the box, Ubuntu is not correctly forwarding the dns lookup to my router, which is able to provide static dns entries for certain services on my network. This works perfectly with windows and macos.
In an attempt to resolve this, it wasn't working correctly with the systemd resolver, I have swapped it out for dnsmasq, still no cigar :-/
The laptop picks up an IP via dhcp correctly and network manager correctly populates /etc/resolv.conf with the routers IP for dns.
Normal internet dns resolution is working correctly and if I turn off the automatic dns resolver entry provided by network manager, /etc/resolv.conf has no entry and internet dns breaks as expected. This also proves that my laptop is also forwarding dns queries it can't resolve locally.
I am at a complete loss as to what is wrong, any guidance on possible qwerks with network manager and/or dnsmasq would be gratefully appreciated. Also if anyone has a link to a really good technical deep dive on linux DNS 2016/17 that would be of great help.