Comment 1 for bug 862928

I have found a way to reconfigure the system to resolve the problem. However, there is still a bug in the default configuration of Ubuntu.

The problem DOES appear to be name resolution.

Even with bind9 installed, the local system is never configured to set /etc/resolv.conf to USE the local nameserver!

When I configured that manually, by editing /etc/resolv.conf, then rebooted, it properly exported the filesystems -- for
a single boot. But then NetworkManager overwrote /etc/resolv.conf with its own crazy idea of how to resolve domain
names, and on the second reboot, it failed to export the filesystems.

But this at least showed what the problem was. And enough talented sysadmins had already seen THIS problem that they came up with a big kludge script (apt-get install resolvconf) and patched all of the applications that love to clobber /etc/resolv.conf to call it. So after I installed the resolvconf package, and made sure that /etc/default/bind9 was set to "RESOLVCONF=yes" so that it would automatically inject localhost into resolvconf, everything started working.

This problem CLEARLY should be fixed in the default configuration. Forcing resolvconf and bind9 won't work, because the system can't know how to configure bind9 so it'll locally store a cache of the domain names that /etc/exports needs to resolve. I don't know how to fix this -- the complexities of upchuck are beyond me. I think you'll have to actually let upchuck know that, yes, /etc/exports MIGHT INDEED contain domain names and MIGHT INDEED have to look them up, so if domain service isn't yet working, then oops, DON'T RUN exportfs yet. Or, as an old programmer warrior often told me, "I can make your program run arbitrarily fast if you don't mind it producing the wrong answer." Upchuck has to produce the right answer -- THEN make things as fast as possible within that constraint.