At 16.49 -0700 00-06-29, Randy Bush wrote:
> > there are already requirements in the draft for a registry to not produce
>> A records for name servers registered in a TLD for which the registry is
>> not authoritative.
>
>so, if a nameserver serves domains in two or more registries, the nameserver
>must be registered in each of the registries?
It is already like that today, so, yes, you have to. I tried to when
being on the NSI registry advisory board change this so IF the NS
refers to a host in a different TLD, only the name is registered in
the registry and not the IP-address. That failed. One wanted to have
the IP-address there.
Secondly, there is a rule though that no glue is to be generated
unless it is really needed (i.e. the registry is authoritative for
the domain where the hostname the NS refers to).
On the other hand, NSI registrar still have som _hughe_ problems if
you have a NS pointing to for example "ns.paf.se", and having a
domain which is in the ".com" domain. Try that, and then try to
change the IP-address of that ns.paf.se host at NSI registrar...
It doesn't work! (at least not one year ago)
And, NSI at that time also generated the glue for the host. Because
the IP address was impossible to change, and because glue was
generated --- I was VERY unhappy...
It is today _very_ confusing that NSI is trying to map and allow
changes given the IP-address, i.e. changes on A records using the IP
address as key. Because of this (as far as I can see) the NS record
for for example webweaving.org is set to the nameserver for the
sigz.net, which is not true. I.e. they happen to have the same
IP-address, but the hostnames and zones are handled by different
administrative handles in the registry database.
I see because of this abilities for the administrative body for one
of the domains which have nameservers on the same host to change the
zone information for the other...
I.e. what happens if now the administrative person for the
webweaving.org domain want to move the NS away from 192.71.228.17?
Can he change the IP-address of the nameserver of his (regardless of
name) and because of that also change the IP-address of the
nameserver for sigz.net zone (regardless of name)? That should not be
possible.
I want to be able to have
example.com. IN NS a.example.com.
a.example.com. IN A 192.168.1.1
example.org. IN NS a.example.org.
a.example.org. IN A 192.168.1.1
There should be _no_way_ the administrative body for example.com can
change the NS (name or IP-address) for the a.example.org domain, and
because of that the IP-address for a.example.org. He should only be
able to change the IP address of a.example.com.
paf
---------
See http://www.nsiregistry.com/maillist/rrp/
for message archives and subscription management information.
This archive was generated by hypermail 2b29 : Mon Jul 03 2000 - 13:38:49 EDT