 cob_1310nm Of GoodnessPremium
join:2003-07-08
Tulsa, OK
 ·AT&T U-Verse
| reply to HelpPlz
Re: Youtube sucks for me I've done some more packet capturing, here's a larger list of bad hosts. The loopback addresses are in place because I'm adding them to my hosts file as I encounter them. I didn't trace to all of them, but I assume they have the extra 2 hops after the AT&T > Google handoff we've seen with the previous ones.
127.0.0.1 r20---sn-q4f7dnee.c.youtube.com
127.0.0.1 r18---sn-q4f7dnez.c.youtube.com
127.0.0.1 r9---sn-q4f7dney.c.youtube.com
127.0.0.1 r14---sn-q4f7dnle.c.youtube.com
127.0.0.1 r20---sn-q4f7dnez.c.youtube.com
127.0.0.1 r2---sn-q4f7dnle.c.youtube.com
127.0.0.1 r9---sn-q4f7dnse.c.youtube.com
127.0.0.1 r5---sn-q4f7dnl6.c.youtube.com
127.0.0.1 r17---sn-q4f7dnle.c.youtube.com
127.0.0.1 r6---sn-q4f7dnle.c.youtube.com
127.0.0.1 r9---sn-q4f7dne7.c.youtube.com
127.0.0.1 r5---sn-q4f7dnse.c.youtube.com
127.0.0.1 r8---sn-q4f7dne7.c.youtube.com
--
"No matter how hard you push and no matter what the priority, you can't increase the speed of light."
- RFC 1925 |
|
|
|
| I also observed some of these servers having an issue. I'd suspect it has to do w/ the peering (although it appears to be post AT&T handoff).
Either way, null routing that list appears to have helped and I'll continue to monitor this thread until we get something better than a band-aid figured out  |
|
| reply to cob_
Thanks for the tip about blocking youtube servers. Blocking this one worked for me.
127.0.0.1 r1---sn-vgqelnez.c.youtube.com |
|
| Note there are a lot of people who suggest using 0.0.0.0 in the hosts file instead of 127.0.0.1. Some say there is no advantage to 0.0.0.0, but I have not seen anybody say that 0.0.0.0 has a disadvantage. |
|
