SafeSearch is a feature offered by major search engines—such as YouTube, Google, Bing, and DuckDuckGo. It helps filter out inappropriate or explicit content from search results. By using the LAN DNS feature, network administrators can enforce SafeSearch for all LAN clients, ensuring that searches across these platforms automatically apply content filtering. Compared to DrayOS 4, where users had to manually map IP addresses or CNAMEs through the LAN DNS function, DrayOS 5 offers a dedicated SafeSearch option. Administrators can now apply SafeSearch to LAN clients with just a few simple selections and checkmarks.
1. Check the IP address SafeSearch in your area: For Windows users, run Command Prompt and enter command “nslookup forcesafesearch.google.com”, record the answer

2. On Vigor Router, set up LAN DNS for Google Search: Go to Applications >> LAN DNS/DNS Forwarding, and click on an index number to edit a profile.
3. With the LAN DNS configuration, when LAN client open Google Search, they will be redirected to Google SafeSearch, and will see a message says that SafeSearch has turned on.

If SafeSearch is not turned on as expected. please try the following
ipconfig/flushdns in command prompt.
dns.googlecloudflare-dns.comdoh.opendns.comdns.nextdns.iodns.quad9.netdoh.cleanbrowsing.org
With the LAN DNS SafeSearch configurations, when a LAN client opens Google Search, they will be redirected to Google SafeSearch. If a LAN user searches for improper content, the search results will be filtered and the page may display a warning message.
If SafeSearch is not turned on as expected, please try the following:
1. Enable DNS Redirection at LAN >> General Setup.
2. Create a LAN DNS profile, go to LAN >> LAN DNS, click Add to add a new profile, input profile name, and enable this profile.
3. There are two methods to set up the Domain Name, by IP and by CNAME, you may use either one of them.
By IP
By CNAME
4. Verifying the settings: Go to www.google.com, we should see the message “SafeSearch has turned on”. (If it's not, try clearing the browser's cookies first)

Published On:2025-12-16
ShareWas this helpful?