[FS#847] resolv.conf no longer points at local dnsmasq instance

[LEDE Bugs]

A new Flyspray task has been opened.  Details are below. 

User who did this - Kevin Darbyshire-Bryant (kdarbyshirebryant) 

Attached to Project - LEDE Project
Summary - resolv.conf no longer points at local dnsmasq instance
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - On recent builds /etc/resolv.conf now contains external nameservers and no longer points at 127.0.0.1 or ::1.  Thus the router is unaware of internally handled name/ip mappings handled courtesy dnsmasq.

https://git.lede-project.org/?p=source.git;a=commit;h=a53f8ba6771de64c9c82a2e6867791226f3003cb looks suspicious.  I have no idea what problem it is trying to solve.  I suspect the dnsmasq init script has achieved sentience and this is the beginnings of skynet.

I'm happy to provide configs, but not via this bug tracker.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=847