CNAME and Enforcing Google Safe Search

[fellipec]

Expected Behaviour:

Following this guide to enforce safe search on network

Expect the CNAME resolve to forcesafesearch.google.com sucessfully

Actual Behaviour:

As discussed on this post, CNAMEs are not fowarded by design.

So how to use this feature effectively?

[Bucking_Horn]

I've explained that already in my reply to Force safe search using Pi-hole - #2 by Bucking_Horn (your above first link):

@Bucking_Horn

To make CNAMEs work, you'd have to define the respective local DNS records (A and AAAA) for resolution targets as well.
If you consider this, you should be aware that when acquiring the IP addresses to add, the IPs you would receive for resolving a given domain may differ from those that someone requesting it from another geographical location may see.
Also, this approach may break as soon as public DNS resolution of such a target domain would change to a different IP.

[DanSchaper]

You need to add both CNAME and host values.

Something along the lines of raw.githubusercontent.com/jaykepeters/PSS/master/Pi-hole_SafeSearch.sh

# Host Records!!!
hostRecords=(
    "host-record=forcesafesearch.google.com,216.239.38.120"
    "host-record=safe.duckduckgo.com,54.241.17.246"
    "host-record=restrict.youtube.com,216.239.38.120"
    "host-record=strict.bing.com,204.79.197.220"
    "host-record=safesearch.pixabay.com,176.9.158.70"
)
ytSS=(
   "cname=www.youtube.com,restrict.youtube.com"
   "cname=m.youtube.com,restrict.youtube.com"
   "cname=youtubei.googleapis.com,restrict.youtube.com"
   "cname=youtube.googleapis.com,restrict.youtube.com"
   "cname=www.youtube-nocookie.com,restrict.youtube.com"

Edit: The guide seems correct, what is the problem you are seeing?

[fellipec]

Thank you. This solved the problem.

[fellipec]

Thanks, after I tried to troubleshoot this for some hours I had a coffee and read again and noticed this. It's working now.