Point your GoDaddy domainto our hosted servers.

Understand what this change does

A domain is the address customers enter, while DNS tells the internet which services handle its website, email and other subdomains. Changing the domain’s nameservers transfers authority for the complete DNS zone from GoDaddy to the new DNS provider. It does not transfer domain registration ownership.

Good to know: Do not edit an NS record inside the DNS records table when the goal is to change the domain’s authoritative nameservers. GoDaddy provides a separate Nameservers setting for that action.

Confirm whether nameservers are the right method

Use custom nameservers only when Sahasna has confirmed that the entire DNS zone will be managed on its hosting platform. If GoDaddy should continue managing DNS, the safer approach may be to change only the website’s A and CNAME records using values supplied for the hosting account.

• Nameserver change: moves management of website, email and every other DNS record to another provider.
• A and CNAME change: keeps DNS at GoDaddy and points only the required website hostnames.
• Domain transfer: moves registration to another registrar and is a separate process not required for hosting.

Protect email and other services first

Before changing nameservers, record every active DNS entry currently used by the domain. This can include MX records for email, TXT records for SPF, DKIM and verification, CNAME records for services and subdomains, and any existing A or AAAA records. These records must exist in the new DNS zone before or immediately when authority changes.

Good to know: Incorrect or missing MX and related TXT records can interrupt mail delivery or cause outgoing messages to fail authentication. Confirm the email provider and required records with Sahasna before proceeding.

Collect the exact hosting values

Use only the nameserver pair or DNS records supplied in the Sahasna hosting handover message for this specific domain. Copy the values exactly and keep that message available during the change. Nameserver addresses normally look like hostnames rather than numeric IP addresses.

• Confirm both required nameserver values before opening GoDaddy.
• Confirm that the new DNS zone already contains the website and email records.
• Take screenshots or export the current GoDaddy DNS records for rollback reference.
• Plan the change when somebody can test the website, forms and email afterwards.

Open the GoDaddy nameserver settings

Sign in to the GoDaddy Domain Portfolio and select the individual domain. Open DNS, then select Nameservers. The precise wording may vary as GoDaddy updates its interface, but nameservers should be managed from the domain’s DNS settings rather than by adding ordinary NS records to the zone.

Enter the custom nameservers

Choose “I’ll use my own nameservers” or the equivalent custom-nameserver option. Replace the current values with the two exact nameservers supplied by Sahasna, then select Save and Continue. If Domain Protection is enabled, GoDaddy may require identity verification before accepting the update.

Good to know: Do not guess the values and do not enter example placeholders. If the handover message is missing, stop and request the correct nameservers before saving.

Allow time for DNS propagation

DNS changes are cached across many networks and will not appear everywhere at the same moment. GoDaddy says most updates take effect within an hour but nameserver and other DNS changes can take up to 48 hours to update globally. During that period, different users may temporarily reach different DNS providers.

• Do not repeatedly change the nameservers while propagation is still in progress.
• Test on more than one network, such as office broadband and mobile data.
• Keep the previous hosting available during the transition when possible.

Verify the complete service, not only the homepage

After the new nameservers begin appearing, Sahasna should confirm the authoritative nameservers and website DNS records. Then test the real customer journey and every service connected to the domain.

• Open both the root domain and the www version over HTTPS.
• Check certificate validity and confirm there are no redirect loops.
• Submit important forms and verify that notifications arrive.
• Send and receive email using each business mail service.
• Check subdomains, verification records and third-party integrations.

Know how to recover from a problem

If a required service fails, first compare the new DNS zone with the saved records and correct missing or incorrect entries. If the entire new DNS service is unavailable and a rollback is necessary, restore the previous nameservers recorded before the change. A rollback also needs propagation time, so it is not instant.

Good to know: Avoid deleting the old hosting or DNS configuration until the new website, email and integrations have been stable and verified.

Official GoDaddy references

GoDaddy may update the labels and position of controls. Use its current documentation alongside the values and instructions supplied for the Sahasna hosting account.