<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1513757070965_11863">Why is this happening? I am an average user trying to get to the <a href="http://www.gnu.org/" id="yui_3_16_0_ym19_1_1513757070965_16653">www.gnu.org</a> website. I have no problem with any other website at the moment. I have spent hours googling and asking questions on forums trying to solve this problem. But I do not know how to resolve this. I have tried different solutions only to get myself into more trouble. I am using Ubuntu 17.04 64bit which is a new installation with very few additions. I do have Ghostery and a Ad Blocker on both browsers (firefox and chrome) but there is no effect with them enabled or disabled.<br></div><div id="yui_3_16_0_ym19_1_1513757070965_26335">So here is where I am up to:<br></div><div id="yui_3_16_0_ym19_1_1513757070965_26333">So many resolv.conf files in different folders /etc, /etc/systemd, run/systemd/resolve, run/resolvconf and so many other places I dont know about. Why is it not mentioned in the manual pages how to configure them manual or automatically? So many people have different ideas on how to correct this problem online that my head hurts!</div><div id="yui_3_16_0_ym19_1_1513757070965_29545">I have change one file at /etc/systemd/resolv.conf without any effort on the problem. Set DNSSEC=off and added google DNS servers.<br></div><div id="yui_3_16_0_ym19_1_1513757070965_40807">Now I will show you the output I am currently dealing with, for which I do not have an answer to.</div><div id="yui_3_16_0_ym19_1_1513757070965_40828" dir="ltr">// Where is this config status stored??? In /etc/systemd/resolv.conf ???<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_76566">$ systemd-resolve --status</div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_44358"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_42712">Global<br id="yui_3_16_0_ym19_1_1513757070965_41030"> DNSSEC NTA: 10.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41031"> 16.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41032"> 168.192.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41033"> 17.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41034"> 18.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41035"> 19.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41036"> 20.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41037"> 21.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41038"> 22.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41039"> 23.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41040"> 24.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41041"> 25.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41042"> 26.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41043"> 27.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41044"> 28.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41045"> 29.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41046"> 30.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41047"> 31.172.in-addr.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41048"> corp<br id="yui_3_16_0_ym19_1_1513757070965_41049"> d.f.ip6.arpa<br id="yui_3_16_0_ym19_1_1513757070965_41050"> home<br id="yui_3_16_0_ym19_1_1513757070965_41051"> internal<br id="yui_3_16_0_ym19_1_1513757070965_41052"> intranet<br id="yui_3_16_0_ym19_1_1513757070965_41053"> lan<br id="yui_3_16_0_ym19_1_1513757070965_41054"> local<br id="yui_3_16_0_ym19_1_1513757070965_41055"> private<br id="yui_3_16_0_ym19_1_1513757070965_41056"> test<br id="yui_3_16_0_ym19_1_1513757070965_41057"><br id="yui_3_16_0_ym19_1_1513757070965_41058">Link 2 (enp4s0)<br id="yui_3_16_0_ym19_1_1513757070965_41059"> Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6<br id="yui_3_16_0_ym19_1_1513757070965_41060"> LLMNR setting: yes<br id="yui_3_16_0_ym19_1_1513757070965_41061">MulticastDNS setting: no<br id="yui_3_16_0_ym19_1_1513757070965_41062"> DNSSEC setting: no<br id="yui_3_16_0_ym19_1_1513757070965_41063"> DNSSEC supported: no<br id="yui_3_16_0_ym19_1_1513757070965_41064"> DNS Servers: 192.168.0.1<br id="yui_3_16_0_ym19_1_1513757070965_41065"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_44364">---------------------------------------------------------------<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_44359">//Why is it not looking at my router IP address? (192.168.0.1)<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_62109">//Yet with IP address of gnu.org I have success! Why?<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_62123">$ nslookup 208.118.235.148</div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_44370">Server: 127.0.0.53<br id="yui_3_16_0_ym19_1_1513757070965_41068">Address: 127.0.0.53#53<br id="yui_3_16_0_ym19_1_1513757070965_41069"><br id="yui_3_16_0_ym19_1_1513757070965_41070">Non-authoritative answer:<br id="yui_3_16_0_ym19_1_1513757070965_41071">148.235.118.208.in-addr.arpa name = wildebeest.gnu.org.<br id="yui_3_16_0_ym19_1_1513757070965_41072"><br id="yui_3_16_0_ym19_1_1513757070965_41073">Authoritative answers can be found from:<br id="yui_3_16_0_ym19_1_1513757070965_41074">-------------------------------------------------------------------------<br id="yui_3_16_0_ym19_1_1513757070965_41075"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_58899">//Yet the standard name lookup failed! Why?</div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_79778">//Still not my router IP address!<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_58901">$ nslookup gnu.org</div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_44374">Server: 127.0.0.53<br id="yui_3_16_0_ym19_1_1513757070965_41077">Address: 127.0.0.53#53<br id="yui_3_16_0_ym19_1_1513757070965_41078"><br id="yui_3_16_0_ym19_1_1513757070965_41079">** server can't find gnu.org: SERVFAIL<br id="yui_3_16_0_ym19_1_1513757070965_41080"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_52444"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_58898">------------------------------------------------------------------------<br id="yui_3_16_0_ym19_1_1513757070965_41081"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_45983">//Told to do this and got SERVFAIL</div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_55653">$ dig zeus2<br id="yui_3_16_0_ym19_1_1513757070965_41082"><br id="yui_3_16_0_ym19_1_1513757070965_41083">; <<>> DiG 9.10.3-P4-Ubuntu <<>> zeus2<br id="yui_3_16_0_ym19_1_1513757070965_41084">;; global options: +cmd<br id="yui_3_16_0_ym19_1_1513757070965_41085">;; Got answer:<br id="yui_3_16_0_ym19_1_1513757070965_41086">;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 29581<br id="yui_3_16_0_ym19_1_1513757070965_41087">;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1<br id="yui_3_16_0_ym19_1_1513757070965_41088"><br id="yui_3_16_0_ym19_1_1513757070965_41089">;; OPT PSEUDOSECTION:<br id="yui_3_16_0_ym19_1_1513757070965_41090">; EDNS: version: 0, flags:; udp: 65494<br id="yui_3_16_0_ym19_1_1513757070965_41091">;; QUESTION SECTION:<br id="yui_3_16_0_ym19_1_1513757070965_41092">;zeus2. IN A<br id="yui_3_16_0_ym19_1_1513757070965_41093"><br id="yui_3_16_0_ym19_1_1513757070965_41094">;; Query time: 868 msec<br id="yui_3_16_0_ym19_1_1513757070965_41095">;; SERVER: 127.0.0.53#53(127.0.0.53)<br id="yui_3_16_0_ym19_1_1513757070965_41096">;; WHEN: Wed Dec 20 07:48:41 AEDT 2017<br id="yui_3_16_0_ym19_1_1513757070965_41097">;; MSG SIZE rcvd: 34<br id="yui_3_16_0_ym19_1_1513757070965_41098"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_45984">----------------------------------------------------------------------------------------</div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_54067">//My router ip address gave me a good response, i think?<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_57265"><br id="yui_3_16_0_ym19_1_1513757070965_41099"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_45986">$ dig @192.168.0.1 zeus2.lan<br id="yui_3_16_0_ym19_1_1513757070965_41100"><br id="yui_3_16_0_ym19_1_1513757070965_41101">; <<>> DiG 9.10.3-P4-Ubuntu <<>> @192.168.0.1 zeus2.lan<br id="yui_3_16_0_ym19_1_1513757070965_41102">; (1 server found)<br id="yui_3_16_0_ym19_1_1513757070965_41103">;; global options: +cmd<br id="yui_3_16_0_ym19_1_1513757070965_41104">;; Got answer:<br id="yui_3_16_0_ym19_1_1513757070965_41105">;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56529<br id="yui_3_16_0_ym19_1_1513757070965_41106">;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1<br id="yui_3_16_0_ym19_1_1513757070965_41107"><br id="yui_3_16_0_ym19_1_1513757070965_41108">;; OPT PSEUDOSECTION:<br id="yui_3_16_0_ym19_1_1513757070965_41109">; EDNS: version: 0, flags:; udp: 4096<br id="yui_3_16_0_ym19_1_1513757070965_41110">;; QUESTION SECTION:<br id="yui_3_16_0_ym19_1_1513757070965_41111">;zeus2.lan. IN A<br id="yui_3_16_0_ym19_1_1513757070965_41112"><br id="yui_3_16_0_ym19_1_1513757070965_41113">;; AUTHORITY SECTION:<br id="yui_3_16_0_ym19_1_1513757070965_41114">. 74527 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017121901 1800 900 604800 86400<br id="yui_3_16_0_ym19_1_1513757070965_41115"><br id="yui_3_16_0_ym19_1_1513757070965_41116">;; Query time: 289 msec<br id="yui_3_16_0_ym19_1_1513757070965_41117">;; SERVER: 192.168.0.1#53(192.168.0.1)<br id="yui_3_16_0_ym19_1_1513757070965_41118">;; WHEN: Wed Dec 20 07:50:10 AEDT 2017<br id="yui_3_16_0_ym19_1_1513757070965_41119">;; MSG SIZE rcvd: 113<br id="yui_3_16_0_ym19_1_1513757070965_41120">-----------------------------------------------------------------------------------------------------------</div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_45999">This is where I am up to and i need some guidance how to proceed.<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_50824">Any help with this dilemma would be most appreciated.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1513757070965_49216"> <br></div></div></body></html>