@“x”#1036128Is it possible via DHCP option 6? Otherwise I don’t have a better idea than what is described in part 2

Or hang the PiHole in the IB network (via VLAN internally in Proxmox if it also runs on it)

@“x”#1036128First change the IB subnet to that of Pfsense, enter the DNS IP, change the IP range back and hope that it doesn’t check the IB

Of course remove the static route as well as the Pfsense during the process

@Neliommiosch84

I have a bit of a problem understanding this.

If all your devices, including the Pi-hole, are in the pfSense network, then the DNS entries of the Internet box itself are not used at all, unless of course you would automatically transfer them to your pfSense network unnecessarily.

Why do you want to enter something different from the default on the Internet box?

Strange thing…

The router is simply not designed for this.

Do a NAT.

@“x”#1036128It’s normal, the box loops through DNS requests as if through itself for caching

If you set up DNS via DHCP option 6 then the IB gives the clients directly the IP from the DNS server

@“x”#1036128The suggestion I made in post 4 didn’t work

There will hardly be a better solution than what I have already suggested here

@“x”#1036128All right, what a shame

Then I would simply hang the PiHole in the IB network and it would be fine

---

@Neliommiosch84 wrote:

@NilsL Okay, I was able to solve this problem, thanks.

Anyone else have @Werner? any idea how I could solve the original problem?

Or why Swisscom even prohibits a DNS server in a different subnet?

---

This is not Swisscom banning something like this, but rather normal IP network technology with the associated routing tables and rules, which basically read:

- public IP addresses are routed to the Internet

- private IP addresses are only routed within the router’s own network

You’re currently trying to reinvent network technology without any apparent benefit to me.

If I understand it correctly, according to your wishes, your DNS server (presumably the Pi-hole appliance) should reside behind an additional firewall (the pfSense) in its own private IP range.

Aside from the fact that this doesn’t work, what’s the point of it anyway?

In principle, of course, the concept applies that you operate your Pi-hole within the same network in which it is to be used, and if not, it certainly belongs on the highest level of the router cascade, i.e. directly in the IP network of the Internet box.

Why are you even trying to deviate from that?