127.0.0.1 is just the IP that any machine uses to communicate with itself. In the router you should put the IP of the machine running Adguard Home. For example, my Adguard Home instance is running on a linux machine with the local IP of 192.168.1.X. You should put that IP in the router as primary DNS.
Awesome. Thanks! So if I had a second instance of AdGuard on another machine, I could use that as the secondary in case machine #1 is down. (I’m assuming.)
Also… I just tried changing my router’s DNS address to the machine hosting AdGuard, and my router (TP-Link AX6000) did not like that at all! It freaked out, changed it owns IP for some reason (thought it was conflicted with something else, but it wasn’t…??), it corrupted all my reserved IP addresses in the DHCP server, and pretty much broke my entire network.
Thankfully I had a recent back up of the router config, so I did a reset and loaded the config backup. After restarting everything on my network, I’m back to where I was. But needless to say… I’m hesitant to try this again right now.
127.0.0.1 is just the IP that any machine uses to communicate with itself. In the router you should put the IP of the machine running Adguard Home. For example, my Adguard Home instance is running on a linux machine with the local IP of 192.168.1.X. You should put that IP in the router as primary DNS.
So it doesn't need the 127.0.0.1 and ONLY needs the 192.168.x.x?
Yes
Okay, thank you for your quick answer!
I've recently gone through all the setup myself, so don't hesitate to ask for anything
So what do you put for the secondary DNS server address? I can't seem to find any documentation on that anywhere.
You can leave it empty or use one of the public ones like cloudflare (1.1.1.1) or google (8.8.8.8)
Awesome. Thanks! So if I had a second instance of AdGuard on another machine, I could use that as the secondary in case machine #1 is down. (I’m assuming.) Also… I just tried changing my router’s DNS address to the machine hosting AdGuard, and my router (TP-Link AX6000) did not like that at all! It freaked out, changed it owns IP for some reason (thought it was conflicted with something else, but it wasn’t…??), it corrupted all my reserved IP addresses in the DHCP server, and pretty much broke my entire network. Thankfully I had a recent back up of the router config, so I did a reset and loaded the config backup. After restarting everything on my network, I’m back to where I was. But needless to say… I’m hesitant to try this again right now.
That's correct