Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same
result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and
then stops dead.
On Sunday, 6 March 2022 09:39:32 GMT John Covici wrote:
Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and
then stops dead.
The host name is youtube.com. The 'www' is just a prefix for humans to recognise; it has no real function any more, as far as I know.
Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same
result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and
then stops dead.
Am I doing something wrong? My windows box is doing this correctly.
Thanks in advance for any suggestions.
On 06/03/2022 09:39, John Covici wrote:
Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and
then stops dead.
Am I doing something wrong? My windows box is doing this correctly.
Thanks in advance for any suggestions.
cat /etc/hosts?
I'm sure you'd remember if you'd messed about with it, but a
redirect there would explain it ...
On Sun, 06 Mar 2022 06:18:33 -0500,
Wols Lists wrote:
On 06/03/2022 09:39, John Covici wrote:
Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and then stops dead.
Am I doing something wrong? My windows box is doing this correctly.
Thanks in advance for any suggestions.
cat /etc/hosts?
I'm sure you'd remember if you'd messed about with it, but a
redirect there would explain it ...
No joy there, it looks like anything on the web under youtube
redirects to www.youtube.com, what I can't figure out is even if I
ping it, it says name or service not known, but dig sees it.
[1 <text/plain; UTF-8 (7bit)>]Traceroute does not work, either.
On Sunday, 6 March 2022 12:27:47 GMT John Covici wrote:
On Sun, 06 Mar 2022 06:18:33 -0500,
Wols Lists wrote:
On 06/03/2022 09:39, John Covici wrote:
Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and then stops dead.
Am I doing something wrong? My windows box is doing this correctly.
Thanks in advance for any suggestions.
cat /etc/hosts?
I'm sure you'd remember if you'd messed about with it, but a
redirect there would explain it ...
No joy there, it looks like anything on the web under youtube
redirects to www.youtube.com, what I can't figure out is even if I
ping it, it says name or service not known, but dig sees it.
I don't run named, so I'm not sure if some configuration issue is at play with
your setup. Did you try traceroute? I am able to ping 'www.youtube.com' as well as 'youtube.com'. They resolve to different IPv4 addresses, but the same
IPv6. When I run traceroute the route deviates 3 hops before the target, whether I use ICMP, or TCP on ports 80 and 443.
Therefore it seems there is a URL redirect on youtube. When tested from here the redirection is not on the same webserver, but to some other server/farm hidden behind Google's vast estate and reverse proxies. The routing from your
network to Google would be specific to your location.
Traceroute does not work, either.
On Sun, 06 Mar 2022 05:20:07 -0500,
Peter Humphrey wrote:
On Sunday, 6 March 2022 09:39:32 GMT John Covici wrote:
Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and then stops dead.
The host name is youtube.com. The 'www' is just a prefix for humans to recognise; it has no real function any more, as far as I know.
Well, if I try to go to anything on youtube with the browser, it
redirects to www.youtube.com which is not accessible, except using
dig.
On Sun, 06 Mar 2022 06:18:33 -0500,
Wols Lists wrote:
On 06/03/2022 09:39, John Covici wrote:
Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and then stops dead.
Am I doing something wrong? My windows box is doing this correctly.
Thanks in advance for any suggestions.
cat /etc/hosts?
I'm sure you'd remember if you'd messed about with it, but a
redirect there would explain it ...
No joy there, it looks like anything on the web under youtube
redirects to www.youtube.com, what I can't figure out is even if I
ping it, it says name or service not known, but dig sees it.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
covici@ccs.covici.com
On Sun, Mar 6, 2022 at 9:01 AM John Covici <covici@ccs.covici.com> 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.)
On Sunday, 6 March 2022 11:07:54 GMT John Covici wrote:If I could get ping or host to work, I would go further. I have lynx
On Sun, 06 Mar 2022 05:20:07 -0500,
Peter Humphrey wrote:
On Sunday, 6 March 2022 09:39:32 GMT John Covici wrote:
Hi. On my gentoo box, no application including ping can access www.youtube.com. However, a dig is doing it correctly, so I can not understand what is happening. A restart of named, gives me the same result. This is very baffling to me. If I change the URL to just youtube.com, it tries to work till the redirect to www.youtube.com and then stops dead.
The host name is youtube.com. The 'www' is just a prefix for humans to recognise; it has no real function any more, as far as I know.
Well, if I try to go to anything on youtube with the browser, it
redirects to www.youtube.com which is not accessible, except using
dig.
Which browser? The ones I've tried would first try youtube.com, and if that fails name lookup it will try prepending www. That may happen too fast for you
to notice, though.
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 <covici@ccs.covici.com> 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?
On Sun, 06 Mar 2022 09:23:58 -0500,
Rich Freeman wrote:
On Sun, Mar 6, 2022 at 9:01 AM John Covici <covici@ccs.covici.com> 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
On Sun, Mar 6, 2022 at 12:20 PM John Covici <covici@ccs.covici.com> wrote:
OK, I discovered that if I add 8.8.8.8 to my resolv.conf,
www.youtube.com becomes accessible. I would like not to have either
google or cloudflare in there, if I can avoid them -- they were
blocking some places I wanted to go to with a 521 error code. So, the mystery deepens.
Actually, it got a lot simpler. You ruled out host, nsswitch, etc
issues. This is just a DNS server issue. Run:
dig www.youtube.com @8.8.8.8
dig www.youtube.com @127.0.0.1
dig www.youtube.com @198.7.0.5
All three should resolve something reasonable (it is ok if they don't
resolve the same - load balancing/etc can result in that). If any
fail to resolve then that DNS server has issues. At that point you
need to check the config on that DNS server.
On Sun, Mar 6, 2022 at 9:01 AM John Covici <covici@ccs.covici.com> 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.)
OK, I discovered that if I add 8.8.8.8 to my resolv.conf,
www.youtube.com becomes accessible. I would like not to have either
google or cloudflare in there, if I can avoid them -- they were
blocking some places I wanted to go to with a 521 error code. So, the mystery deepens.
On Sun, Mar 6, 2022 at 12:20 PM John Covici <covici@ccs.covici.com> wrote:
OK, I discovered that if I add 8.8.8.8 to my resolv.conf,
www.youtube.com becomes accessible. I would like not to have either
google or cloudflare in there, if I can avoid them -- they were
blocking some places I wanted to go to with a 521 error code. So, the mystery deepens.
Actually, it got a lot simpler. You ruled out host, nsswitch, etc
issues. This is just a DNS server issue. Run:
dig www.youtube.com @8.8.8.8
dig www.youtube.com @127.0.0.1
dig www.youtube.com @198.7.0.5
All three should resolve something reasonable (it is ok if they don't
resolve the same - load balancing/etc can result in that). If any
fail to resolve then that DNS server has issues. At that point you
need to check the config on that DNS server.
OK, I discovered that if I add 8.8.8.8 to my resolv.conf,
www.youtube.com becomes accessible. I would like not to have either
google or cloudflare in there, if I can avoid them -- they were
blocking some places I wanted to go to with a 521 error code. So, the mystery deepens.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 153:28:48 |
Calls: | 10,383 |
Files: | 14,054 |
Messages: | 6,417,839 |