Allegedly, on or about 24 June 2016, Rick Stevens sent: > Recheck the /etc/resolv.conf file to see if you have any additional > nameservers defined. If not, then you COULD add 8.8.8.8 to the > "Additional DNS servers" section of the NM config and do another > NM restart. The thing that bothers me is that the DHCP stuff is not > giving you any nameservers to use other than the router and that the > machine it is giving you (192.168.1.1) isn't acting like a resolver > itself and it should if it doesn't pass along any nameservers. > > The vast majority of wireless routers pass through the DNS servers > they get from their ISP upstream providers. The WAN side of your > wireless router gets its IP via DHCP from your ISP along with > nameservers to use. It usually passes those nameservers along to ITS > DHCP clients on the LAN side of things. If not, they run a caching > name server or proxy that the LAN DHCP clients use. Routers usually upstream your request to the ISP's DNS servers to resolve, *but*... I've found many ISPs DNS servers to be awful (*), you can be better off to run one properly, yourself, or configure your router to use an external reliable one *instead* of your ISPs. Then, all the other equipment on a LAN will just work without any fuss. * (Slow, overworked, sometimes timing out, sometimes never having answers queries. On one ISP, on of the biggest in the country, their own DNS servers rarely had answers to their own equipment hostnames.) Sometimes ISPs re-jig their servers, and put them on other IPs, but don't bother to update their DHCP servers, or you're still on an old lease and hadn't found out about the new ones, yet. Or, they have several DNS servers and dole out different ones to different clients as they connect, and some of the DNS servers don't work too well. With dial-up, hanging up and re-connecting would often work past that malarkey, but changing your IP (and other assigned addresses) is harder to do with broadband, where you usually get the same IP each connection. I gave up on my ISP's DNS servers many years ago, and ran my own DNS server for the last three ISPs that I've been with. It saved me a lot of pain. Since I run the DNS and DHCP servers on a computer, rather than the router, it made it very easy for me to do things exactly the way that I wanted. This is one potential problem with using a non-ISP DNS server, in that some ISPs only put the data for their own POP and IMAP mail servers, for example, into their own DNS server. Or have different IPs to give to internally connected to clients to outside users. If you don't use their data to try connecting to thing, things fail to work in peculiar ways. These days, I run my own DNS server, and have the router as the forwarder for other queries (which will automatically use my ISP's current DNS server). As a forwarder, it answers queries the usual servers don't know about. Adding a second DNS server to the computer's configuration (DHCP or NetworkManager), doesn't quite work the same way, there's a long timeout before the second DNS server is used, and only if the first one doesn't respond. If the first one does respond, even if it doesn't have an answer, it has responded, and the second one will not be consulted. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. I don't think it's pure coincidence that "officialdom" sounds the same as "official dumb." -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
