Connect Your Domain (A Records) Recommended
Point your client's existing domain to Reputifly Cloud by adding 2 simple DNS records. Your email, nameservers, and all other DNS settings stay completely untouched.
Email safe. This method only changes where your website is hosted. Your email (MX records), nameservers, and all other DNS settings remain exactly as they are.
What You Need
- Access to your domain registrar's DNS panel (Exabytes, GoDaddy, Namecheap, etc.)
- The domain name you want to connect (e.g.
yourdomain.com)
Step-By-Step Guide
Log Into Your Domain Registrar
Go to your domain provider (Exabytes, GoDaddy, Namecheap, Cloudflare Registrar, etc.) and find the DNS management panel for your domain. This is usually under "DNS Settings", "DNS Records", or "Zone Editor".
Find "DNS Records" (Not "Nameservers")
Look for the section where you can add individual DNS records. Do not change your nameservers — that's a different setting. You only need to add A records.
Add These 2 A Records
Create two new A records pointing to the Reputifly Cloud server:
| Type | Host | Points to | |
|---|---|---|---|
| A | @ | 46.224.233.157 | |
| A | www | 46.224.233.157 |
If your registrar already has A records for @ or www pointing to a different IP, remove those old records first, then add the new ones above.
Wait For DNS Propagation
DNS changes typically take 5–30 minutes to propagate worldwide. In rare cases it can take up to 24 hours. You don't need to do anything during this time.
Notify Your Reputifly Admin
Once you've added both records, let your Reputifly admin know. They'll activate your site from the Reputifly Cloud dashboard, which sets up your SSL certificate and completes the connection.
Troubleshooting
"This record will conflict with the CNAME record for the zone"
Your registrar already has a CNAME record for the same hostname (usually
www). A domain can't have both a CNAME and an A record for the same name. Delete the existing CNAME record first, then add the A record. The old CNAME was likely pointing to your previous host."I added the records but my site still shows the old website"
DNS propagation takes 5–30 minutes (up to 24 hours in rare cases). Wait and try again. Try opening your domain in a private/incognito window to avoid browser cache. You can check propagation status at dnschecker.org.
"My website works but my email stopped working"
This should not happen with A records — they only affect the website. If your email broke, you may have accidentally changed your nameservers instead of adding A records. Go back to your registrar and verify your nameservers are still set to your email provider's nameservers (not Cloudflare or any other value). Your A records and nameservers are separate settings.
"My registrar uses different field names"
Different registrars label fields differently. Common alternatives: "Host" may be called "Name" or "Hostname". "@" may need to be entered as your full domain (e.g.
yourdomain.com) or left blank. "Points to" may be called "Value", "Address", or "IP Address". If unsure, contact your registrar's support team."I already have an A record for @ — do I replace it or add another?"
Replace it. Delete the old A record pointing to your previous host's IP address, then add the new one pointing to
46.224.233.157. Having two A records for the same hostname causes unpredictable behavior."I added the new A records but didn't delete the old ones"
This is a common mistake. If you have both your old IP and
46.224.233.157 as A records for the same hostname, your website will randomly flip between the old server and the new one — sometimes loading the old site, sometimes the new one. Delete all A records with the old IP address (for both @ and www), keeping only the ones pointing to 46.224.233.157."Warning: None of IP addresses specified in A DNS records match the IP address used for hosting"
This warning from your registrar (e.g. Plesk/Exabytes) is expected and safe to ignore. It's telling you that your A records no longer point to their own hosting server — which is exactly what you intended. Your website is now hosted on Reputifly Cloud, not at your registrar.
"Warning: WWW prefix was changed. Be sure to modify the SSL/TLS certificate accordingly"
This warning from your registrar is also safe to ignore. Your Reputifly admin will issue a new SSL certificate for your domain when they activate it. You don't need to do anything about SSL on the registrar side.
Frequently Asked Questions
Will this affect my email?
No. A records only control where your website is hosted. Your email is controlled by MX records, which are completely separate and will not be changed.
How long does DNS propagation take?
Usually 5–30 minutes. Maximum 24 hours. Most registrars update within 15 minutes.
What if I made a mistake?
Simply delete the incorrect A record and add the correct one. DNS records are safe to add and remove — there's no permanent damage from an incorrect entry.
Do I need to remove my old A records?
Yes. If you have existing A records for @ or www pointing to a different IP address (your old host), remove those first. Then add the new records pointing to
46.224.233.157.What's the difference between A records and nameservers?
Nameservers control who manages all your DNS. A records control where one specific thing (the website) points to. Changing A records is much safer because it only affects the website, not your email or anything else.