[SOLUTION]
Just gonna save anyone who gets here some time.
In this particular case, and for whatever reason (unknown), changing settings in the gui/via SSH and then soft and even hard rebooting had no effect. The solution was a full power cycle for changed settings were applied.
---------------------------------------------------------------------------------------------------------------------------
Relevant info - due to the nature of the layout and pre-existing networking in my rented apartment, I have two routers, both flashed with Merlin and up to date:
Router 1: AX56U, Wireless router mode
Router 2: AC68U, AP mode
I've had R2 for a while, it is what all my wireless devices connected to (and still connect to). R1 was purchased due to where the modem for the apartment is located and the remaining space in the cabinet - my AC68U just couldn't fit.
Config is R1 `192.168.1.1` -> switch -> all main rooms. R2 `192.168.1.3` with R1 as the gateway. Almost all wireless devices connect to R2.
A few years ago I configured piHole `192.168.1.101` on a raspberry pi zero w, and adguard `192.168.1.200` on a Synology NAS to be DNS servers for R1. These were set as DNS 1 and 2 respectively in LAN -> DHCP Servers. Both devices and R2 are set to 'No Redirection' in the DNS Director. Mostly pihole would respond quickest, but ~20% would be served by adguard. WAN DNS was set to auto from the ISP.
Recently I've added more demanding services to the NAS, so to lighten the load a little I set up adguard on my Home Assistant Odroid N2+ `192.168.1.105` and updated Lan -> DHCP Server -> DNS Server 1 on R1 accordingly, with nothing in DNS Server 2. When after a while I saw it wasn't responding to any queries or seeing any clients, I set it as the DNS server for my PC, and it was pinged. I set the PC back to auto DNS from the router, I turned off the rPi with pihole on it, and DNS started to get routed back to my NAS adguard instance (1.200). Stopping adguard on the NAS then stopped all DNS from working.
Currently the raspberry pi is back on, however `192.168.1.101` isn't anywhere in an R1 field except where I've assigned it that IP in DHCP. DNS is only set to `192.168.1.105`. However `nslookup` of a site always returns pihole as the server:
Thinking it might be stuck in nvram, I ran
which returns
unless I specify nslookup google.com 192.168.1.105 in which case it returns
If I do
to see all DNS settings, the other relevant parts are
I had played around with Dual Wan a while back but had disabled it again pretty much immediately, so I'm surprised to see that a) there's WAN, WAN0 and WAN1 and b) although the WAN DNS is set in the GUI to auto from the IP, it's displaying the built-in adguard option which as far as I remember I've never selected.
I wonder what resolv is showing, so # cat /etc/resolv.conf:
which are my ISP's DNS servers.
From there I wonder if it's a DHCP issue where the client lease needs to be renewed. Using my Android phone, I 'forgot' the network, removed the DHCP allocation in the router, restarted the router, restarted my phone, and it was given exactly the same IP it was previously assigned, even though there's nothing on the phone or router tying it to that. Did the same with my laptop, and got the same result, and nslookup still shows pihole (1.101) as the server.
Remember how I'm connecting to R2 via wifi? Well I connect to R1 via wifi thinking maybe something's somehow gotten cached and / or stuck in R2. Nope, nslookup still shows the DNS server as pihole.
At this point I have no idea where I'm going wrong, nor can I remember what else I did to set pihole and the NAS adguard instance as my DNS servers and have since forgotten. Any help would be greatly appreciated.
Just gonna save anyone who gets here some time.
In this particular case, and for whatever reason (unknown), changing settings in the gui/via SSH and then soft and even hard rebooting had no effect. The solution was a full power cycle for changed settings were applied.
---------------------------------------------------------------------------------------------------------------------------
Relevant info - due to the nature of the layout and pre-existing networking in my rented apartment, I have two routers, both flashed with Merlin and up to date:
Router 1: AX56U, Wireless router mode
Router 2: AC68U, AP mode
I've had R2 for a while, it is what all my wireless devices connected to (and still connect to). R1 was purchased due to where the modem for the apartment is located and the remaining space in the cabinet - my AC68U just couldn't fit.
Config is R1 `192.168.1.1` -> switch -> all main rooms. R2 `192.168.1.3` with R1 as the gateway. Almost all wireless devices connect to R2.
A few years ago I configured piHole `192.168.1.101` on a raspberry pi zero w, and adguard `192.168.1.200` on a Synology NAS to be DNS servers for R1. These were set as DNS 1 and 2 respectively in LAN -> DHCP Servers. Both devices and R2 are set to 'No Redirection' in the DNS Director. Mostly pihole would respond quickest, but ~20% would be served by adguard. WAN DNS was set to auto from the ISP.
Recently I've added more demanding services to the NAS, so to lighten the load a little I set up adguard on my Home Assistant Odroid N2+ `192.168.1.105` and updated Lan -> DHCP Server -> DNS Server 1 on R1 accordingly, with nothing in DNS Server 2. When after a while I saw it wasn't responding to any queries or seeing any clients, I set it as the DNS server for my PC, and it was pinged. I set the PC back to auto DNS from the router, I turned off the rPi with pihole on it, and DNS started to get routed back to my NAS adguard instance (1.200). Stopping adguard on the NAS then stopped all DNS from working.
Currently the raspberry pi is back on, however `192.168.1.101` isn't anywhere in an R1 field except where I've assigned it that IP in DHCP. DNS is only set to `192.168.1.105`. However `nslookup` of a site always returns pihole as the server:
Code:
Server: pi.hole
Address: 192.168.1.101
Non-authoritative answer:
Name: google.com
Addresses: 2404:6800:400a:80a::200e
172.217.25.174Thinking it might be stuck in nvram, I ran
Code:
nvram show | grep dhcp_dns
Code:
dhcp_dns1_x=192.168.1.105
dhcp_dns2_x=unless I specify nslookup google.com 192.168.1.105 in which case it returns
Code:
Server: HomeAssistant
Address: 192.168.1.105
Non-authoritative answer:
Name: google.com
Addresses: 2404:6800:4004:801::200e
172.217.26.238If I do
Code:
nvram show | grep dns
Code:
lan_dns=
lan_dns1_x=
lan_dns2_x=
wan0_dns=202.224.32.1 202.224.32.2
wan0_dns1_x=94.140.14.14
wan0_dns2_x=94.140.15.15
wan0_dns_r=202.224.32.1 202.224.32.2
wan0_dnsenable_x=1
wan0_xdns=
wan1_dns=
wan1_dns1_x=
wan1_dns2_x=
wan1_dnsenable_x=1
wan_dns=202.224.32.1 202.224.32.2
wan_dns1_x=94.140.14.14
wan_dns2_x=94.140.15.15
wan_dnsenable_x=1I had played around with Dual Wan a while back but had disabled it again pretty much immediately, so I'm surprised to see that a) there's WAN, WAN0 and WAN1 and b) although the WAN DNS is set in the GUI to auto from the IP, it's displaying the built-in adguard option which as far as I remember I've never selected.
I wonder what resolv is showing, so # cat /etc/resolv.conf:
Code:
nameserver 202.224.32.1
nameserver 202.224.32.2which are my ISP's DNS servers.
From there I wonder if it's a DHCP issue where the client lease needs to be renewed. Using my Android phone, I 'forgot' the network, removed the DHCP allocation in the router, restarted the router, restarted my phone, and it was given exactly the same IP it was previously assigned, even though there's nothing on the phone or router tying it to that. Did the same with my laptop, and got the same result, and nslookup still shows pihole (1.101) as the server.
Remember how I'm connecting to R2 via wifi? Well I connect to R1 via wifi thinking maybe something's somehow gotten cached and / or stuck in R2. Nope, nslookup still shows the DNS server as pihole.
At this point I have no idea where I'm going wrong, nor can I remember what else I did to set pihole and the NAS adguard instance as my DNS servers and have since forgotten. Any help would be greatly appreciated.
Last edited:
