http://wiki.rivendellaudio.org/index.php?title=DHCP_vs._static_IP_addresses&feed=atom&action=historyDHCP vs. static IP addresses - Revision history2024-03-29T08:42:02ZRevision history for this page on the wikiMediaWiki 1.26.4http://wiki.rivendellaudio.org/index.php?title=DHCP_vs._static_IP_addresses&diff=18&oldid=prevHiggles: Created page with "<PRE> On Tuesday 14 August 2007 16:42, Federico Grau wrote: > Has anyone used DHCP (dynamically assigned) IP addresses with Rivendell > workstations? I see in rdadmin that th..."2018-02-21T15:14:26Z<p>Created page with "<PRE> On Tuesday 14 August 2007 16:42, Federico Grau wrote: > Has anyone used DHCP (dynamically assigned) IP addresses with Rivendell > workstations? I see in rdadmin that th..."</p>
<p><b>New page</b></p><div><PRE><br />
On Tuesday 14 August 2007 16:42, Federico Grau wrote:<br />
> Has anyone used DHCP (dynamically assigned) IP addresses with Rivendell<br />
> workstations? I see in rdadmin that there are several fields referencing a<br />
> Rivendell hosts' IP address and hostname. We have experienced problems if<br />
> they don't all match ... so I can't really imagine how things would work in<br />
> a DHCP environment where the IP and hostname are potentially changing<br />
> frequently.<br />
<br />
In a nutshell -- DHCP won't work well in a Rivendell environment. Early on in<br />
the design process, I did experiment with using DNS to resolve hostnames.<br />
Because of the non-deterministic nature of the DNS protocol (recursive<br />
lookups, etc), it didn't play at all nice with realtime performance. (When<br />
the user hits PLAY, it needs to play *now*, not when some name server three<br />
lookups away gets around to resolving a name.) Hence, the static IP address<br />
entries in the RD database.<br />
<br />
Cheers!<br />
Fred Gleason</div>Higgles