On Fri, 09 Jun 2006 23:14:06 +1200 Don Gould <[EMAIL PROTECTED]> wrote:
> http://www.aboutdebian.com/dns.htm seems to be the best link so far... > > However, not having read it fully, it doesn't seem to explain how to set > up ddns to update your own zone on your own lan... thou, it might do as > well, I might not have read it properly. > > Most of the links I've looked at in the last 10 mins all seem to refer > more to the assumption that you're setting your server up for ddns on > your isp. > > Cheers Don We had this conversation a week or so ago. Dynamic DNS services update your public domain's DNS record to public IP address. eg I use the dyndns.org service to associate the ip address i get from orcon to a domain rout.dyndns.org. But that is stuff all use for a private lan behind a NAT firewall using a private address range. For that you have a number of options including: 1. Use /etc/hosts on all your linux and windows machines. Difficult to maintain. The internet started this way but became too difficult to maintain for obvious reasons. Its impractical if you are using dhcp or your IP addresses may change for some other reason. 2. Set up an internal DNS service using the standard dns server software. However again, unless you are using static ip addresses it is difficult to integrate with dhcp 3. IMHO on a small soho lan the best way is to use dnsmasq. http://thekelleys.org.uk/dnsmasq/doc.html dnsmasq provides integrated dhcp and dns, so when a machine asks for an ip address its hostname gets added to dns. For addresses that dnsmasq cannot resolve locally it goes out to external dns servers, usually your ISP's. It completely solves the integration of dhcp and dns. ipcop and other firewall distros use it. > > Don Gould wrote: > > > Nick Rout wrote: > > > >>On Fri, 09 Jun 2006 19:44:14 +1200 > >>Don Gould <[EMAIL PROTECTED]> wrote: > >> > >> > >> > >>>However ddns is another solution. > >>> > >>> > >> > >>Can we have a reference to a howto? > >> > >> > > Not from me sorry, I haven't done it before, it just occured to me > > that a ddns client on each machine with a ddns server running on your > > fw would be quite a good answer. > > > > However, I'm going to look into it because I've got the same issues on > > my network and the community thing I'm working on is going to end up > > with the same. > > > > Time to do some googling I guess. > > > > Cheers Don > > >
