Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CNAME to safe.duckduckgo.com is unresolved #451

Open
charlesmulder opened this issue Aug 26, 2024 · 1 comment
Open

CNAME to safe.duckduckgo.com is unresolved #451

charlesmulder opened this issue Aug 26, 2024 · 1 comment

Comments

@charlesmulder
Copy link

charlesmulder commented Aug 26, 2024

Hi.

I hope you can help me to enforce safe searching on my home network.

I have followed the documentation to Force Safe Search at a Network Level, but once I add the CNAME the duckduckgo.com domain doesn't resolve.

$ curl https://duckduckgo.com
curl: (6) Could not resolve host: duckduckgo.com
$ dig 192.168.1.208 duckduckgo.com
duckduckgo.com.         0       IN      CNAME   safe.duckduckgo.com.
$ dig 192.168.1.208 safe.duckduckgo.com
safe.duckduckgo.com.    202     IN      A       52.142.126.100

I followed Google's documentation Lock SafeSearch for accounts, devices & networks you manage, which is working as expected.

$ dig 192.168.1.208 www.google.com
www.google.com.         0       IN      CNAME   forcesafesearch.google.com.
forcesafesearch.google.com. 6654 IN     A       216.239.38.120
$ dig 192.168.1.208 forcesafesearch.google.com
forcesafesearch.google.com. 6205 IN     A       216.239.38.120

Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@charlesmulder and others