Point your domain or Cloudflare DNS to Pakish hosting for the website while keeping MX and mail authentication records intact so email keeps working.
Nameservers vs individual DNS records
- Nameserver method: delegate DNS to Pakish — manage web and mail records in cPanel Zone Editor.
- Record method: keep DNS at Cloudflare or your registrar — add A/CNAME for web and preserve MX/TXT for mail.
Pakish nameservers (when delegating DNS)
domainpakistan.mars.orderbox-dns.comdomainpakistan.earth.orderbox-dns.comdomainpakistan.venus.orderbox-dns.comdomainpakistan.mercury.orderbox-dns.com
Use the exact nameservers in your welcome email if they differ for your account.
Web records at Cloudflare
- Add an A record for
@pointing to your Pakish server IP from your hosting welcome email or cPanel Server Information. - Add a CNAME for
wwwto your domain or use A records per your preference. - Use DNS only (grey cloud) temporarily while testing if proxy causes certificate or redirect issues.
Preserve MX, SPF, DKIM, and DMARC
- Before changing DNS, export or screenshot existing MX and TXT records.
- If mail stays on Pakish, keep MX pointing to your hosting mail hostname.
- If mail uses Google or Microsoft, keep their MX records and add SPF/DKIM/DMARC for that provider.
- Configure authentication — SPF, DKIM, and DMARC.
SSL implications
Enable origin SSL on the server before forcing HTTPS through Cloudflare — AutoSSL and HTTPS.
DNS propagation and verification
- Allow time for DNS propagation (often minutes to 24 hours).
- Test web: browse
https://yourdomain.com. - Test mail: send and receive from a domain mailbox.
Avoid accidental email outage
Do not delete MX records when adding web records. When moving only the website to Pakish, leave mail DNS unchanged at the current provider.
For .pk domains or PKNIC glue records, also read DNS record management and private nameservers if applicable.
If email stops after DNS changes, open an urgent ticket with your domain, registrar or Cloudflare DNS provider, and what records you changed.
