On Thu, 10 May 2001, Andy Gardner wrote:
The OpenSRS system won't allow you to use a name server that isn't in verisign's NS database without registering the NS first. It's a safety feature. Unfortunately, doing so for NS's in ccTLD is a manual process.
What I don't see is why you can't follow the recommended method and create a.ns.cipher-interernational.com and b.ns.cipher-international.com using the IP addresses of your existing nameservers? Most registrars I've dealt with are happy to create the 'glue' records you need to do this automatically.
Once you talk to OpenSRS and get your ccTLD Name Server glue inserted, you shouldn't have any further problem with your current registrar (Tucows) even though their RESELLER appears to be a little dense.
You can't put .nz glue records into the .com database. And even if you did, they'd be rejected by most DNS resolvers. Of course, you can put delegations to nameservers outside .com, they just end up being glueless. Which is usually fine, although can lead to problems down the track if something on the authoratitive .nz servers changes, so I guess that's why OpenSRS discourages it. (before you ask, yes the delegations for waikato.edu and waikato.com have this problem... do a 'dig SOA waikato.edu @192.5.5.241' and note that the nameserver IP addresses aren't returned, you have to stop and query the .nz servers about waikato.ac.nz first before continuing to lookup waikato.edu addresses... I'm hoping to recitify this in the near future however) --Colin. ** Colin Palmer, Systems and Development Group, University of Waikato, NZ ** --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog