Am I the only one failing with Youtube this morning?

[robjduk]

Hello,

First off, I have never really had to play with forward lookup zones before so today is ruining me. Youtube education has died and replaced with the following simple steps...

 

YOUTUBE CONTENT LINK

 

Every time I create forward lookup zones like I think it should be done, youtube stops working around the site with DNS reasons given. When I remove what I do it works again (although with full access). Really need/want to get this sorted asap and could use some EASY, STEP BY STEP, ULTIMATE HAND HOLDING guide.

 

Long story short, what I am doing at the moment is this...

creating a forward lookup zone for the following with CNAMES restrictmoderate.youtube.com

 

Forward lookup zone 1:

youtube.com

m.youtube.com CNAME forwarding to restrictmoderate.youtube.com

http://www.youtube.com CNAME forwarding to restrictmoderate.youtube.com

 

Forward lookup zone 2:

googleapis.com

youtube.googleapis.com CNAME forwarding to restrictmoderate.youtube.com

youtubei.googleapis.com CNAME forwarding to restrictmoderate.youtube.com

 

Forward lookup zone 3:

youtube-nocookie.com

http://www.youtube-nocookie.com CNAME forward to restrictmoderate.youtube.com

 

oh and when I do this, Chromebooks all stop logging in too.

 

Life has not been kind to me so far this year and this is really getting to me. Can anyone just make this go away? I did see a post about this on EDG however it was on the Smoothwall page and I am lightspeed.

 

Thanks all

Edited July 7, 2016 by robjduk

[localzuk]

Question - is your filtering device using your internal DNS servers? If not, you could potentially be having issues as the filtering device may be doing the DNS resolution rather than the client.

[robjduk]

Filtering is controlled by our local authority however I use their DNS for the domain.

[localzuk]

Filtering is controlled by our local authority however I use their DNS for the domain.

 

The issue is, if your clients aren't doing the name resolution for the requests (as they're going via that filtering device that is doing them instead), your internal DNS settings would be ignored.

 

You may need to speak to your LA IT people about it.

[IrritableTech]

Question - is your filtering device using your internal DNS servers? If not, you could potentially be having issues as the filtering device may be doing the DNS resolution rather than the client.

 

Yup this was a problem for us which we've had to work around.

 

I created the DNS entries a bit differently from you however...

 

I created a new zone for each of the five URLs and created a DNAME for restrictmoderate.youtube.com

 

If your servers are acting as the SOA for the parent domain youtube.com for example, they may not be returning all the other required subdomains - a.youtube.com, accounts.youtube.com etc. etc.

[robjduk]

That worked thank you.