Peter Hardy wrote:
Uh, I mentioned dynamic DNS in passing earlier. The Linux DHCP client
has hooks built in to issue DNS updates whenever it gets a new lease.
Another alternative is a daemon that polls the IP address and updates
a service like http://dyndns.org/ whenever it notices the IP address
changing. I'm using one of these to point casa.dyndns.tv at my ADSL
link, which is notorious for changing its address a dozen times on a
bad day. But the hostname always resolves to the current address, and
there's very little stopping me from registering, say,
stibbonsmegacorp.com, putting a zone on an external name server (like,
say, the free service offered by xname.org), and CNAMEing it to my
dyndns hostname.
No, I don't consider it terribly suitable for a commercial operation
either, but there's no pressing technical reason why not.
But really, this is getting why out of scope for a discussion on DHCP.
Just a footnote: one CANNOT register to be authoritative for a set of
public ip addresses that
one does not own. One has to pay (or be authorized by) the owner of the
public ip addresses to use
it for the services previously mentioned.
O Plameras
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
