[FS#847] resolv.conf no longer points at local dnsmasq instance
LEDE Bugs
lede-bugs at lists.infradead.org
Wed Jun 14 16:00:58 PDT 2017
The following task has a new comment added:
FS#847 - resolv.conf no longer points at local dnsmasq instance
User who did this - Kevin Darbyshire-Bryant (kdarbyshirebryant)
----------
Am confused 'cos I didn't mention anything about DNAT port rewriting.
My setup is straightforward in that there's a single dnsmasq instance handling dns,dhcpv4&v6 across a few interfaces/subnets. It listens on port 53 on all subnets.
With the commit in place, /etc/resolv.conf is sym linked to /tmp/resolv.conf which is symlinked (in error) to /tmp/resolv.conf.auto
resolv.conf.auth points at the upstream recursive resolvers (google in this case, both ipv4 & v6)
Based on your rules/explanation (there's only 1 instance of dnsmasq), I don't understand why /tmp/resolv.conf doesn't point at 'loopback'.
----------
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=847#comment2799
More information about the lede-bugs
mailing list