[Bug 1247803] Re: dnsmasq temporarily breaks DNS resolution when starting for the first time

[Philip Potter]

I agree that the postinst is a better place than the init script to run
"resolvconf -u".

I'm not sure that it should be conditional on IGNORE_RESOLVCONF though -
given that the update script will be run next time anything touches
resolvconf, what's to be gained by not running it in the postinst? And
why stop there? Why not also make it conditional on ENABLED=0?

I've created a branch with an unconditional "resolvconf -u" in the
postinst. I'm new to launchpad and bazaar so I'm not sure what the next
step is -- do I propose a merge? Do I attach a patch to this ticket?

-- 
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/1247803

Title:
  dnsmasq temporarily breaks DNS resolution when starting for the first
  time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1247803/+subscriptions