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