My networking is clearly bollixed, but I can't figure out how:
derek@vinka:~$ nslookup google.com
;; connection timed out; no servers could be reached
derek@vinka:~$ curl google.com
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>
Surely, if I can't look up a domain, I shouldn't be able to browse to it. Can anybody explain what's going on here?
tracepath
is also just a long series of either ???
or no reply
responses.
(fwiw, everything was working, but I'm trying to change my secondary router—on a 50' ethernet cable—connected to the cable modem/router to become an AP on the same subnet, instead of being a router on its own subnet)
derek@vinka:~$ env | grep -i proxy
derek@vinka:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 vinka
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
derek@vinka:~$
derek@vinka:~$ nslookup
> server
Default server: 127.0.1.1
Address: 127.0.1.1#53
Interestingly, I get the same result from a system running NetworkManager and another running Connmand.
If I lookup through my router (nslookup host 192.168.0.1
), I still can't get any resolutions, but browsers/curl/wget always work on my laptop, my raspberry Pi media server, and my phone—all of them running different OSes.
What about /etc/nsswitch?
derek@vinka:~$ grep hosts /etc/nsswitch.conf
hosts: files mdns4_minimal dns [NOTFOUND=return] resolve [!UNAVAIL=return] dns
Clearly that last dns
is redundant, but it looks right, otherwise.
derek@vinka:~$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.1.1
On my media server:
derek@nas ~ $ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver 127.0.0.1
env | grep -i proxy
.systemd
strikes again. This time it'ssystemd-resolve
.