Transferred your domain to ArkHost but it's not working? Here's how to fix it.
Quick Setup
Required DNS records:
- A record - Points your domain to server IP address
- CNAME record - Points www to your domain (www.yourdomain.com → yourdomain.com)
- MX record - Routes email to mail server
- SPF record - Prevents email spoofing (TXT record)
Add domain in DirectAdmin: Account Manager → Domain Setup → Add Domain
Enable SSL: Account Manager → SSL Certificates → Get automatic certificate from ACME Provider
DNS propagation takes 2-48 hours. SSL activates 5-10 minutes after DNS resolves.
Domain Still Shows Old Host After 48 Hours
Check if DNS actually updated:
dig yourdomain.com +short
Should return your new server IP. If it shows old IP:
- Records updated at registrar, not hosting DNS zone
- Using wrong nameservers (check
whois yourdomain.com) - High TTL at old host (can take up to TTL value to expire)
Check global propagation: whatsmydns.net
If DNS resolves correctly but site still shows old content: browser cache. Clear it or test in incognito mode.
SSL Certificate Won't Activate
SSL requires A record pointing to correct server first. Let's Encrypt verifies domain ownership by connecting to your server.
Verify A record resolves:
nslookup yourdomain.com
Common failures:
- A record points to wrong IP
- DNS not propagated yet (wait 2-4 hours minimum)
- Port 80 blocked (ACME verification needs HTTP)
- Domain has CAA record blocking Let's Encrypt
DirectAdmin shows specific error in SSL Certificates section. Read it.
www Works But Root Domain Doesn't (Or Vice Versa)
Two different problems:
Root works, www doesn't:
- Missing CNAME record for www
- CNAME points to wrong target
Fix: Add CNAME record: www → yourdomain.com
www works, root doesn't:
- Missing or wrong A record
- A record has wrong IP address
Fix: Add A record: @ (or blank) → server IP address
Both should be configured. Some users type www, others don't.
Email Stopped Working After DNS Change
MX records tell email where to deliver mail. After DNS changes, verify MX records point correctly.
dig yourdomain.com MX +short
Should show your mail server. If missing or wrong:
- Email delivers to old host (gets lost)
- Email bounces entirely
Standard MX record: mail.yourdomain.com with priority 10
Also check A record exists for mail.yourdomain.com pointing to server IP.
SPF record (TXT) required to prevent spam filtering:
v=spf1 a mx ~all
DNS_PROBE_FINISHED_NXDOMAIN Error
Means DNS servers can't find your domain. Browser can't resolve it to IP address.
Causes:
- Domain doesn't exist (typo, not registered)
- Nameservers not configured at registrar
- DNS zone deleted on hosting server
- Registrar suspended domain (expired, transfer locked)
Check nameservers:
whois yourdomain.com | grep "Name Server"
Should show valid nameservers. If blank or showing registrar defaults, DNS won't resolve.
Verification Commands
Check A record:
dig yourdomain.com +short
Check MX records:
dig yourdomain.com MX +short
Check nameservers:
dig yourdomain.com NS +short
Full DNS info:
dig yourdomain.com ANY
Windows users: replace dig with nslookup
TTL Matters
TTL (Time To Live) = how long DNS records are cached.
Old host had TTL 86400 (24 hours)? DNS servers cache old IP for 24 hours after you change it.
Lower TTL before migration (set to 300 = 5 minutes). Change DNS records. Wait for propagation. Increase TTL after migration completes.
Can't speed up propagation retroactively. TTL was set at old host before you changed records.
Still Broken?
Open ticket with:
- Domain name
- Output of
dig yourdomain.com - What you changed and when
- Specific error message
Generic "not working" doesn't help. DNS errors are specific. Show us what's failing.
