DNS Resolver: Domain Override with OpenVPN
-
Yes, I can query the DNS on HOME LAN directly and it works. It is manually entered into several machines. That is why I was confused, I don't know why DNS Resolver won't work with it.
I tried several options for Outgoing Network Interfaces (All, LAN, local VLAN, WAN, etc) but that does not have an effect. External domain resolution is working ok, but anything from the Domain Override field will not resolve.
-
The setting that I am most unsure about is the "System Domain Local Zone Type". The default is Transparent.
The DNS server on the HOME LAN is Windows Server 2012. Do I have to use a specific "System Domain Local Zone Type" for it to work with my DNS server?
-
Did you set your ACL?? Your coming from another network, your going to have to edit the ACL to allow them to query it.
You can change it from transparent, not a fan of that default mode either. Mine is set to static.. Transparent will try and resolve, so for example if I try and resolve something.local.lan that does not exist I don't want it trying to resolve that. Since I know for sure there is no .lan tld no reason to even send that query. This also stops any bad suffix search like something.local.lan.local.lan from going out.
I wold assume you have to edit your acl for your other network and then you can query.
-
As far as I can tell, Windows Server 2012 DNS server does not have ACLs for who can make a query. Also, we already have another site where all clients query this remote DNS server directly and we did not set up any ACLs for these remote clients. Yes, some of them are domain members but many of them are not, for example printers and iPhones that are successfully making DNS queries from this remote network. This is why I don't understand what is stopping DNS resolver. If other devices can use the remote DNS server, why can't DNS Resolver make queries?
-
- Check the states at REMOTE pfsense, at least you will know on which interface your dns resolver sends packets for HOME DNS.
- is pfsense at HOME is default gateway for DNS server?
-
- I don't know what it means to "check the states"
- Yes, pfsense at HOME is the default gateway for the Windows Server 2012 DNS server.
-
your not doing query to your home dns, your doing a query to unbound are you not? And it does a query to your home dns server. That is what a domain override is..
So yeah unbound has acl..
If your doing a query directly to your 2012 server, that would be an issue with your 2012 server not pfsense if its not answering.
Vs coming home and domain overrides.. Lets just be clear.. Where is your client doing a query to what IP? What is this IP.. If its not doing a query to unbound on pfsense, what does domain overrides have to do with anything?
-
- I don't know what it means to "check the states"
- Yes, pfsense at HOME is the default gateway for the Windows Server 2012 DNS server.
Diagnostics -> States
This will show all 'live' traffic (not explicitly blocked or dropped) -
your not doing query to your home dns, your doing a query to unbound are you not? And it does a query to your home dns server. That is what a domain override is..
So yeah unbound has acl..
If your doing a query directly to your 2012 server, that would be an issue with your 2012 server not pfsense if its not answering.
Vs coming home and domain overrides.. Lets just be clear.. Where is your client doing a query to what IP? What is this IP.. If its not doing a query to unbound on pfsense, what does domain overrides have to do with anything?
Remote client 10.1.1.51 queries pfSense DNS Resolver at 10.1.1.1. This works for non-local domain names. Domain override points back to the HOME DNS at 192.168.9.3 (Windows Server 2012 DNS). When client 10.1.1.51 queries 10.1.1.1 for a host in the local domain, resolution fails. 10.1.1.51 can resolve local hostnames if it uses 192.168.9.3 as it's DNS server, but not if it uses 10.1.1.1.
The ACL is blank in the DNS Resolver at 10.1.1.1. Is it necessary for me to populate that list in order for the domain override to 192.168.9.3 to work correctly?
-
I have tried adding the networks to the unbound ACL but this has no effect. I'm still banging my head against the wall as the why the Unbound domain override works locally but not at the remote sites.
-
I installed Wireshark on the HOME DNS controller.
On the HOME LAN:
DNS query for a host in the domain override: a DNS query/response shows in wiresharkOn the REMOTE LAN:
DNS query for a host in the domain override: nothing is displayed in wiresharkIt appears that the DNS requests from Unbound on REMOTE LAN (for Domain Override hosts) are not making it back to the DNS server on HOME LAN. But why? No firewall rules in place to block it, everything in place to allow it. ??
-
Services / DNS Resolver / General Settings
Outgoing Network Interfaces
All - does not work
Select Localhost, WAN, LAN, OPT (OpenVPN) -
Hi,
i have similar issues which hostname resolutions from the remote network.
@Aaron, any further progresses? -
"It appears that the DNS requests from Unbound on REMOTE LAN (for Domain Override hosts) are not making it back to the DNS server on HOME LAN. But why? No firewall rules in place to block it, everything in place to allow it. ?"
That that server is working and he allows.. Did the traffic actually get there? Sniff on the server to see if you see the query, etc.
-
I had this issue as well with DNS Domain Overrides to MS DNS over OpenVPN.
To fix I had to:
- Disable DNSSEC
- Select outbound Interfaces as ALL.
I originally had Outbound Interfaces it as WAN. It appears that OpenVPN interfaces are implicitly included under all. They cannot be explicitly selected.
