Weird question about DNS resolution within a nested network
-
Ok so I'm on someone's network using pfsense to create my own network and stay separate from them (mostly)
and I'm using pfsense as a DNS resolver to resolve *.example.com to some servers/services on my network.
However, on the network above mine, they are not able to use my DNS to access my servers/services
I have tried configuring it so that they use my pfsense box as a DNS server, and then setup a nat rule allowing them to access pfsense and the servers/services (I verified from their network port 53 is open) and i have enabled DNS forwarding mode. However no dice, ever time i do a nslookup this is what i getnslookup example.com 192.168.0.34 (the pfsense box's IP from their network)
Server: 192.168.0.34
Address: 192.168.0.34#53** server can't find example.com: REFUSED
Anyone have any clue why its not working?
In the documentation is says this "In forwarding mode the DNS Resolver will forward DNS queries to the list of servers configured under System > General Setup or those obtained automatically from a dynamic WAN."
But im not entirely sure if its working or how to configure that. -
@Bubbadoge-0 said in Weird question about DNS resolution within a nested network:
** server can't find example.com: REFUSED
You need to make sure you allow some network to talk to unbound.. This would be in the ACLs - the auto is only going to allow lan side networks.. If your clients are upstream, ie pfsense wan they would not be allowed out of the box. You would have to add them to your ACL.
What do the upstream clients normally use for dns? You should prob just put in a domain override at that NS to know to go ask pfsense for example.com
-
@johnpoz yep that did it for me, just needed to allow their subnet in the ACL thank you.
