Re: Can't find the DNS Servers
- Date: Wed, 4 Oct 2017 11:55:11 -0500
- From: David Wright <deblis@xxxxxxxxxxxxxxxxx>
- Subject: Re: Can't find the DNS Servers
On Wed 04 Oct 2017 at 08:38:10 (-0400), Greg Wooledge wrote:
> On Tue, Oct 03, 2017 at 04:47:35PM -0700, Gary Roach wrote:
> > Symptoms: Any package that needs access to the network sends an error
> > message indicating that it doesn't have access to the internet. Ping doesn't
> > work for names but does for ip addresses. All ip addresses both local and
> > global.
> Show, don't tell.
> > In short, there doesn't seem to be any access to a name server. My believe
> > that my Actiontec router at 192.168.1.1 also acts as a name server.
> In your diagnostic command-and-response session, be sure to include
> the results of your attempts to ping your nameserver by IP address,
> and of performing a DNS lookup using that nameserver. See examples
> In the event that one of the commands does not work as expected, it's
> helpful to try alternatives. E.g. if you can't do name resolutions
> through 192.168.1.1 then try through 22.214.171.124.
> Most plastic routers don't run their own nameserver; instead, they just
> forward your DNS requests to your ISP's nameservers, which may or may
> not be functional on any given day. So, if 192.168.1.1 fails but
> 126.96.36.199 works, then you know you're going to need to go down the road
> of changing what resolv.conf contains to something usable, a topic upon
> which we've already had a massive discussion within this thread.
> If both 192.168.1.1 and 188.8.131.52 fail, then you may be facing a firewall
> or routing issue.
Last time this came up with this OP, the discussion of whether routers
contain DNS servers ran into the sand unanswered, though the paucity
of lines in their /etc/hosts (localhost plus those allnodes/routers)
seemed to suggest that this one (if it's still the same one) might.