>> (to provide local name resolution). If you're serving >external traffic to your any of your machines (like a webserver), BIND >9.2 has split >> DNS (allowing the same domain name to have both internal and >external IP addresses depending on the machine requesting), as does >djbdns > >Why exactly do you need to run your own dns if you want to run >a publicly available server?
Speaking for myself alone: I run dual homed external/internal DNS for the same reason I am running a web server, mail server etc. on my home network - just for the hell of it really and as a learning exercise. My ISP (paradise.net) provides secondary name service and mail bagging for no additional cost. I did try a public name service for about a week but found it to be unreliable. >Running the server is easy, and there are heaps of places to get a name >hosted on (many of which free)? Is running a DNS server any harder? You could also argue that there are plenty of places to get your web pages hosted for free too, but does it provide as much entertainment value as running your own? RE: DHCP discussion: DHCP version 3 supports dynamic DNS updates. I came across this DHCP-V3 implementation recently: http://www.isc.org/products/DHCP/dhcp-v3.html I haven't tried it since I don't have a permanent use for DHCP on my home network.
