AC1350 ignoring local DNS settings (pi-hole)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I'm having the exact problem described here. I restarted the router and my local DNS server is still being ignored. I don't remember changing any router settings and I've been using this set up for a few years now.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Yep, set both DNS servers to 192.168.0.100 and test.
Is your device Archer C60 ?
Your DHCP server pool looks unrealisticly large.
You LAN settings should be like:
IP address 192.168.0.1/255.255.255.0
And the DHCP pool more like:
192.168.0.2 - 192.168.0.99
- Copy Link
- Report Inappropriate Content
Keep the router's IP address and its DHCP server pool settings as I posted and everything would be fine.
This router can serve normally 25-30 devices so your previous DHCP pool was unnecessarily large.
As for the DNS settings keep both primary and secondary DNSs set to your pi-hole - I believe this was the issue, cause I doubt that you have any devices in other than 192.168.0.0/24 network.
- Copy Link
- Report Inappropriate Content
There should be a reason for that for sure. Any FW updates on the router recently ?
Do the problematic devices get their IP addresses by router's DHCP server or they are statically assigned ?
Have you checked the network properties of these devices to see what's their DNS servers assigned ?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
If you have in your router DHCP server settings:
Primary DNS:192.168.0.100 (pi-hole)
Secondary DNS:192.168.0.1 (router)
and for some reason a DNS request can't be resolved by the Primary DNS server then the DNS query will be resolved by the Secondary DNS server.
To test if that's the case I would suggest to remove the Secondary DNS server (192.168.0.1) from your router's DHCP server DNS entries and test again.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Yep, set both DNS servers to 192.168.0.100 and test.
Is your device Archer C60 ?
Your DHCP server pool looks unrealisticly large.
You LAN settings should be like:
IP address 192.168.0.1/255.255.255.0
And the DHCP pool more like:
192.168.0.2 - 192.168.0.99
- Copy Link
- Report Inappropriate Content
@terziyski I think when I set up the router I wanted to have 192.0.x.x and 192.1.x.x have meanings. That's why my pihole's at 192.168.1.100 instead of 192.168.0.100. My LAN settings are IP address 192.168.0.1/255.255.0.0
If there's harm in that, I can scale back to only 100 addresses like you suggest. I don't know what's normal :)
EDIT: Oh, and the model title of the page I visit is "Archer C59".
- Copy Link
- Report Inappropriate Content
Thanks! It's working now. (Or at least I'm at the pihole problem level, no longer router) I think I was causing multiple problems. My 192.168.x.x dhcp space meant that I was handing out addresses that the pihole considered "outside the local network". I need to either tell the pihole to accept DNS requests more than one hop away (scary, though my pihole's behind the router without a port forwarded to it or anything) or tell the pihole what's inside my network. This may have combined with not having the pihole listed as the secondary DNS server.
Thanks again!
- Copy Link
- Report Inappropriate Content
Keep the router's IP address and its DHCP server pool settings as I posted and everything would be fine.
This router can serve normally 25-30 devices so your previous DHCP pool was unnecessarily large.
As for the DNS settings keep both primary and secondary DNSs set to your pi-hole - I believe this was the issue, cause I doubt that you have any devices in other than 192.168.0.0/24 network.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1060
Replies: 8
Voters 0
No one has voted for it yet.