On 10/27/22 1:16 AM, Marco Moock wrote:
Hello,
Hi,
how do ISPs automatically create the reverse and forwaring zones for their customers IP pools?
I think it might be out of scope for what you were asking about, but I believe the following is an alternative approach.
For example one of their clients has the IP 2001:db::3.
So for clarity, we're talking about 2001:db:0:0:0:0:0:3. (I think. I'm on my first cup of coffee.)
This is a singular IP (presumably link-net) for a customer. So there would be exactly one forward AAAA and one reverse PTR record.
I remember years ago that DHCP servers could be configured to dynamically update the forward and / or reverse zone when providing a lease to a client.
With this in mind, the forward and reverse zones would be roughly the size of the number of customers thus not blossoming ~> exploding into something that is tantamount to a DoS.
Its reverse zone 3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.d.0.0.1.0.0.2.ip6.arpa includes a PTR pointing to 3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.d.0.0.1.0.0.2.isp.example.org This has an AAAA record of 2001:db::3. Is it possible to let bind create that automatically for certain zones?
Aside from $GENERATE, which others have talked about exploding the zone, I'm not aware of any way to have BIND /initiate/ the change to zone content / data (for this).
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
