<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>It's all up to the client what it does with the information DHCP
passes out.<br>
<br>
It's been my experience that the order DHCP gives on the
domain-search<br>
is the order the client uses.</p>
<p>Bill<br>
</p>
<div class="moz-cite-prefix">On 10/15/2019 11:23 AM, Surya Teja
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+0Ac3wwLn29HMakre=zkEwDiB2y+oCG=fBooPmz2vqv9WvS+A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Hi ,
<div dir="auto">If the option 119 is granted by the dhcp server
to the dhcp client, will the perference of the domain value
matters?</div>
<div dir="auto">Ex: option domain-search "<a
href="http://example.com" moz-do-not-send="true">example.com</a>","<a
href="http://example1.com" moz-do-not-send="true">example1.com</a>","<a
href="http://example2.com" moz-do-not-send="true">example2.com</a>"
will it makes any difference if the order changes ?</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, 14 Oct 2019, 19:44
dave calafrancesco, <<a href="mailto:dcalaf@drakkar.org"
moz-do-not-send="true">dcalaf@drakkar.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">You want to
set this:<br>
<br>
option domain-search domain-list;<br>
<br>
The domain-search option specifies a ’search list’
of Domain Names to be used by the <br>
client to locate not-fully-qualified domain names. The
difference between this option and <br>
historic use of the domain-name option for<br>
the same ends is that this option is encoded in
RFC1035 compressed labels on the <br>
wire. For example:<br>
<br>
option domain-search "<a
href="http://example.com" rel="noreferrer noreferrer"
target="_blank" moz-do-not-send="true">example.com</a>", "<a
href="http://sales.example.com" rel="noreferrer noreferrer"
target="_blank" moz-do-not-send="true">sales.example.com</a>",<br>
"<a
href="http://eng.example.com" rel="noreferrer noreferrer"
target="_blank" moz-do-not-send="true">eng.example.com</a>";<br>
<br>
Dave<br>
<br>
On 10/13/19 09:52, Surya Teja wrote:<br>
> Hi I want to send multiple domains information to the
dhcp client from the dhcp server, but the <br>
> option domain-name is taking only one domain, I cannot
give comma separated list for it, On <br>
> surfing the internet I found the option 119 where we can
give comma separate list.<br>
> I have added it to my config but the dhcp client is not
getting the info, because in the dhcp <br>
> client request packet it is not asking for option 119<br>
> Is there any way that dhcp server can offer all the
options defined in its scope modules to the <br>
> client irrespective of the client asking for the
specific option or<br>
> Any way of introducing the specific option in the request
packet from the client to dhcp server <br>
> and make use of it.<br>
> <br>
> <br>
> <br>
> <br>
> Thanks in advance.<br>
> <br>
> <br>
> _______________________________________________<br>
> dhcp-users mailing list<br>
> <a href="mailto:dhcp-users@lists.isc.org"
target="_blank" rel="noreferrer" moz-do-not-send="true">dhcp-users@lists.isc.org</a><br>
> <a
href="https://lists.isc.org/mailman/listinfo/dhcp-users"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
> <br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
dhcp-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a>
</pre>
</blockquote>
</body>
</html>