Hi there, On my router/modem I cannot change the DNS entries, thus just using Adguard/PiHole for DNS blocking ads doesn’t work. Would a seperate Router circumvent this problem? Could I set up Adguard (or PiHole) on a Raspberry and use it as a DNS server for my home network?

The plan would be to use my ISP-provided router just as a modem to connect to the internet. Then us a second router to provide my home network, where also Adguard/PiHole can do their thing.

Would this setup work and how would I need to configure it?

7 points

I’ve done something similar in Ireland, where ISP router was the only way to connect. Managed to setup everything on OpenWRT router, but it kept disconnecting, so I put openwrt router behind ISP router.

Interesting thing I found in ISP router is DMZ host - just point it to your own router and that’s it. Basically ISP router doesn’t exist lol.

Then you have absolute freedom with your router.

permalink
report
reply
2 points

I ran like this for years. As long as you have DMZ/exposed host functionality everything works great. The only thing that needed some massaging was IPv6, but if you want/need that, you probably know enough about it to get it working.

“Double NAT” is a bit of a bugbear in the home lab community, but as long as you can port forward in bulk you should not even notice it, aside from a tiny bit of additional latency.

permalink
report
parent
reply
6 points

Cant you just set PiHole’s IP as DNS on your clients?

permalink
report
reply
1 point

Yes, especially if you use it as your dhcp server.

permalink
report
parent
reply
4 points

Bridge mode on the ISP router is what you want. Then it just passes through the internet connection to the internal router on the edge of your network. It’s what I do with Comcast.

permalink
report
reply
3 points

Connect the router’s WAN port into the cable modem. Plug your stuff into the router LAN ports or connect to the new router wifi. Set pi hole to a static address and then set the router’s DNS to point to that. Remove any secondary DNS in the router settings. Reboot everything and make sure it all works. That should be about it.

permalink
report
reply
2 points
*

I had this same problem but Pihole can act as your DHCP server too. I turned off DHCP on my ISP router, turned it on in Pihole and configured my range (with some buffer for static IPs for servers and others) and off it went. When all my clients (laptops, workstations, phones, etc.) requested an IP (which I saw them trickle in almost immediately), they got their IP from Pihole and also automatically directed all DNS queries to Pihole. No need for complicated setups.

Edit: fix typos.

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.7K

    Monthly active users

  • 3.5K

    Posts

  • 78K

    Comments