ns_ip_* vs. ns_name_* in new Domainz system
Has anybody else seen instances in the new register where a domain has ns_name_* records, but no corresponding ns_ip_* records? For example, patho.gen.nz has: ns_name_1: dns1.clear.net.nz ns_ip_1: 203.97.33.1 ns_name_2: soa2.qsi.net.nz ns_ip_2: ns_name_3: tardis.patho.gen.nz ns_ip_3: 203.97.2.226 ns_name_4: medusa.blackops.org ns_ip_4: This makes me slightly nervous. Has anybody else seen this kind of thing for other domains? Are the current zone files running at ns99.waikato.ac.nz built from this new data, or are the old zone files still running? If the former, when will the first authoritative zone from the new system be loaded? (it looks like it will be worth checking). The fact that the hosts soa2.qsi.net.nz and medusa.blackops.org are quite possibly unknown to Domainz makes me suspect a systematic problem of some kind, and not a random one. Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog
Joe, Not to answer all of your email today, but.... Joe Abley wrote:
Has anybody else seen instances in the new register where a domain has ns_name_* records, but no corresponding ns_ip_* records?
For example, patho.gen.nz has:
ns_name_1: dns1.clear.net.nz ns_ip_1: 203.97.33.1 ns_name_2: soa2.qsi.net.nz ns_ip_2: ns_name_3: tardis.patho.gen.nz ns_ip_3: 203.97.2.226 ns_name_4: medusa.blackops.org ns_ip_4:
This makes me slightly nervous. Has anybody else seen this kind of thing for other domains?
The ns_ip_* fields were optional in the old system, and were only used where the nameserver was within the zone being specified (ie only used to produce glue records where necessary). Therefore, the only nameserver in the above list that NEEDS to have the IP number specified (the rest are ignored), is 'tardis.patho.gen.nz'.
Are the current zone files running at ns99.waikato.ac.nz built from this new data, or are the old zone files still running? If the former, when will the first authoritative zone from the new system be loaded? (it looks like it will be worth checking).
ns99 is still running on the zone files generated here at Waikato on Friday last week. I believe we are looking at doing a zone-build on the new system later today, and possibly making ns99 a slave to the new system once the relevant checks of those zonefiles have been made.
The fact that the hosts soa2.qsi.net.nz and medusa.blackops.org are quite possibly unknown to Domainz makes me suspect a systematic problem of some kind, and not a random one.
I don't think the above is a problem at all. 'qsi.net.nz' should have an IP number for 'soa2.qsi.net.nz' in its nameserver declaration (if it uses that nameserver for it's own zone), and medusa.blackops.org isn't part of the '.nz' registry, so you just hope that the appropriate glue records are being used if they are necessary for the 'blackops.org' domain.
$ host -t ns qsi.net.nz qsi.net.nz name server soa2.qsi.net.nz qsi.net.nz name server ns1.2day.com qsi.net.nz name server soa1.qsi.net.nz
$ host -t ns blackops.org blackops.org name server NS2.INTRA-CONNECT.NET blackops.org name server WARLOCK.blackops.org blackops.org name server medusa.blackops.org
So, both of those domains need the appropriate glue records generated so
that anyone looking for your nameservers can find them.
But that's not something that is required to be in your domain's
application in the '.nz' register.
Hmmm, I think I'm digging a 'techno-hole'. Perhaps I'll leave it at
that, and anyone that understands and feels they need to clarify can.....
Geoff.
----------------------------------
Geoff Thompson
On Tue, 9 May 2000, Geoff Thompson wrote:
This makes me slightly nervous. Has anybody else seen this kind of thing for other domains?
The ns_ip_* fields were optional in the old system, and were only used where the nameserver was within the zone being specified (ie only used to produce glue records where necessary).
Therefore, the only nameserver in the above list that NEEDS to have the IP number specified (the rest are ignored), is 'tardis.patho.gen.nz'.
Cool. I'm not nervous about that any more :) It looks like the only ns_ip_* records which were preserved in the shift to the new database were: + nameservers operated by known registrars + nameservers whose address records are required for purposes of glue Is that right? Thanks for your quick responses, by the way -- they are appreciated, Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog
Joe Abley wrote:
On Tue, 9 May 2000, Geoff Thompson wrote:
This makes me slightly nervous. Has anybody else seen this kind of thing for other domains?
The ns_ip_* fields were optional in the old system, and were only used where the nameserver was within the zone being specified (ie only used to produce glue records where necessary).
Therefore, the only nameserver in the above list that NEEDS to have the IP number specified (the rest are ignored), is 'tardis.patho.gen.nz'.
Cool. I'm not nervous about that any more :)
It looks like the only ns_ip_* records which were preserved in the shift to the new database were:
+ nameservers operated by known registrars
+ nameservers whose address records are required for purposes of glue
Is that right?
Sorry, but I don't want to speculate, and can only comment on the data that you shown us. Perhaps this is a question to clarify with the developers of the new system when they have a moment.
Thanks for your quick responses, by the way -- they are appreciated,
Phew. I was paranoid of sounding too pretentious, which I hope I'm
not. I'm just trying to explain things before comments and critizisms
spiral out of control.
I'd also like to say, that I'm not the authoritative 'Tech Support'
channel for these sorts of questions, and that Domainz should be
the first point of contact about such concerns. They may be a
little snowed-under at this point in time, so I guess response
times aren't initially going to be great, but analysing the system
from outside isn't always going to give the correct answer (ask
the Waikato Uni helpdesk about our user account management
system.....)
Geoff
----------------------------------
Geoff Thompson
Joe Abley
Has anybody else seen instances in the new register where a domain has ns_name_* records, but no corresponding ns_ip_* records?
For example, patho.gen.nz has:
ns_name_1: dns1.clear.net.nz ns_ip_1: 203.97.33.1 ns_name_2: soa2.qsi.net.nz ns_ip_2: ns_name_3: tardis.patho.gen.nz ns_ip_3: 203.97.2.226 ns_name_4: medusa.blackops.org ns_ip_4:
This makes me slightly nervous. Has anybody else seen this kind of thing for other domains?
Nothing to be worried about. Y'see, the Waikato system captured the ns_ip_* fields, but unless the corresponding nameserver is within the domain being referenced, it didn't actually do anything with them. It didn't push them to the zone file. It didn't even check them. You could put what you did in your holidays in there, and I think some people did. So, the import process just throws those fields away as being basically crap. If soa2.qsi.net.nz is mentioned in the list of name servers for qsi.co.nz, then the IP address associated with that will be used as glue. Otherwise, you get the IP address for soa2.qsi.net.nz it from the authoritative name servers for qsi.co.nz.
Are the current zone files running at ns99.waikato.ac.nz built from this new data, or are the old zone files still running? If the former, when will the first authoritative zone from the new system be loaded? (it looks like it will be worth checking).
They will be when the system is cut over. Initially, ns99.waikato,ac.nz will become a secondary off the new system (with other zones copying from ns99), then the other secondaries migrated to using the new servers. The other major change to the configuration is that the new servers are configured with fetch-glue off. There are some cases where that will mean an extra lookup (your resolvers will just do this) for name servers, but it's pretty rare for a nameserver not to be mentioned by IP address somewhere in the database. -- don --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog
participants (3)
-
Don Stokes -
Geoff Thompson -
Joe Abley