DNS Forwarder: forward not working for dns request

chris1284

Hi,
i have technitium cluster with 2 dns + dhcp servers. the dns resolver at pfsense is disbaled, the dhcp service is disabled. in

SystemGeneral Setup -> System: domain is set to home.arpa
SystemGeneral Setup -> DNS Server: 192.168.2.3 & 192.168.2.7 is set

the dns forwarder is enabled, service started.

WG0 is my wireguard interface with 10.0.9.1/24

domain overrides is set:

my problem is on my wireguard tunnels, that nslookuphostname or hostname.home.arpa is not forwarded. internal everything is working, because idhcp sets the dns server and the search suffic to home.apra. in wireguard clients i have fix ips and set the DNS like this:

[Interface]
PrivateKey =blablub=
Address = 10.0.9.5/32
DNS = 10.0.9.1, home.arpa

nslookup on a wireguard client with hostname only:

nslookup nas00
Server:  UnKnown
Address:  10.0.9.1

*** nas00 wurde von UnKnown nicht gefunden: Server failed.

with hostname + domain

nslookup nas00.home.arpa
Server:  UnKnown
Address:  10.0.9.1

*** nas00.home.arpa wurde von UnKnown nicht gefunden: Server failed.

what can i do, to configure the forwarder to forward every dns reqeust at 10.0.9.1 to 192.168.2.3?
for the ****.org domain it is working (i have some interl host overrides).

thx

SteveITS

@chris1284 is the answer a private IP?
https://docs.netgate.com/pfsense/en/latest/services/dns/rebinding.html#dns-resolver

chris1284

@SteveITS yes, the answer should be an adress from 192.168.2.0/24. the rebind-domain-ok option is set for home.arpa. the domain override lists includes also both domain. for the ***.org it is working. for home.arpa not

SteveITS

@chris1284 Well I’ve used Resolver and it works there. You might try that and set it to forward. It basically replaced Forwarder years ago.

chris1284

@SteveITS thx, with dns resolver it worked directly