Hi,
What steps can a host legally take to handle registrar changes for their hosting clients?
For example, I have a client who has a domain registered through AAAQ.com. He wants to change the nameserver information to point to his hosting account on my servers. However, AAAQ's site is...somewhat less than helpful. Even when I dug through the Hostway documentation to try and find out how to change his nameserver information, the option to update the domain info didn't even exist through his control panel.
I can vaguely remember in 1997/1998, when a host could request a nameserver update for the client. I don't know why this stopped, but I'm guessing that part of it is tied in with the sudden explosion of registrars and resellers, plus added security concerns (ie, Verisign/NetSol's foo-bar-boo-boo with the $ex.com domain).
Aside from having directions on updating their own nameservers, what can a web host do to handle the nameserver information updates for their hosting clients (if we still can)?
What steps can a host legally take to handle registrar changes for their hosting clients?
For example, I have a client who has a domain registered through AAAQ.com. He wants to change the nameserver information to point to his hosting account on my servers. However, AAAQ's site is...somewhat less than helpful. Even when I dug through the Hostway documentation to try and find out how to change his nameserver information, the option to update the domain info didn't even exist through his control panel.
I can vaguely remember in 1997/1998, when a host could request a nameserver update for the client. I don't know why this stopped, but I'm guessing that part of it is tied in with the sudden explosion of registrars and resellers, plus added security concerns (ie, Verisign/NetSol's foo-bar-boo-boo with the $ex.com domain).
Aside from having directions on updating their own nameservers, what can a web host do to handle the nameserver information updates for their hosting clients (if we still can)?