Yes, writing an NSS plugin would have been the next resort. It's certainly easier than getting glibc and all other resolver libraries to support ports other than 53. But it's more difficult than the solution that was actually adopted, namely, to make nm-dnsmasq listen at 127.0.1.1.
(BTW, I don't know if it has been mentioned earlier in this thread, but one drawback of the adopted solution (i.e., making nm-dnsmasq listen at another address than 127.0.0.1) is that it breaks name service on machines that have no /etc/resolv.conf. In that case the resolver acts as if "nameserver 127.0.0.1" were specified. Granted, Ubuntu Precise and higher machines should *not* lack /etc/resolv.conf.) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
