Comment # 3 on bug 1183123 from Michael Matz

(In reply to Jonathan Kang from comment #1)
> (In reply to Michael Hirmke from comment #0)
> > Using the combination nfs, systemd, NetworkManager and nscd I always run
> > into the problem, that NetworkManager states the system being online, before
> > it is really online. In this case, all nfs mounts by systemd are failing,
> > because the names of the servers can't be resolved at that time.
> > Later NM's nfs dispatcher script works, but also comes too late for some
> > services, that are started by systemd in the meantime.
> > Using Networkmanager-wait-online for these services doesn't help either,
> > because - as stated above - NM believes it is online long before it really
> > is.
> > 
> > Disabling nscd in this case cures the problem. After doing so, even systemd
> > is able to mount the nfs shares. Everything is placed in the correct order.
> 
> NetworkManager has dropped nscd support quite a long while ago. So I guess
> it's
> nscd that interferes DNS resolution.

Define "dropped".  What support was there to start with?  nscd cannot simply be
ignored by NetworkManager, it needs to work together with the system DNS
resolver.  E.g. if it changes any config behind the back of system DNS
resolvers
knowledge (for instance by an intermediary like dnsmasq and changing only _its_
config) then nscd needs to be made aware of that, so that it may drop outdated
information.

> > Is this a bug? Or is it ok for this scenario to disable nscd? Or do I have
> > to use special settings for this case?
> 
> What do you use nscd for? You can disable nscd if you don't need it.

nscd is a default component of the system.  Advising users to disable it is
not the right course of action, though it may be used as a work around.