Entware Pi-hole directly on the router? Yes!

[junior120872]

I'm doing this as well.

Do you use keepalived between them, or do you just use them as DNS1 and DNS2?

 

[Untried3868]

Do you use keepalived between them, or do you just use them as DNS1 and DNS2?

I'm using them as DNS1 and DNS2, but they're configured identically. I was unable to indicate the actual Raspberry Pi devices in my signature due to the character limitation.

Edit: Signature updated.

 

[junior120872]

I'm using them as DNS1 and DNS2, but they're configured identically. I was unable to indicate the actual Raspberry Pi devices in my signature due to the character limitation.

Edit: Signature updated.

Do you see DNS resolution errors when one of them are down? I ended up having to use keepalived with a virtual ip address between the two, to prevent issues with resolution during maintenance of one of the machines (hardware, software).

 

[Untried3868]

Do you see DNS resolution errors when one of them are down? I ended up having to use keepalived with a virtual ip address between the two, to prevent issues with resolution during maintenance of one of the machines (hardware, software).

No, never experienced resolution issues...thankfully.

 

[heslo]

That's all that comes to my mind:

pihole debug
# upload when asked

netstat -tulnp | pihole tricorder

cat /etc/dnsmasq.conf | pihole tricorder

You could probably use wan-event script to just reload Pi-hole when reconnect happens if we can't get this fixed any other way

It went down momentarily this time but came back by itself no issue within a minute. Not sure if this was a related disconnect but thought I'd grab the logs anyway and upload them. You might be able to spot something

Sign in - Google Accounts

Sign in - Google Accounts

Sign in - Google Accounts

 

[jacklul]

Other than errors indicating that network is unreachable when trying to connect to upstream DNS (1.0.0.1) there is nothing useful there.
I assume you have listeningMode set to LOCAL, you might try setting it to ALL (and make sure you don't open port 53 in your router), maybe when the reconnect happens router changes something with the interfaces and Pi-hole uses old references or something, this is unlikely but maybe possible.
I see you have a tailscale, when this issue happens does the Pi-hole DNS still works when accessed through VPN?

 

[heslo]

Other than errors indicating that network is unreachable when trying to connect to upstream DNS (1.0.0.1) there is nothing useful there.
I assume you have listeningMode set to LOCAL, you might try setting it to ALL (and make sure you don't open port 53 in your router), maybe when the reconnect happens router changes something with the interfaces and Pi-hole uses old references or something, this is unlikely but maybe possible.
I see you have a tailscale, when this issue happens does the Pi-hole DNS still works when accessed through VPN?

Correct, listeningmode is set to LOCAL, I'll leave it as such until it properly goes down like last time (hopefully never again lol) and collect the logs again to see if anything does come up.

I have a tailscale yeah, this problem occurred without it as well so I'm sure it's not that. As for the pihole DNS using through it, I haven't set that up yet as I'm using it more to access a device and its files remotely, not using the pihole DNS (although that is on the list when I get some free time to set it up and test)

Thanks for looking at the logs! Only thing I've change since last time it went down is chuck a fan on my modem, I've noticed it getting quite hot especially with the increased temperatures where I live. It's 6 or 7 years old now, that may also be causing the issue and everything else is downstream from that but yeah, just trying to cover all bases currently