snagrat Posted July 11, 2017 Posted July 11, 2017 Have an issue where our uses can no longer get to YouTube and according to Lightspeed support is it because SWGfL are pushing users to a different URL. If I do a nslookup http://www.youtube.com it comes back as nossl.youtube.ifl.net. Anyone else having this issue?
mthomas08 Posted July 11, 2017 Posted July 11, 2017 We've got Lightspeed but no issues but ours is not provided by the SWGFL because we went else where to save costs. Our old setup was provided by the broadband providers. It was all housed by them. Although it was at times useful having them as middle men at times if they had problems it caused outages with us.
DJ-1701 Posted July 11, 2017 Posted July 11, 2017 Don't use Lightspeed, so not having an issue, but our nslookup result is the same for SWGfL... Non-authoritative answer: Name: nossl.youtube.ifl.net Addresses: 194.154.21.101 194.154.21.106 194.154.21.105 194.154.21.120 194.154.21.107 194.154.21.122 194.154.21.109 194.154.21.108 194.154.21.104 194.154.21.110 194.154.21.97 194.154.21.119 194.154.21.102 194.154.21.114 194.154.21.121 194.154.21.100 194.154.21.99 194.154.21.117 194.154.21.111 194.154.21.116 194.154.21.118 194.154.21.115 194.154.21.103 194.154.21.113 194.154.21.112 194.154.21.96 194.154.21.98 Aliases: www.youtube.com And different on the Exa network... Non-authoritative answer: Name: youtube-ui.l.google.com Addresses: 2a00:1450:4009:809::200e 216.58.198.174 Aliases: www.youtube.com
snagrat Posted July 11, 2017 Author Posted July 11, 2017 Yes Lightspeed are expecting the result you get on Exa. It is failing due to what SWGfL are doing.
DJ-1701 Posted July 11, 2017 Posted July 11, 2017 Yes Lightspeed are expecting the result you get on Exa. It is failing due to what SWGfL are doing. Which is odd that SWGfL are still doing it... because we still get redirected to the https site.
psydii Posted July 11, 2017 Posted July 11, 2017 Thats the RM IP space. Try pointing your DNS Servers/LightSpeed to use 8.8.8.8 for external lookups and try again. They are using a non encrypted version of youtube to do the content filtering. I thought Google had stopped that, but it is possible RM have persuaded them to re-implement it.
snagrat Posted July 11, 2017 Author Posted July 11, 2017 Thats the RM IP space. Try pointing your DNS Servers/LightSpeed to use 8.8.8.8 for external lookups and try again. They are using a non encrypted version of youtube to do the content filtering. I thought Google had stopped that, but it is possible RM have persuaded them to re-implement it. I'm pretty sure SWGfL block the use of using Googles 8.8.8.8 for DNS. Plus we need the DNS set correctly on the Lightspeed to resolve to our internal domain
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now