1. Read the current Cloudflare record, its content, proxy state and TTL. Identify whether Domain Nexus is managing the provider directly or applying a portable replica record set.
2. Compare the desired record with the existing owner name and type. Do not assume a content replacement creates a completely unrelated record.
3. Review the proposed changeset and the target's result. This build retains Cloudflare metadata for an unambiguous single-record content replacement where that metadata is not explicitly replaced.
4. Check any DNS_REPLICA_PROXY_TTL error before retrying. For portable replication, the adapter uses a 300-second portable TTL representation for a proxied record whose Cloudflare TTL is automatic.
5. Choose the intended remedy: keep compatible portable TTL data or deliberately change that record to DNS-only in the appropriate provider workflow. Re-read the target before another synchronisation.

A proxied record can return Cloudflare's addresses publicly while the stored DNS record identifies the origin. Verify proxy behaviour and application reachability as separate checks. Replacing the origin repeatedly will not make a proxied public answer look like a DNS-only one.

No. Other targets receive their supported portable records. Cloudflare proxy settings, comments, tags and provider-specific routing do not acquire an equivalent meaning on another DNS service merely because the domain name is the same.

The adapter also groups changes for the same owner when performing transitions involving CNAME records. If it refuses an unsupported target record or an oversized owner batch, resolve that exact condition through a smaller reviewed plan. Do not delete unfamiliar records at the provider just to make a reconciliation pass. Preserve a snapshot and ensure website and mail requirements remain represented after the change.

• Connect Cloudflare with a scoped token and the correct account
• Synchronize a DNS package across multiple servers and select its master
• Resolve DNS drift and changes with an unknown provider outcome
• Understand protected records and resolve DNS record conflicts

• Cloudflare: Record TTL behaviour