I have activated AdGuard Home on my Beryl, it has some upstream rules for *.my.custom domains that request it from 192.168.8.1 (Beryl AX) configured static hostnames. I do this so I can move some devices between networks I control and the Beryl.
I changed the mode to Extender while I am on my in-laws, where the main router already resolves *.my.custom domains and I noticed a problem: I could access some-device.my.custom while connected to the main router WiFi, but not when connected to the Beryl AX.
After some debugging I found the problem, even when AdGuard Home Seems to be disabled and not accessible while con Extender mode:
It was actively trying to route *.my.custom and failing because requests to 192.168.8.1:53 were timing out. I saw it on the System Logs.
I had to go back to router mode, disable AdGuard manually and going back into Extender Mode and then I was able to access some-device.my.custom from both the main router WiFi and my Beryl's WiFi.
I searched the board but I was not able to find any similar problem. Is this an unknown bug?
alzhao
2
Will do a test and check if this is a bug.
alzhao
4
From my test, if you tick this option, Adguard Home will still be used to resolve dns.
Can you confirm?
1 Like
Hi, I am not on the other place right now. But I do have that option enabled when working on router mode.
The problem is fixed in firmware v4.8.
