On 09/27/2013 05:42 AM, Dan Egli wrote: > I'm familiar with the ddns ability in dhcpd and named. In fact, at first I > was going to use them. But my understanding was that ddns doesn't update > the reverse pointers. I.e. it will insert a record into the DNS server that > box A is 192.168.0.15, but it won't insert the PTR to say that 192.168.0.15 > is box A in the in-addr.arpa zone. That's why I use the scripted method I > devised. Now if the ddns method DOES update the reverse pointers, that's > different. And then there's the point where I'd ask how well DHCPd would be > at applying changes to forward FILE A and reverse file A vs. forward file B > and reverse file A. Remember that there's two networks, each with > independent address ranges. But the way it's setup so far is that although > the DNS would contain two zone files for the address pointers (i.e. > a.upper.rec and a.lower.rec) there is only one zone file for the > in-addr.arpa reverse pointers. I don't know how well ddns would work that > way.
ISC DHCPD absolutely does update both forward and reverse ptrs. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
