Comment 9 for bug 389006

I'm targeting this to Lucid since it effectively breaks connection sharing.

I can confirm that sudo killall -s HUP dnsmasq makes it work, so it appears to be a problem with the timing of /etc/resolv.conf when dnsmasq is started. Because dnsmasq is started with the no-poll parameter, it doesn't pick up on changes in resolv.conf all by itself. I would suggest we:

 * contact NM upstream to ask if no-poll is a deliberate decision, and the rationale
 * upload NM patched to NOT use no-poll when firing up dnsmasq, to verify that this fixes the issues with DNS and connection sharing