# Nameservers vs A/CNAME records — which one should I use?

Dropify's dashboard sets up domains through **nameservers** (`dns1.dropify.shop` and `dns2.dropify.shop`) — this is the option shown directly in **Store Settings → Domains**. If you want to keep your domain's DNS managed elsewhere (for example, to keep using your existing email), the **CNAME** method is an official, supported alternative: add a CNAME record pointing to `cname.dropify.shop` at your domain registrar. This is set up on the registrar side rather than in the Dropify dashboard — see the video tutorial on the Dropify YouTube channel (https://www.youtube.com/watch?v=ohMQiCt3lT4) for the exact steps.

## Steps

1. For most stores: change the nameservers as described in [How to connect a custom domain to your Dropify store](https://help.dropify.shop/en/domains_dns/connect-custom-domain/). This is the setup shown directly in the dashboard and the simplest option.
2. If you need to keep your domain's DNS managed elsewhere (business email, Cloudflare protection, etc.), do **not** switch nameservers. Instead, add a CNAME record at your registrar pointing to `cname.dropify.shop` — see the video tutorial on the Dropify YouTube channel for the exact steps, or contact support if you get stuck.
3. When using Cloudflare specifically, whether Cloudflare's proxy (orange cloud) should be on or off depends on your setup, and an incorrect proxy state can block SSL generation — contact support if you're unsure which to use.
4. Only use one method at a time — a leftover **A record** (e.g. from before you switched to nameservers) can override the nameservers and stop the domain from connecting even though the nameservers are set correctly.

## Common problems

- Domain won't connect even though nameservers check out everywhere (who.is, DNSChecker, nslookup) → an old A record is taking priority; remove it. If your registrar blocks DNS edits once nameservers point to Dropify, temporarily revert to default nameservers, remove the A record, then switch back and use Dropify's refresh/sync option.
- Can't remove an old `@` record at your provider → try replacing it with a `www` record instead, or contact your provider's support — this is on their side, not Dropify's.
- Root (non-www) domain stops working when set primary, but `www` works fine → usually a provider-side DNS setting; contact your domain provider. Only the two Dropify nameservers are needed — no separate A, AAAA, or CNAME records.
- Domain flagged as inaccessible but everything checks out → ask support to re-verify; propagation delays can cause false alarms that resolve on their own.

## Related
- [How to connect a custom domain to your Dropify store](https://help.dropify.shop/en/domains_dns/connect-custom-domain/)
- [My domain is connected but the store still won't load](https://help.dropify.shop/en/domains_dns/domain-not-connecting-troubleshooting/)
- [How to set up a professional/business email on your connected domain](https://help.dropify.shop/en/domains_dns/mx-records-for-custom-email/)