RE: [FreeDNS] Network Solutions not recognizing .za.net

["Geoff Robertson" <geoff@xxxxxxxxxxxxx>]

Hi List,

Basically, the way network solutions works is that before you can
register a domain with them, you need to register your authorative
nameservers with them (not as domain names, but in their database of
registered name servers). This is a dubious thing to require, but it's
probably similar in intent to the zone checks that coza runs when
registering names with them.

So, basically the problem is that to register the two nameservers we
need to use (coruscant.mylesahead.za.net, hoth.mylesahead.za.net) as
nameservers with network solutions, the nameservers for ZA.NET need to
be registered with network solutions first (logically it's obvious,
since those are the nameservers that will delegate the ZA.NET
namespace). With that done, we should be able to register coruscant and
hoth as nameservers, then (and here's what people missed on Geoff's
previous mail) move the SOA and other NS records to our new
infrastructure.

Now, the questions:
	Does anyone have a .com domain with a SOA in the ZA.NET
namespace? If so, is it registered with Network Solutions and how did
you do it/describe the hoops you had to jump through.
	Who do we contact at za.net to have the za.net nameservers
registered with netsol? We'd desperately like to trash our old
infrastrucure and complete the move the new.

Thanks,

Michael
_____________________________________________________
FreeDNS                    ZA NiC - free domain names
freedns@xxxxxx    Archive: http://www.za.net/freedns/