On Mon, 2006-12-11 at 10:57 -0500, Peter Staubach wrote: > Ian Kent wrote: > > On Mon, 2006-12-11 at 09:16 -0500, Jeff Moyer wrote: > > > >> ==> On Mon, 11 Dec 2006 10:05:07 -0200, Fabio Olive Leite <[EMAIL > >> PROTECTED]> said: > >> > >> Fabio> On Mon, Dec 11, 2006 at 12:56:31PM +0900, Ian Kent wrote: > >> Fabio> > > >> Fabio> > Not valid at all. > >> Fabio> > And they are tolerated because the admin explicitly configures > >> DNS to > >> Fabio> > violate the RFC. > >> > >> Fabio> The sad thing is that mount(1) does no such validation, and allows > >> one > >> Fabio> to mount an NFS export on a hostname containing underscores just > >> fine. > >> Fabio> So we can end up in a situation where automount does not allow the > >> Fabio> user to configure a working NFS mount she has. > >> > >> Yes, and when coupled with the fact that some other vendors' products > >> allow this sort of thing by default, I think we may have to support > >> it. I'm a big fan of sticking to the RFC's, but in this case, I think > >> we should make an exception. > >> > > > > Ya .. I reality I don't feel as strongly as I made out. > > > > I did want to see if there was anyone else that did have an opinion > > though. > > > > I'll merge the patch unless anyone else feels strongly against it. > > Do we know which other vendors products support '_' as a valid character > in a hostname?
Bind can be configured to allow it, as you probably know, but the default has been to not allow it for several years now. I guess that many sites that have Windows machines with '_' in host names configure DNS to allow them or they probably use the Windows DNS. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
