Setting googles nosslsearch.. doesnt work
I have looked into googles nosslsearch and is this going to work for BYOD devices too? If I have my DHCP server as the smoothie and its giving out DNS addresses of 188.8.131.52 and 184.108.40.206, are users still able to get round the nosslsearch as the DNS edit is on the internal network which the BYOD devices dont see.
Is there a way in smoothwall, maybe a header override that can be used, a bit like the youtube one to block or redirect users to the normal Google instead of https://..
@AMLightfoot, i have tried the google suggestion and it doesnt work - Creating a new forward lookup zone: google.com, create a CNAME www and point it to nosslsearch.google.com messes up our website internally and also breaks google, thats if im setting it up right?
There are a lot of threads on the net about how its not worknig for others too. Plus if i go to https://nosslsearch.google.com or Google the pages arent available.
Has anyone on here got this to work?