At Wed, 17 Apr 2002 11:52:52 +0200, Hesham Soliman wrote: > >> Well, entities performing the server role of DHCP only answer >> Inform requests when (they think) they have something useful to >> say. The specific mechanism by which multiple entities could act >> in the DHCP server role on a single node > > But it doesn't have to be a single node. There maybe multiple nodes, > that what I don't understand.
I don't think I understand what it is that you don't understand. :) If a node that supports a DNS server choses to do so by somehow inserting its address into a DHCP server on another node, that's ok, but it's not necessary, and some people are concerned about that approach because of fate sharing issues, so it'd probably be better for each node that offers DNS service to answer the appropriate DHCP Information Request messages for itself. The point, however, is that the client doesn't care either way. > The rest of the discussion above is simply saying don't use the DNS > request to discover the DNS, send a DHCP message first and get > more. But what happens if you have more than one server pretending > to be a DHCP server? Does the RA send the request to a multicast > address and filter the replies? No "pretending" involved. DHCP allows multiple servers, DHCP clients cope, and DHCP relay agents just relay. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
