> Note that in a registry, there's an ordering problem, too. Consider
> this case
>
> 1. Register example.org with some name servers.
>
> 2. Register ns1.example.org. It's not yet a name server, so you
> don't need an IP address, because no glue is strictly needed.
>
> 3. Update example.org, and add ns1.example.org as a nameserver.
>
> The problem is that in (3), _ex hypothesi_ you didn't collect the IP
> address in (2), so you'll have a delegation that can't be used (since
> you can't get to the name server without the IP address).
>
> Since this is a general problem when in-zone hosts are created in a
> registry, there are good reasons always to collect and store IP
> addresses for host objects (or whatever analogous thing you use in
> your protocol) that are in-zone.
>
> --
> Andrew Sullivan 204-4141 Yonge Street
> Afilias Canada Toronto, Ontario Canada
> <[EMAIL PROTECTED]> M2P 2A8
> jabber: [EMAIL PROTECTED] +1 416 646 3304 x4110
so WHO is the "owner" of that IP data, the zone admin
for "example.org" or the machine admin for "ns1.example.org"?
historically, the HOST has had an independent admin, precisely
because they control the IP's used by the machine, not the zone
admin.
--bill
_______________________________________________
DNSOP mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dnsop
