I've googled til my fingers bled and all I cna find are how-to describing how I cna set up djbdns to serve a home network (maybe I just didn't know what I was looking at?). Here's what I'm doing.
I have registered a domain (we'll call it foobar.com) and I intend on hosting it publicly from my home server, which is running on a cable modem that is fed a business-class service (ie, I pay a little more and they let me run servers from home [Cox Business Service, in case it matters to anyone]). Obviously, to run it from my home box I have to have a nameserver that is authoritative for the server. I asked Cox is they offered a nameserver to their customers just for this purpose. It was a long shot and didn't pan out. They don't. If I intend to run a website from home, I also have to run a dns server from home that will be authoritative for this domain. So I emerged djbdns (chosen because people said it was simpler and more secure than bind). I also ran dnscache-setup and tinydns-setup. This installed the apps to /var (/var/dnscachex and /var/tinydns/ and /var/axfrdns respectively). When I did this, all my home systems stopped being able to resolve names. They all use this one box as a router/gateway, so it stands to reason that when I hosed the dns settings in that one box, they'd all come tunmbling down. Looking in the /etc/resolv.conf file shows that it is pointing to itself as the nameserver (using the external IP, not 127.0.0.1). When I replaced that with the original resolv.conf that points to Cox's dns servers, everything started working again. I changed /etc/resolv.conf to point to 127.0.0.1 to see it that made a difference. It just made the name resolution error out faster (unknown host error when I ping a known domain). I put the nameserver back to the way djbdns set it (pointing to my external IP) and checked the /var/dnscachex/root/servers/@ file. That file contains the 2 Cox dns servers, like I beleive it's supposed to. Basically, I'm swinging in the wind here. I'm a newbie in the dns arena, but willing to read and learn. Still, the install didn't go as transparently as I'd have liked since afterward, I couldn't resolve anything. Note that I can't resolve anything on any box on the nertwork OR on the server itself, so this isn't a persmissions issue, I don't think. I need a how-to guide that talks about doing what I need done. I don't care to use the proxy dns (dnscachex) and only need the content dns (tinydns) to feed the rest of the world my external domain ip. And of course, in the process, I'd like to retain the ability to resolve other domain names. ;-) Any help whatsoever would be appreciated. -Tom Caudron -- [EMAIL PROTECTED] mailing list
