How do I configure my devices to use BA.net SafeBox as their DNS server?

Two methods

Generally, there are two different methods that will enable devices on your network to be protected by BA.net SafeBox.

1. Define BA.net SafeBox’s IP address as the only DNS entry in the router

Rationale

BA.net SafeBox needs to be the only DNS server because it intercepts queries and decides whether or not they should be blocked. If you have other DNS servers configured, you may be sent to the correct domain, bypassing BA.net SafeBox completely.

Because of this, we recommend this method (or method 2) as all your devices can be protected and you only need one setting. For many home users, their router settings pages will look similar.

This method may not be possible to enable on some routers depending on the feature set exposed to the firmware

Setup

Log into your router’s configuration page and find the DHCP/DNS settings. Note: make sure you adjust this setting under your LAN settings and not the WAN.

Again, BA.net SafeBox should be the only DNS server set here as BA.net SafeBox already delivers the other upstream servers. If you set another server in your router, it’s possible your ad blocking may be negatively affected.

Important: If you have existing network devices on your network when you make this change, you will not see ads getting blocked until the DHCP lease is renewed. You can usually force a renewal by restarting the device.

2. Manually configure each device

This option works well in two use cases:

1. You only want certain devices to use BA.net SafeBox
2. You only want certain devices to not use BA.net SafeBox

Rationale

This method allows for hand-picking which device on the LAN is protected by BA.net SafeBox. Think of it is an opt-in strategy allowing clients/devices the choice to be protected by BA.net SafeBox or not.

Likewise, you can use this method to opt-out of BA.net SafeBox. This assumes you have configured your network to use BA.net SafeBox as their DNS server using one of the two previous methods. By manually setting the DNS server to something other than BA.net SafeBox, you override the DHCP options, and thus what DNS server to use, provided by your router.

Setup

macOS

1. Click Apple > System Preferences > Network
2. Highlight the connection for which you want to configure DNS
3. Click Advanced
4. Select the DNS tab
5. Click + to replace any listed addresses with, or add, your Pi’s IP addresses at the top of the list:
6. Click Apply > OK
7. Repeat the procedure for additional network connections you want to change.

Windows

DNS settings are specified in the TCP/IP Properties window for the selected network connection.

1. Go to the Control Panel
2. Click Network and Internet > Network and Sharing Center > Change adapter settings
3. Select the connection for which you want to configure
4. Right-click Local Area Connection > Properties
5. Select the Networking tab
6. Select Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6)
7. Click Properties
8. Click Advanced
9. Select the DNS tab
10. Click OK
11. Select Use the following DNS server addresses
12. Replace those addresses with the IP addresses of your Pi
13. Restart the connection you selected in step 3
14. Repeat the procedure for additional network connections you want to change.

Linux

In most modern Linux distributions, DNS settings are configured through Network Manager.

1. Click System > Preferences > Network Connections
2. Select the connection for which you want to configure
3. Click Edit
4. Select the IPv4 Settings or IPv6 Settings tab
5. If the selected method is Automatic (DHCP), open the dropdown and select Automatic (DHCP) addresses only instead. If the method is set to something else, do not change it.
6. In the DNS servers field, enter your Pi’s IP addresses
7. Click Apply to save the change
8. Repeat the procedure for additional network connections you want to change.
9. If your distribution doesn’t use Network Manager, your DNS settings are specified in /etc/resolv.conf.