[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting

[John Hupp]

I thought I was done with this kind of issue, but I may be back for
more.

It turns out that the only LTSP client that boots normally is the one
that I was doing all of the above troubleshooting on.  Others that I
have tried in my little 2-PC setup all stop at a blank/black screen
after successfully getting to the Lubuntu splash screen.

I have now set up forwarding of the client syslog messages to the
server, and the log always ends with a string of ntpd items, the last of
which is "ntpd[1314]: Listening on routing socket on fd #24 for
interface updates"

I found this other Ubuntu Precise bug (#999725)
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/999725 which reports
that ntp is being started before DNS resolution is available.  A quick
scan of the initial comments shows that the discussion revolves around
network-manager's handling of network configuration.  The bug is
currently marked Expired due to inactivity.

Bug #999725 seems to involve some of the same issues as the ones dealt
with here.

Comments?  Troubleshooting?  Workarounds?

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