DNS resolver configuration Issue

[Gokulapandi]

In my pfSense firewall, I have set the pfSense IP address as the primary DNS server for both the LAN and OpenVPN clients.

Within the LAN, I host several internal domains, and I’ve configured host overrides in the DNS Resolver for these -. Additionally, I have an IPsec connection to an AWS account, where certain application load balncer DNS names (e.g., a1XXXXXXXXXXXXXXXXXXXX0.elb.eu-north-1.amazonaws.com) point to resources within a private subnet.

Now, I want to configure my network so that all types of domain names resolve correctly, including:

Internal LAN domains

Public internet domains

AWS private subnet domains (such as internal ALB DNS names)

I have disabled the dns forwarder.

Within my LAN network, I host a few internal domains. For those domains, I have added host overrides in the DNS Resolver. Its working as expected.

Cuurently, i am facing an issue with resolving the internal ALB DNS names from OpneVPN and LAN, but the same internal ALB DNS names are resolving in public.

Anyone suggest the solution ?

[viragomann]

@Gokulapandi
Add domain overwrites for your AWS domains and point it to the remote dns server.

[Gokulapandi]

@viragomann
Thanks, I have added that it's resolving when we are trying to ping but resolving in the nslookup command.

DNS lookup is working in pfsense firewall itself.

[viragomann]

@Gokulapandi
The DNS resolver doesn't hand out private IPs by default. You have to enable this with a custom option:

server:
private-domain: "<your-domain.tld>"

The server line is only needed if you haven't one already, otherwise you can write the private-domain line below of it.