Tue, 14 Jun 2016 13:48:56 -0500 Chris Bennett <chrisbenn...@bennettconstruction.us> > > > They both work for me also, with dig @8.8.8.8, etc. > > > Whois fails, lynx, elinks, firefox cannot connect outside > > > > > > Could this problem be because of my being behind the wifi NAT?
Could you trip the power to the wifi translating network segment? > > Compare the full output from resolving there with dig with the same > > thing ssh'd to another host (or post it here so someone else can compare). > > from OK server: > > dig bsd.org @8.8.8.8 +trace > ;; Received 149 bytes from 66.180.173.221#53(ns1.tfm.com) in 27 ms > > From problem computer: > > dig bsd.org @8.8.8.8 +trace > dig: couldn't get address for 'c.root-servers.net': not found > > Every dig here gives a different letter with problem. > j.root-servers.net or m.root-servers.net, etc > > Should I send more info? If you want, test with another set of public DNS servers, but it appears that you can't get anything back from your DNS requests going out to remote destination port 53 over UDP. You may want to test with TCP on remote port 53 as suggested by Stuart, just to confirm whether it's UDP specific or totally port 53 related.
