Comment 17 for bug 1010724

I looked at this carefully; and wrote a (I hope) pretty complete blog post explaining the situation:
http://blog.cyphermox.net/2012/08/bug-1010724-why-doesnt-dnsmasq-listen.html

I'll mark prioritize this down to Wishlist for now, since there doesn't in fact appear to be lag caused by the current setup. It's going to be something to revisit later should there be time to look into the situation, but I'm not going to worry too much about it unless there's clearly an issue.

This is just a prioritization for the development work on NetworkManager by Ubuntu developers maintaining the package. It basically just means that *I* won't spend time looking into the situation further, but I'll be happy to sponsor patches should someone come up with a clever way to cover all the issues I noted in the above blog entry; namely:

- It should show up in /etc/resolv.conf; but that also seems like unnecessary duplication of information.
- Starting dnsmasq entries on ::1 may cause issues with other dnsmasq instances.

It was brought to my attention that draft-smith-v6ops-larger-ipv6-loopback-prefix-00 aims at fixing this, but it's going to take a while and lots of work for these solutions to be accepted and implemented.