Disregard this. You can not stop youtube at Layer 3. Or you will lose Google pretty much.
Sorry. On Thu, Oct 4, 2012 at 1:12 PM, Steven Miano <[email protected]> wrote: > I'm confused as to why it would block the Google DNS servers (which I > believe are 8.8.8.8 and 8.8.4.4 unless they have more? resolve to): > > 8.8.8.8.in-addr.arpa. 43194 IN PTR > google-public-dns-a.google.com. > > My results to both of our suggestions seem to be identical. Very > interesting that we get completely different results though. :-) > > [mianosm@dev ~]$ host youtube.com | awk '/has address/ {print $NF}' > 173.194.37.100 > 173.194.37.105 > 173.194.37.96 > 173.194.37.104 > 173.194.37.102 > 173.194.37.101 > 173.194.37.99 > 173.194.37.110 > 173.194.37.98 > 173.194.37.103 > 173.194.37.97 > [mianosm@dev ~]$ dig youtube.com | egrep youtube.com | awk '{ print $5 }' > | grep -v '<<' | grep . > 173.194.37.100 > 173.194.37.105 > 173.194.37.96 > 173.194.37.104 > 173.194.37.102 > 173.194.37.101 > 173.194.37.99 > 173.194.37.110 > 173.194.37.98 > 173.194.37.103 > 173.194.37.97 > > > On Thu, Oct 4, 2012 at 11:27 AM, Chris Schanzle <[email protected]> wrote: > >> On 10/04/2012 09:58 AM, Steven Miano wrote: >> >>> dig youtube.com <http://youtube.com> | egrep youtube.com < >>> http://youtube.com> | awk '{ print $5 }' | grep . | grep -v '<<' > >>> yt.dig >>> >> >> You'd block google's DNS servers with that, which might not be a problem >> on the client, but may I suggest a "new and improved" method: >> >> host youtube.com | awk '/has address/ {print $NF}' >> 74.125.228.5 >> 74.125.228.3 >> 74.125.228.1 >> 74.125.228.14 >> 74.125.228.0 >> 74.125.228.8 >> 74.125.228.2 >> 74.125.228.6 >> 74.125.228.4 >> 74.125.228.9 >> 74.125.228.7 >> >> >> Remove the awk filter and you'll also see the IPv6: >> >> youtube.com has IPv6 address 2607:f8b0:400d:c00::5d >> > > > > -- > <http://stevenmiano.com/> Miano, Steven M. > http://stevenmiano.com > > -- <http://stevenmiano.com/> Miano, Steven M. http://stevenmiano.com
