Date: Tue, 26 Feb 2002 22:58:53 -0600 From: "GB" <gregbrooks@blue-mouse.com> To: <freebsd-questions@freebsd.org> Subject: djbdns and freebsd Message-ID: <000401c1bf4b$74d0d4e0$0201a8c0@CITYMOUSE>
next in thread | raw e-mail | index | archive | help
Folks, I'm having a devil of a time setting up djbdns (see excerpt of note below). I know this isn't the right list for djbdns questions, but that particular list has lower traffic by an order of magnitude. Rather than tie up freebsd-questions bandwidth, I'm asking any helpful soul who wants to walk me through this to e-mail me personally. If we solve it before the Local Unix Consultant shows up on Thursday, I'll donate half of what I would have paid the consultant to the FreeBSD Foundation. Many thanks, Greg * * * * :::BEGIN SET-UP AND PROBLEM INFO::: Setup: Clean install of FreeBSD 4.5 w/KDE desktop. IP address of 192.168.1.7 and host/domain of mouseland.quadkings.com (yes, it's a silly name). What gets done just fine: * Use ifconfig to add a second IP address (192.168.1.8 with netmask of 0xffffffff). The second ifconfig command was included in rc.conf so the address would be there after reboot. * Add tinydns, dnscache and dnslog users (no shell, no password) * Make install djbdns and dependencies * Use dnscache-conf to tell dnscache to listen on port 192.168.1.8 * start dnscache service * set up tinydns (i.e., add host/domain/MX info into a text file and then make within that directory to create a cdb file). * Start tinydns service Honestly, I haven't gotten around to testing tinydns because I keep getting hung up on the resolver component (dnscache). I've had a lot of good feedback from the dnsdjb e-mail list on how to properly configure the data file, however, so I think that will go fine. Things I've tried: * Be default, dnscache listens to the assigned IP and no other. I've tried setting it up to listen on both 192.168.1.8 (and assigning appropriate inbound permissions using the touch command) so other machines on the LAN could use it; I've also tried using 127.0.0.1 so only the server would use it. I can get other machines on the LAN to ping the 192 address, but can't resolve addresses. What makes me think I'm doing something really wrong in the djbdns setup is that I can't even get the server to resolve on 127.0.0.1 -- the simplest configuration, and one that should have no conflicts. Other issue: the Linksys SOHO router/firewall gives you no way to send port 53 traffic to both IP addresses from the outside world other than to list port 53 twice in the forwarding-setup screen. This didn't seem like a problem (after all, the queries to dnscache would all be coming from inside the LAN), but I thought I'd mention it. Even if we DO get dnscache to work, I might not be able to use it to serve the other machines on my LAN because I can't port-forward the same port to two different IP addresses, can I? I guess the bottom-bottom line is that I don't HAVE to have dnscache running -- if tinydns will run, it will serve up the SOA data required to host domains. But as long as it's installed, I'd like to try and get dnscache to work because I like the speediness of the local resolver (hell, I got the damned thing to work on win2k's DNS server). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000401c1bf4b$74d0d4e0$0201a8c0>