I understand that the reason Ubuntu puts a [NOTFOUND=return] before dns is for performance reasons, however performance reasons should not cause usability problems, IMO. At the very least, as a user, I expect a way to control this behavior via some checkbox somewhere in my network preferences, or even better - during the installation process.
Of course, if Jasey is correct and there is actually a bug in libnss_dns.so.2, then the solution is probably to fix the bug rather than go around it...
Confirmed this on both Jaunty and Karmic 32bit.
I understand that the reason Ubuntu puts a [NOTFOUND=return] before dns is for performance reasons, however performance reasons should not cause usability problems, IMO. At the very least, as a user, I expect a way to control this behavior via some checkbox somewhere in my network preferences, or even better - during the installation process.
Of course, if Jasey is correct and there is actually a bug in libnss_dns.so.2, then the solution is probably to fix the bug rather than go around it...