| 1 |
On Sun, Mar 6, 2022 at 11:49 AM Michael <confabulate@××××××××.com> wrote: |
| 2 |
> |
| 3 |
> On Sunday, 6 March 2022 16:34:21 GMT John Covici wrote: |
| 4 |
> > On Sun, 06 Mar 2022 09:23:58 -0500, |
| 5 |
> > |
| 6 |
> > Rich Freeman wrote: |
| 7 |
> > > On Sun, Mar 6, 2022 at 9:01 AM John Covici <covici@××××××××××.com> wrote: |
| 8 |
> > > > Traceroute does not work, either. |
| 9 |
> > > |
| 10 |
> > > Can you elaborate on what "does not work" means, both for traceroute and |
| 11 |
> > > ping? |
| 12 |
> > > |
| 13 |
> > > This is sounding like a name resolution issue. Dig will directly |
| 14 |
> > > query the name server you point it at. Traceroute or ping will use |
| 15 |
> > > the C resolver. |
| 16 |
> > > |
| 17 |
> > > Places this could go wrong include: |
| 18 |
> > > /etc/hosts |
| 19 |
> > > /etc/host.conf |
| 20 |
> > > /etc/nsswitch.conf |
| 21 |
> > > /etc/resolv.conf |
| 22 |
> > > |
| 23 |
> > > (And that is just off the top of my head.) |
| 24 |
> > |
| 25 |
> > ping www.youtube.com |
| 26 |
> > ping: www.youtube.com: Name or service not known |
| 27 |
> > |
| 28 |
> > Same exact result for traceroute . |
| 29 |
> > Here is my /etc/resolv.conf |
| 30 |
> > nameserver 127.0.0.1 |
| 31 |
> > nameserver 198.7.0.5 |
| 32 |
> |
| 33 |
> Did you try to compare 'dig +trace' output for the two different URLs with and |
| 34 |
> without @8.8.8.8 as the DN resolver, to see how the responses to your local |
| 35 |
> setup differ? |
| 36 |
|
| 37 |
Specifically, run the dig @127.0.0.1 and @198.7.0.5 and compare that |
| 38 |
with @8.8.8.8. If some of those fail then there is a DNS server |
| 39 |
problem of some sort. If they're all consistent, I'd check nsswitch |
| 40 |
and the other files to ensure DNS is even being used. |
| 41 |
|
| 42 |
-- |
| 43 |
Rich |
Archives