# dns_records_conflict

Records already on these names would stop the domain from verifying.

## What it means

The customer used **Add it for me** on the connect page, and their DNS zone already has records on a name Apexly needs: a CNAME pointing somewhere else, other A or AAAA records on the apex, a record behind the Cloudflare proxy, or a record that cannot sit next to a CNAME.

Apexly never deletes or overwrites a record without asking. `status_detail.conflicts` lists each record (`type`, `name`, `content`, `proxied`, `reason`, `replaceable`) and `status_detail.can_replace` says whether replacing them is enough.

## Why it happens

- The domain used to point at another service, such as an old careers site.
- The apex still has the previous host's A records, or an AAAA record from before.
- The record exists but its proxy (orange cloud) is on.
- An MX, TXT or other record sits on a subdomain that needs a CNAME.

## What to do

1. On the connect page, read the list and choose **Replace these records**. Only the listed records, on the names Apexly needs, are changed; nothing else in the zone is touched.
2. If a record is marked as one we leave alone (for example an MX record on the subdomain), remove or move it at the DNS provider yourself, then try again.
3. Or add the records by hand with **I'd rather add it myself**.

- [Connect page](/docs/connect-page)
- [Embed the connect flow](/docs/guides/embed-connect)

## In the API

```
HTTP 409

{
  "error": {
    "code": "dns_records_conflict",
    "message": "Records already on these names would stop the domain from verifying.",
    "fix": "Review the records in status_detail.conflicts and confirm replacing them, or change them at the DNS provider.",
    "docs": "https://docs.apexly.dev/errors/dns_records_conflict"
  }
}
```