DNS is how computers turn a name, such as defend-o-tron.protected.lan, into an address. The Defend-O-Tron answers for its own names under protected.lan:
defend-o-tron.protected.lan: the web interface.adguard.protected.lan: the DNS filter’s own settings.crowdsec.protected.lan: where connected systems read the block list.Your computers can only use these names if their lookups for protected.lan reach the Defend-O-Tron.
Without A or B below, none of the
*.protected.lannames work. Your computers cannot finddefend-o-tron.protected.lan,adguard.protected.lanorcrowdsec.protected.lan. You can still reach the web interface athttps://<management ip>/.
| A. Send only protected.lan to the Defend-O-Tron | B. Use the Defend-O-Tron for all DNS | |
|---|---|---|
| What it does | Your router or DNS server asks the Defend-O-Tron about protected.lan names, and everything else as before | Every lookup on your network goes through the Defend-O-Tron |
| Ad, tracker, and malware filtering | No | Yes, with the built-in DNS filter |
| If the Defend-O-Tron is switched off | Only protected.lan names stop working | All name lookups stop, so web browsing stops too |
| Best for | Offices with their own DNS server, or a router that can forward one domain | Small networks that want filtering |
If you are not sure, choose A. It changes the least, and the rest of the Defend-O-Tron’s protection works the same either way.
Find the Defend-O-Tron’s management address. In the web interface, under Device, click Management port. The Address box shows it (in the example, 192.168.1.20). The steps below call it <management ip>.

Make sure that address never changes. Every step below points your network at this address. If the Defend-O-Tron gets a different one, DNS stops working for everything set up here. Do one of these:
Do this before you change any DNS settings. An address that changes later breaks name lookups for every device that uses the Defend-O-Tron for DNS.
Allow your DNS server or router through the Defend-O-Tron’s firewall. Under Detection, click Firewall. On the Management access card, check that the address of the system that will ask the Defend-O-Tron (your router or DNS server for A, your computers for B) is covered by Management allowed addresses and Management networks. Add it if it isn’t, then click Save and apply.

This is called conditional forwarding: “for names ending in protected.lan, ask this server”. Pick the system that answers DNS on your network.
For networks with a Windows domain controller or Windows DNS server.
Open DNS Manager and expand your server.
Right-click Conditional Forwarders and choose New Conditional Forwarder…

In DNS Domain, type protected.lan.
In the list of server IP addresses below it, click and type the Defend-O-Tron’s management address, then press Enter. A red mark saying the server is not authoritative is normal here and can be ignored.
To share the setting with your other domain controllers, tick Store this conditional forwarder in Active Directory and choose who to share it with.
Click OK.

The same in PowerShell, run as Administrator:
Add-DnsServerConditionalForwarderZone -Name "protected.lan" -MasterServers <management ip> -ReplicationScope "Domain"
Leave out -ReplicationScope "Domain" to keep it on this server only. See Microsoft’s DNS forwarding page for more.
Needs RouterOS 7.5 or later. Your router must already be the DNS server for your network, which is how MikroTik routers come set up. If you use DNS over HTTPS on the router, you need 7.16 or later.
protected.lan, and Forward To to the Defend-O-Tron’s management address.protected.lan is forwarded, and none of the names under it.The same from the RouterOS terminal:
/ip/dns/static/add name=protected.lan type=FWD forward-to=<management ip> match-subdomain=yes
/ip/dns/cache/flush
If Match Subdomain isn’t shown on your screen, use the terminal command. See MikroTik’s DNS guide for more.
pfSense uses the DNS Resolver unless you have switched to the DNS Forwarder.
protected.lan and IP Address to the Defend-O-Tron’s management address. Leave TLS Queries off.Defend-O-Tron.On the DNS Forwarder instead, use Services → DNS Forwarder → Domain Overrides → Add, with the same domain and address.
pfSense handles the rest by itself. See Netgate’s Domain Overrides page for more.
protected.lan and Server IP to the Defend-O-Tron’s management address. Leave Port empty (port 53).Fill in Domain. If it is left empty, OPNsense sends every lookup to the Defend-O-Tron.
See the OPNsense Unbound guide for more.
Needs UniFi Network 9.3 or later, on a UniFi gateway (Dream Machine, Cloud Gateway, and others).
protected.lan and IP Address to the Defend-O-Tron’s management address.This works for computers that use the UniFi gateway as their DNS server. Leave the network’s DHCP DNS Server setting on Auto. See Ubiquiti’s DNS records article for the current steps.
For FortiOS 7.x. Your computers must use the FortiGate as their DNS server.
protected-lan.protected.lan.The same from the FortiGate CLI (replace internal with your interface name):
config system dns-server
edit "internal"
set mode recursive
next
end
config system dns-database
edit "protected-lan"
set domain "protected.lan"
set type primary
set view shadow
set authoritative disable
set forwarder "<management ip>"
next
end
See Fortinet’s FortiGate DNS server guide for more.
Meraki MX appliances can’t forward one domain to another DNS server. Use one of these instead:
For a Linux server running dnsmasq or Unbound.
dnsmasq: add these lines to a file in /etc/dnsmasq.d/, for example /etc/dnsmasq.d/defend-o-tron.conf, then restart dnsmasq:
server=/protected.lan/<management ip>
rebind-domain-ok=/protected.lan/
Unbound: add these lines to your Unbound configuration, for example /etc/unbound/unbound.conf.d/defend-o-tron.conf, then restart Unbound:
server:
domain-insecure: "protected.lan"
private-domain: "protected.lan"
forward-zone:
name: "protected.lan"
forward-addr: <management ip>
The extra lines let the private address in the Defend-O-Tron’s answers through. Without them, many DNS servers throw those answers away as a safety measure.
For DNS filtering, your network’s lookups must reach the Defend-O-Tron. There are three ways. Use the first one if you can:
| Way | What you change | Filtering | AdGuard sees each device |
|---|---|---|---|
| B1. Your router hands it out | The DNS server your router gives every device (DHCP) | Every device | Yes |
| B2. Your DNS server forwards everything | Your own DNS server sends every lookup to the Defend-O-Tron | Every device that uses your DNS server | No: AdGuard sees only your DNS server, so per-device rules and the Top devices list do not work |
| B3. One device only | That device’s own network settings | That device only | Yes |
For B1 and B3, each device asks the Defend-O-Tron itself, so the devices’ addresses must be allowed on the Firewall page (see Before you start). For B2, only your DNS server needs to be allowed.
Set the Defend-O-Tron’s management address as the only DNS server your router’s DHCP server hands out. Computers pick up the change when they renew their address, or straight away after a restart.
Don’t add a second, public DNS server (such as your internet provider’s,
8.8.8.8, or1.1.1.1) “as a backup”. Computers don’t always ask the first server first. When they ask the public one, it skips the filtering, and it replies that protected.lan names don’t exist. The result is names that work one minute and fail the next.
Check IPv6 too. If your network uses IPv6, your router may also hand out your internet provider’s DNS server over IPv6, which causes the same problem. Turn that off, or point it at the Defend-O-Tron.
Some routers block DNS answers that contain a private address (often called DNS rebind protection). If protected.lan names don’t work after this change, add protected.lan to the router’s rebind-protection exceptions.
<management ip>, and leave the others empty.OPNsense offers several DHCP services. Use the one your LAN runs:
dns-server for your LAN with the value <management ip>.<management ip>.<management ip>.Then click Save and Apply.
In a terminal (or IP → DHCP Server → Networks in WinBox), set the DNS server for each DHCP network:
/ip dhcp-server network set [find] dns-server=<management ip>
<management ip> as the only server.<management ip> as the only server.<management ip>.<management ip>.If your network already has its own DNS server, keep it, and make it send every lookup it cannot answer itself to the Defend-O-Tron. Your devices keep using your DNS server, and the lookups are filtered on the way.
<management ip>, and click OK. Remove any other forwarders.<management ip> as the only server, and clear Allow DNS servers to be overridden by DHCP/PPP on WAN. Click Save.If names stop working, clear Enable DNSSEC Support on the same page: the Defend-O-Tron does not check DNSSEC by default.
<management ip>, and leave Domain empty so it applies to every name.If your MikroTik answers DNS for your network, point it at the Defend-O-Tron:
/ip dns set servers=<management ip>
Check that IP → DHCP Client does not add your provider’s DNS servers (use-peer-dns=no).
For dnsmasq, in /etc/dnsmasq.conf (or a file in /etc/dnsmasq.d/):
no-resolv
server=<management ip>
For Unbound, in unbound.conf:
forward-zone:
name: "."
forward-addr: <management ip>
Restart the service after the change.
Use this to try the filter on one device, or for a device that should always be filtered. It changes only that device, and only on the network you set it on.
Browsers can skip the filter. Chrome, Edge and Firefox can send lookups straight to a public resolver over encrypted DNS (“secure DNS” or “DNS over HTTPS”). Lookups sent that way never reach the Defend-O-Tron. In Chrome and Edge, look under Settings → Privacy and security → Security → Use secure DNS and choose your current service provider, or turn it off. In Firefox, look under Settings → Privacy & Security → DNS over HTTPS and choose Off.
Windows 11:
<management ip>, leave Alternate DNS empty, and set DNS over HTTPS to Off.Windows 10: open Control Panel → Network and Sharing Center → Change adapter settings, right-click your connection, choose Properties, then Internet Protocol Version 4 (TCP/IPv4) → Properties. Choose Use the following DNS server addresses, enter <management ip> as the preferred server, and click OK.
<management ip>.With NetworkManager (most desktop distributions):
nmcli connection show # find your connection's name
sudo nmcli connection modify "<name>" ipv4.dns <management ip> ipv4.ignore-auto-dns yes
sudo nmcli connection up "<name>"
<management ip>, and tap Save.This applies to that Wi-Fi network only.
<management ip>. Leave DNS 2 empty.The menu names differ between phone makers. On most networks, B1 is the easier way for Android phones.
On a computer on your network, open a Command Prompt (Windows) or Terminal (Mac, Linux) and type:
nslookup defend-o-tron.protected.lan
The answer should show the Defend-O-Tron’s management address:
Name: defend-o-tron.protected.lan
Address: 192.168.1.20
Then open https://defend-o-tron.protected.lan in your browser.
Test with a full name such as
defend-o-tron.protected.lan. The plain nameprotected.lanon its own has no address, so it never answers.
If the answer is wrong or says the name can’t be found:
ipconfig /flushdns, or restart the computer, then try again.ipconfig /all (Windows) and look at DNS Servers.If you chose B, also check that the filtering works. In the web interface, open Detection → DNS filtering, then the Query log tab. Browse a few sites on the computer, and its lookups appear in the list within a few seconds. With B2, they show your DNS server as the device that asked.
crowdsec.protected.lan.https://…protected.lan pages open without a warning.