On Sun, 06 Mar 2022 12:03:15 -0500,
Rich Freeman wrote:
>
> On Sun, Mar 6, 2022 at 11:49 AM Michael <[email protected]> wrote:
> >
> > On Sunday, 6 March 2022 16:34:21 GMT John Covici wrote:
> > > On Sun, 06 Mar 2022 09:23:58 -0500,
> > >
> > > Rich Freeman wrote:
> > > > On Sun, Mar 6, 2022 at 9:01 AM John Covici <[email protected]>
> > > > wrote:
> > > > > Traceroute does not work, either.
> > > >
> > > > Can you elaborate on what "does not work" means, both for traceroute and
> > > > ping?
> > > >
> > > > This is sounding like a name resolution issue. Dig will directly
> > > > query the name server you point it at. Traceroute or ping will use
> > > > the C resolver.
> > > >
> > > > Places this could go wrong include:
> > > > /etc/hosts
> > > > /etc/host.conf
> > > > /etc/nsswitch.conf
> > > > /etc/resolv.conf
> > > >
> > > > (And that is just off the top of my head.)
> > >
> > > ping www.youtube.com
> > > ping: www.youtube.com: Name or service not known
> > >
> > > Same exact result for traceroute .
> > > Here is my /etc/resolv.conf
> > > nameserver 127.0.0.1
> > > nameserver 198.7.0.5
> >
> > Did you try to compare 'dig +trace' output for the two different URLs with
> > and
> > without @8.8.8.8 as the DN resolver, to see how the responses to your local
> > setup differ?
>
> Specifically, run the dig @127.0.0.1 and @198.7.0.5 and compare that
> with @8.8.8.8. If some of those fail then there is a DNS server
> problem of some sort. If they're all consistent, I'd check nsswitch
> and the other files to ensure DNS is even being used.
Well, what is strange is that 127.0.0.1 works fine, but 198.7.0.5
does not .
Here is the output
dig +trace www.youtube.com @198.7.0.5
; <<>> DiG 9.16.25 <<>> +trace www.youtube.com @198.7.0.5
;; global options: +cmd
;; Received 56 bytes from 198.7.0.5#53(198.7.0.5) in 20 ms
and that is all I get.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
[email protected]
