DHCP 4.2.3-P2 doesn't remove TXT and PTR records but only A

Eddie Lania e.lania at elton.nl
Thu Feb 16 07:24:00 UTC 2012


Andris,

Thanks for the advice.

The clients in our network however are not allowed to do updates to the DNS themselves.
So, this is not a useful solution for me.

Regards,

Eddie.


-----Oorspronkelijk bericht-----
Van: dhcp-users-bounces+e.lania=elton.nl at lists.isc.org [mailto:dhcp-users-bounces+e.lania=elton.nl at lists.isc.org] Namens Andris Kalnozols
Verzonden: donderdag 16 februari 2012 04:13
Aan: dhcp-users at lists.isc.org
Onderwerp: Re: DHCP 4.2.3-P2 doesn't remove TXT and PTR records but only A

> When dhcpd receives DHCPRELEASE for a client, it expires the lease for
> the client and removes only A record of the client but ignores PTR and
> TXT records.
> When a lease expires naturally without a DHCPRELEASE message, every
> resource record regarding the client is discarded.
>
> I think it is a bug.
>
> On Tue, Feb 14, 2012 at 4:29 PM, Eddie Lania <e.lania at elton.nl> wrote:
> > I was wrong, the records are only not removed on dhcprelease.
> > So, when a client sends a release then a PTR and TXT record are left behind.
> >
> > But if a lease expires then all records (PTR, TXT and A) are deleted.
> >
> >
> > crocket <crockabiscuit at gmail.com> wrote:
> > Subject: DHCP 4.2.3-P2 doesn't remove TXT and PTR records but
> >          only A records when leases are released or expired.
> >
> > Thus, I can't use dynamic DNS updates.
> > I don't want any resource record left behind after clients cut off leases.
> >
> > Will it be fixed in future releases? or can it be fixed by changing
> > the configuration?

In an effort to limit the perceived level of brokenness, I wish to
demonstrate that the 4.2.3-P2 DHCP server does work as intended when
using the following dynamic DNS related statements:

  ddns-update-style interim;
  allow client-updates;           # clients will update their own A records
  ddns-ttl 1200;                  # match that of the Microsoft DNS server
  option fqdn.rcode2      255;    # tell clients that the server understands
                                  # the fqdn option and will do the PTR update

  subnet 15.4.88.0 netmask 255.255.248.0 {
    ...
    zone 95.4.15.in-addr.arpa. {
      primary  15.0.48.4;
      key      secret;
    }
    ...
  }

Doing an "ipconfig/release" on a Windows system signals the DHCP
server to do the expected action:

  Feb 15 16:05:22 lpans2 dhcpd: DHCPRELEASE of 15.4.95.185 from
    00:30:6e:d7:31:09 (sp500-old) via eth0 (found)

  Feb 15 16:05:22 masterns named[1229]: update: info: client
    15.243.224.30#39909: updating zone '95.4.15.in-addr.arpa/IN':
    deleting rrset at '185.95.4.15.in-addr.arpa' PTR

The client also deletes its A record.

------
Andris

_______________________________________________
dhcp-users mailing list
dhcp-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users



More information about the dhcp-users mailing list