Setup & nameserver issues
Nameserver delegation, propagation, and other DNS-related issues.
Setup not taking effect
After delegating your nameservers to fast.site, the change can take time to propagate. Usually a few minutes, sometimes longer.
What to check:
- Verify the change was made at your domain registrar (not at an old DNS provider)
- Confirm the change was saved or applied at your registrar/provider
- Some registrars have a separate DNS panel. Double-check you edited the right one
- Allow up to 24-48 hours for full global propagation
# Check current resolution
dig yourdomain.com +shortTip: Run dig NS yourdomain.com to confirm your domain currently lists the fast.site nameservers.
Leftover records from your previous host
If you migrated from another CDN or host, old records can still resolve and route traffic to the wrong place until you switch nameservers cleanly.
Solution:
- Confirm the domain shows the fast.site nameservers globally (check with whatsmydns.net)
- If old records still resolve, your old DNS provider may still be authoritative. Revoke their delegation at the registrar
- Allow up to 24-48 hours for full global cutover
- Email keeps working as long as MX records were re-created in the fast.site DNS panel before nameserver delegation
Cloudflare in front of fast.site
If Cloudflare was previously authoritative for your domain, your nameservers might still point to Cloudflare instead of fast.site.
Problem: Cloudflare is still your authoritative DNS, so traffic never reaches fast.site.
Solution: Change the nameservers at your domain registrar from Cloudflare to the fast.site nameservers (ns1.fast.site / ns2.fast.site).
Still having issues?
Send us your domain and we'll diagnose the delegation from our side.
Contact Support