Date: Thu, 16 Jun 2005 16:44:40 -0400 From: Garrett Wollman <wollman@csail.mit.edu> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: current@FreeBSD.ORG Subject: Re: New dhclient broke multiple domains in domain-name Message-ID: <17073.58552.862249.81604@khavrinen.csail.mit.edu> In-Reply-To: <20050616201646.GC13900@odin.ac.hmc.edu> References: <200506161312.51857.jhb@FreeBSD.org> <42B1D823.5030108@errno.com> <20050616201646.GC13900@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Thu, 16 Jun 2005 13:16:46 -0700, Brooks Davis <brooks@one-eyed-alien.net> said: > The RFC is shockingly lacking in this area. It's rather odd that they > send a value for domain, but not for search (in resolv.conf). It's not > suprising that people ended up abusing this to set search. There is a standard (unless it didn't make it out of I-D) for doing this. The shocking thing is that isc-dhcp(d) has never supported it. I used to have something like this in my dhcpd.conf: #option domain-search-order code 119 = string; # # This was generated using the following command: # perl -e 'print "\3lcs\3mit\3edu\0\2ai\xc0\4\xc0\4\2w3\3org\0"' | hd # ...and represents the search-list lcs.mit.edu, ai.mit.edu, mit.edu, w3.org # in DNS compressed encoding. # #option domain-search-order 03:6c:63:73:03:6d:69:74:03:65:64:75:00:02:61:69:c0:0 4:c0:04:02:77:33:03:6f:72:67:00; AFAIK not even Microsoft clients bother to implement this. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17073.58552.862249.81604>