DHCPD v.3 provides dynamic DNS services. Unfortunately, tinydns does not support this, but BIND (versions 8 and 9) does. Consider running DHCPD v.3 and BIND on an internal server, behind your firewall. I've run DHCPD, BIND and dnscache together at two sites for more than a year with no problems.
-Richard > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Chad Carr > Sent: Friday, April 26, 2002 6:47 AM > To: Mark Ivey > Cc: [EMAIL PROTECTED] > Subject: Re: [Leaf-user] Bering: How do I get my dns & dhcp servers to > work together? > > > On Fri, 26 Apr 2002 00:38:40 -0700 > "Mark Ivey" <[EMAIL PROTECTED]> wrote: > > > I'm running a Bering firewall, and I want all my local > computers added > > to my dns server. This is so I don't have to try to figure out what > > address a computer got before I can access it. How can I > get my dhcp > > server to update my dns server? Should I be running > tinydns, dnscache, > > or both? Thanks! > > This is called dynamic dns, and you will need to run both tinydns and > dnscache (assuming you want a caching recursive dns resolver for your > internal network). > > Take a look at the script at > http://www.thismetalsky.org/files/dhcp_dns > > It monitors your dhcpd leases file for new entries, then puts > matching A > and PTR records into your tinydns data file and reloads it. > > There is a trick to running tinydns and dnscache on the same machine > unless you use two ip addresses. Run tinydns on localhost, > dnscache on > your internal address and forward queries for your domain to > localhost. > That way, your internal hosts get the dynamic entries. Unfortunately, > dnscache will never return a true authoritative response for your own > domain, but what the heck. You can do it right or some way > that works. > > You forward the queries from dnscache to tinydns by putting a > file in the > /etc/dnscache/root/servers directory for your domain that points to > localhost, e.g. franzdoodle.com file would contain 127.0.0.1 > > Okay, That is from memory, but I think it is mostly > accurate. There are > probably some other pitfalls that I've forgotten, so take a look at > http://www.fefe.de/djbdns/#sameip for all the gory details. > > I use this setup for a department of about 100 engineers on a > /22 subnet > with 500 or so Windows, Solaris, and Linux dhcp machines. It > works well > and replaced an "equivalent" Windows NT setup that actually > needed to be > maintained (rebooted) frequently. Nobody even thinks about > our dhcp/dns > server anymore unless they need to add static records. Ahhh, > the way it > should be. > > Later. > Chad Carr > > _______________________________________________ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
