RE: [dhcwg] Review of Service-Discovery-Type options in DHCP

For service/server discovery via DNS, might not the DNS search
list make more sense? In the simplest case, Domain Name = DNS
Search List, but in more complex networks that is not the case.

Domain name might be division.company.com wereas search list
might be division.company.com and company.com. In this case,
you'd locate the service whether it was at the division level
or corporate level. A mail server might be at the division level.
An NTP server might be at the corporate level.

This point seems to have little to do directly with DHCP?

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]
Sent: Wednesday, July 17, 2002 1:41 AM
To: Ralph Droms
Cc: Stuart Cheshire; DHCP discussion list
Subject: Re: [dhcwg] Review of Service-Discovery-Type options in DHCP

> I have always thought of the "Domain Name" option as specifying the domain 
> name that the client should attach to its hostname to form its FQDN.  
> Stuart suggests a somewhat different definition - the "Domain Name" option 
> simply identifies the domain name for the network to which the client is 
> attached.  The client can then use that information in any way it wants: 
> to form an FQDN if it needs one, to form service names.
>

I think Stuart's definition is more generally correct.   The only time when 
the domain name option specifies the client's domain name is when the 
client doesn't have a domain name that it cares to assert.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg