So the fix to make it work the same would be to add 127.0.0.1 to resolv.conf manually?
Sent from my iPad > On Jul 11, 2014, at 6:19 PM, Dave Warren <[email protected]> wrote: > >> On 2014-07-11 10:04, Brian Caouette wrote: >> Why is it unbound doesn't report dns name for light squid and if I return to >> stock it does? In both of them I have enabled register static mappings yet >> unbound doesn't give the time to light squid in the reports were stock does.. > > When you use dnsmasq, pfSense adds 127.0.0.1 to the top of resolv.conf, and > therefore pfSense itself asks dnsmasq for local resolution and is able to > resolve local hostnames. > > However, when you use unbound, dnsmasq is turned off, so pfSense itself is > just using your configured DNS servers (or ISP DHCP provided ones, depending > on configuration) > > Assuming unbound does full resolution and doesn't forward, you can work > around this by listing 127.0.0.1 as your primary DNS resolver in pfSense. > However, if you do that, you'll have to make sure that pfSense isn't handing > out these DNS servers IPs to clients anywhere (DHCP server? OpenVPN?) > > And if you have unbound forwarding, obviously you can't include 127.0.0.1 or > unbound will forward to itself. > > Finally, pointing to 127.0.0.1 will partially break upgrades since pfSense > will come up without packages, and therefore without a DNS server, then it > will find itself unable to find pfsense.org to download packages. > > Ultimately the fix will be for pfSense to recognize unbound as a local DNS > server and add it to resolv.conf by default, similar to dnsmasq. > > -- > Dave Warren > http://www.hireahit.com/ > http://ca.linkedin.com/in/davejwarren > > > _______________________________________________ > List mailing list > [email protected] > https://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
