Understand nameservers versus A records and make your domain resolve to the correct server.
Start with the checks below. Each step explains what to look for and what to try next.
Choose one DNS management method
Use nameservers if you want the hosting provider to manage the domain’s DNS zone. Use DNS records if you want to keep DNS hosted at your registrar or another DNS provider. Do not mix the methods without checking which DNS zone is authoritative.
Choose your connection path
Choose your connection path
Use the nameservers provided with your hosting account at the registrar.
Update only the needed A/AAAA or CNAME records there.
Preserve MX, SPF, DKIM and DMARC records before changing DNS authority.
Test the hosting destination before switching public DNS.
Before you continue: Never copy placeholder nameservers or example IP addresses into real DNS records.
Nameserver method
- Locate the exact nameservers in your hosting activation details.
- Sign in to your domain registrar and open domain DNS or nameserver settings.
- Replace the previous nameservers with the provided values and save.
- Manage subsequent A, MX and TXT records at the new authoritative DNS provider.
A-record method
- Find the correct server IP address in your hosting details.
- At the authoritative DNS provider, set the root domain A record to that IP address.
- Set
wwwusing a suitable CNAME or record according to your setup. - Preserve MX, SPF, DKIM and other email-related records when changing DNS.
Why a change may take time
DNS caching depends on record TTL values and resolver behavior. Test from more than one network. Do not assume a change has failed simply because one device still shows the old website.
How to confirm the issue is resolved
- Repeat the original action that produced the issue.
- Check the result in a second browser or network when relevant.
- Review logs or status messages for remaining errors.
- Keep a short record of what changed so it can be reversed if necessary.
If the issue persists, contact support with the exact error, time, affected domain and actions already tried—never include passwords or secret keys.
How to confirm your DNS change worked
Open the domain in a private browser window and check the result from another network if possible. A successful DNS change means the domain resolves to the intended hosting service; it does not automatically prove HTTPS, email or the website application is configured correctly.
- Wrong website appears: Confirm the domain is added to the correct hosting account and its document root contains the expected site.
- Some people see the old website: Different resolvers may still have cached answers; avoid repeatedly changing records during propagation.
- Email stopped working: If you changed nameservers, restore or verify the MX, SPF, DKIM and DMARC records with your mail provider.
See how DNS propagation works and the email delivery checklist before making another change.
Guidance may vary by plan, control panel version and enabled features. Review the settings available to your account before changing live services.