Would come from Pihole, but am unable to replicate its configuration in Technitium

[wouldntyouknow]

Hi!
I would like to know how I can mirror my current Pihole setup in Technitium.
Quick environment check:

• I own a domain, let's call it "terra.top"
• Pihole runs on Linux and serves two networks (on two interfaces), with all origins permitted:
  1. LAN: 192.168.0.0/24
  2. Tailscale: 100.64.0.0/10
• I have an nginx proxy manager, on IP: 192.168.0.8

The Pihole setup is pretty easy.
In "Local DNS records" I just added a record:
proxy.terra.top -> 192.168.0.8

Then, for each service to be accessed locally (as in on lan and tailscale), I just added CNAME records, like:
ittools.terra.top -> proxy.terra.top
trilium.terra.top -> proxy.terra.top
chat.terra.top -> proxy.terra.top

Of course each entry has its own "proxy host" in nginx, with the target IP:PORT and my wildcard cert for "terra.top" for HTTPS.
Anyting with "*.terra.top" that doesn't match a defined CNAME is forwarded for upstream DNS resolution, which makes it possible to connect to certain services from outside via Cloudflare Tunnels or Pangolin (but I didn't use the same subdomains for outside access, used different ones that do not resolve internally).

I would very much like to replicate this setup in Technitium so I can switch to it.
I tried to look this up, but from what I gathered it's not an easy setup and nothing quite matched my scenario so I was unable to apply to my case, as my understanding in this topic is severely limited.
Thanks for the help!

[ShreyasZare]

Thanks for asking. You can achieve the same by creating a Conditional Forwarder zone for terra.top with forwarder set to "This Server" and adding the required A or CNAME records in that zone. Any record that does not exists in the zone gets automatically resolved normally as defined in the FWD record in that zone which should be set to "This Server" so that resolution is done internally by the DNS server.

Let me know if you have any more queries.

[wouldntyouknow]

Thanks for asking. You can achieve the same by creating a Conditional Forwarder zone for terra.top with forwarder set to "This Server" and adding the required A or CNAME records in that zone. Any record that does not exists in the zone gets automatically resolved normally as defined in the FWD record in that zone which should be set to "This Server" so that resolution is done internally by the DNS server.

Let me know if you have any more queries.

Thank you very much! I thought I need split horizon app or something, this is much more straightforward and understandable!
I don't want to take much of your time, but may I ask for a quick verification?
Are these settings fine? These are for serving LAN and Tailscale clients. I would define 100.35.111.3 as DNS server in Tailscale's DNS settings.

DNS Server Domain: 					technitium.terra.top

DNS Server Local End Points:		192.168.0.3:53
									100.35.111.3:53

DNS Server IPv4 Source Addresses:	192.168.0.3

Recursion: Use Specified Network Access Control List (ACL)
									192.168.0.0/24
									100.64.0.0/10

Just a yes/no will suffice :)

[ShreyasZare]

You're welcome! This forwarder zone config you did is really a type of split horizon setup. The forwarder zone is quite powerful actually and can be used for many type of scenarios.

The "DNS Server Domain" can be anything and it does not affect resolution as its just used when creating zones.

The "DNS Server Local End Points" default values work well and you only need to explicitly set IP addresses here if your server has multiple network adapters. So that looks good here.

The "DNS Server IPv4 Source Addresses" should only be configured if you want the DNS server to send all outbound requests using that interface when you have multiple network interfaces. This should only and only be configured if you know that you want to send all requests out of one or more specific network adapters. The default option should work for most cases. Note that wrong config here will cause all resolution to fail.

The Recursion setting looks fine.