nox
02-27-2002, 06:33 AM
While it's always been known, here is a helpful email from Verisign dealing with the problem that arises with using name servers from some other registrars with Network Solutions domains.. I get this question weekly from resellers so I thought it might help here..
-----------------------------
Dear customer,
It is quite confusing. It's not actually that we have two different systems.
VeriSign the Registry and VeriSign the Registrar ARE literally two different
companies. Due to the obvious conflict in interest, ICANN has regulated this
and the Registry is in no way affiliated (other than in name) with the
Registrar VeriSign. So, often server information may have changed with the
managing registrar of the parent domain name, and of course that information
is relayed to the Registry (otherwise it would be useless), but it is not
necessarily relayed to VeriSign the Registrar, because we have no real
affiliation with it. If you run into an issue like this, and you need that
information to be correctly reflected in our system here's what you can do:
1. go to the managing registrar of the parent domain name and modify or
create the server there.
2. once that creation/mod is visible in the Registry Whois, e-mail or call
VeriSign and request that we "mirror" the newly created or modified server
(if someone you talk to in cust service gets confused, just tell them to
assign the Seibel to the Registry and state that you want the server info
mirrored in our system to what is in the Registry)
3. Once that information is mirrord you may put a VeriSign (Registrar)
domain name on the server. If the domain name is already on the server, it
will then now resolve to the correct location.
Hope this helped some.
Best regards,
Cecelia B
Customer Service Operations
VeriSign, Inc.
http://www.netsol.com
------------------------------------
Thanks Cecelia, you are a rare person in that organisation.. :)
Cheers.
-----------------------------
Dear customer,
It is quite confusing. It's not actually that we have two different systems.
VeriSign the Registry and VeriSign the Registrar ARE literally two different
companies. Due to the obvious conflict in interest, ICANN has regulated this
and the Registry is in no way affiliated (other than in name) with the
Registrar VeriSign. So, often server information may have changed with the
managing registrar of the parent domain name, and of course that information
is relayed to the Registry (otherwise it would be useless), but it is not
necessarily relayed to VeriSign the Registrar, because we have no real
affiliation with it. If you run into an issue like this, and you need that
information to be correctly reflected in our system here's what you can do:
1. go to the managing registrar of the parent domain name and modify or
create the server there.
2. once that creation/mod is visible in the Registry Whois, e-mail or call
VeriSign and request that we "mirror" the newly created or modified server
(if someone you talk to in cust service gets confused, just tell them to
assign the Seibel to the Registry and state that you want the server info
mirrored in our system to what is in the Registry)
3. Once that information is mirrord you may put a VeriSign (Registrar)
domain name on the server. If the domain name is already on the server, it
will then now resolve to the correct location.
Hope this helped some.
Best regards,
Cecelia B
Customer Service Operations
VeriSign, Inc.
http://www.netsol.com
------------------------------------
Thanks Cecelia, you are a rare person in that organisation.. :)
Cheers.
