To:
"Bruce Campbell" <bruce.campbell@apnic.net>, "Robert Elz" <kre@munnari.OZ.AU>, "Harald Alvestrand" <Harald@Alvestrand.no>
Cc:
<dnsop@cafax.se>
From:
"Cricket Liu" <cricket@acmebw.com>
Date:
Fri, 26 May 2000 15:24:59 -0600
Sender:
owner-dnsop@cafax.se
Subject:
Re: root server load and dynamic updates.
> would a valid heuristic to adopt be to attempt the update in the forward > zone first (subject to controls discussed earlier), and only attempt the > reverse update if: > > a) the update succeeded, or > b) the data was already in the forward zone? > > (of course, also check that no PTR was present in the reverse zone in the > last case.) > > If someone configures mail.xa.xa as their name, tries to register that with > the root nameservers, and gets rejected, there's very little reason to go > try to install a pointer to the invalid name in the in-addr.arpa zone. That would only work if the Windows 2000 DHCP server were doing the updates for both the A and PTR RR. The default mode of operation has the DHCP server add the PTR RR and the DHCP client add the A RR. cricket