Re: Two simple openssh questions...

From: Richard E. Silverman (res_at_qoxp.net)
Date: 08/27/03 

Date: 27 Aug 2003 15:13:56 -0400

>>>>> "NKG" == Nico Kadel-Garcia <nkadel@verizon.net> writes:

    NKG> Providing DNS in such situations, especially in DHCP based client
    NKG> configurations, is difficult if not painiful to set up
    NKG> correctly. You basically have to get the DHCP data, rewrite your
    NKG> named.conf on the fly

It would the appropriate zone file, not named.conf...

    NKG> generate reverse DNS tables on the fly, and pray that your DHCP
    NKG> doesn't change for long before your scans of DHCP updates catch
    NKG> it and rebuild your reverse DNS tables.

    NKG> Awkward, painful, and unwise.

I have done exactly this at various places, and it was neither awkward nor
painful. things. A cron job periodically scans the dhcpd state for
new/changed/removed leases, checks in changes to the appropriate named
zone file, and reloads the reverse zone. There's no need to "pray;" so
they're a little out of sync depending on how often leases change --
that's better than no reverse entries at all.

I can't see why it would be "unwise," in any event.

Anyway, a better approach these days is to have dhcpd use DNS dynamic
update to keep the reverse zone up to date. 

-- 
  Richard Silverman
  res@qoxp.net