youtube.com not resolving

[#1]

This started yesterday but until then youtube had been working fine.

Now on two different PCs, I am unable to visit youtube.com.

I have tried using my local custom written dns server / resolver, plusnet HubOne and finally Google's own 8.8.4.4 dns server

As you can see every dns server used reports the same IP address - 172.217.169.78. Somehow I don't think Googles dns server.is wrong about it's own IP address for youtube.

Would somebody at plusnet please explain what is going on?

Been to downforeveryoneorjustme.com:

[#2]

Not that it helps, @7up - sorry - but I had no problem just now going via Google.

[#3]

@bobpullen @Darkfire 

come on lads... youtube is essential in this time of corona-war... whats happening?

[#4]

@7up as was said this really doesn't help you but I can get to youtube.com so to me this means that it's

A. A fault on your side

B. A local issue

C. A routing issue.

What do you get with a traceroute to the IP?

Also I get this using nslookup.

Non-authoritative answer:
Name:	youtube.com
Address: 172.217.20.142
Name:	youtube.com
Address: 2a00:1450:4009:807::200e

You could edit your hosts file and set this IP to resolve to youtube.com to see if it works. If it does then there may be an issue with the server at the address you provided.

[#5]

Well i've concluded it's not a fault at my end - not if googles own dns server at 8.8.4.4 is providing the same IP...

So I opened up another chrome window - and CTRL+Click'ed the youtube icon on my bookmarks bar repeatedly... opened up several hundred tabs... eventually chromes cache timed out and looked it up again finding 216.58.213.14 which works (I later found a way to clear chromes cache the easy way lol).

Anyway as that IP seems to work i've added it into my external domains zone on my dns server for both youtube.com and www.youtube.com.

It's a dirty hack and leaves me vulnerable to not having the latest IP if they change it but for now it's working.

[#6]

For what it's worth I get this for youtube.com:

nslookup youtube.com 8.8.4.4
Server:		8.8.4.4
Address:	8.8.4.4#53

Non-authoritative answer:
Name:	youtube.com
Address: 172.217.169.46
Name:	youtube.com
Address: 2a00:1450:4009:818::200e

and for www.youtube.com I get:

nslookup www.youtube.com 8.8.4.4
Server:		8.8.4.4
Address:	8.8.4.4#53

Non-authoritative answer:
www.youtube.com	canonical name = youtube-ui.l.google.com.
Name:	youtube-ui.l.google.com
Address: 216.58.206.142
Name:	youtube-ui.l.google.com
Address: 216.58.204.14
Name:	youtube-ui.l.google.com
Address: 216.58.204.238
Name:	youtube-ui.l.google.com
Address: 216.58.205.46
Name:	youtube-ui.l.google.com
Address: 216.58.213.14
Name:	youtube-ui.l.google.com
Address: 172.217.169.14
Name:	youtube-ui.l.google.com
Address: 172.217.169.46
Name:	youtube-ui.l.google.com
Address: 172.217.169.78
Name:	youtube-ui.l.google.com
Address: 216.58.213.110
Name:	youtube-ui.l.google.com
Address: 216.58.198.174
Name:	youtube-ui.l.google.com
Address: 216.58.210.46
Name:	youtube-ui.l.google.com
Address: 216.58.204.46
Name:	youtube-ui.l.google.com
Address: 216.58.206.110
Name:	youtube-ui.l.google.com
Address: 2a00:1450:4009:81b::200e

[#7]

---

@7up wrote:

@bobpullen @Darkfire 

come on lads... youtube is essential in this time of corona-war... whats happening?

---

Nothing, that I'm aware of

I resolve to the same IP and can access the site successfully.

Trace as below:-

>tracert 172.217.169.78

Tracing route to lhr48s09-in-f14.1e100.net [172.217.169.78]
over a maximum of 30 hops:

  1     8 ms     1 ms     1 ms  192.168.1.254
  2     8 ms     8 ms     8 ms  250.core.plus.net [195.166.130.250]
  3     8 ms     8 ms    11 ms  84.93.253.87
  4     9 ms     9 ms     9 ms  195.99.125.140
  5    10 ms    11 ms     9 ms  194.72.16.184
  6     9 ms     9 ms    12 ms  peer2-xe3-1-3.telehouse.ukcore.bt.net [109.159.253.5]
  7    10 ms    11 ms    10 ms  209.85.249.187
  8    11 ms     9 ms    11 ms  172.253.66.99
  9    10 ms     9 ms    14 ms  lhr48s09-in-f14.1e100.net [172.217.169.78]

Trace complete.

[#8]

Well there must be something going on Bob, i couldn't get 3 devices to work using that IP - my phone refused to connect too. The moment i rigged the DNS to that other IP everything could connect to youtube.

This isn't a local fault at my end.. i suppose google might have blocked an ip range on that server for whatever reason but that seems unlikely.

[#9]

A trace to the IP, as suggested by @Moot, would have been helpful. I'm not disputing something was wrong, but I'd expect more noise from a widespread issue affecting a site like YouTube.

[#10]

---

@7up wrote:

@bobpullen @Darkfire 

come on lads... ...whats happening?

Off topic, but @Darkfire hasn't worked here for some time