### DNS Changes Necessary for the Web Account Migration

To finalize the migration process, the customer's domain should be migrated to the HSPcomplete DNS. Depending on the availability of the remote name servers, two schemes of the DNS changes can be implemented.

If You Do Not Own the Name Servers Used by the Remote Non-HSPcomplete Server

After both the customer billing and web data is imported into the HSPcomplete and the migrated website is checked, the zone at the Internet Registrar that had registered the customer's domain should be updated manually: the remote name servers should be replaced with the HSPcomplete name servers so that the outside requests for the customer's website will be forwarded to the HSPcomplete Hardware Node.

If you Own the Name Servers Used by the Remote Non-HSPcomplete Server

In this case, you do not need to update the zones at the Internet Registrar.

The HSPcomplete name servers should be renamed into the same names as the remote name servers. And the remote name servers should be just renamed. At the same time the HSPcomplete name servers should be configured to forward all the unknown domain requests to the remote name servers; and the recognized requests (for already migrated domains) should be directed to the HSPcomplete Hardware Node where the customer website was migrated.

Please send us your feedback on this help page