Troubleshoot One-click Services

Last updated October 29, 2026

Table of Contents

• “… cannot both exist on the same name”
• “This would bring this zone to … records”
• The service is still listed after you deleted its records
• Removing a service deleted records you had changed
• The redirect works over HTTP but not HTTPS
• The service records do not match the provider’s instructions
• The service is no longer in the list
• Have more questions?

Most one-click service problems come from records already in the zone, the zone’s record limit, or a provider that changed its setup. Find the message or symptom you see below.

“… cannot both exist on the same name”

When you add a service, you might see a message like this:

A record (id=1234567) already exists on www.example.com. CNAME and A records cannot both exist on the same name.

or, for a service that adds an ALIAS record to the domain apex:

A record (id=1234567) already exists on example.com. ALIAS and A records cannot both exist on the same name.

The service wants to create a record on a name that already has a record it cannot share with. A CNAME record cannot share its name with any other record, and an ALIAS record cannot share its name with an A, AAAA, CNAME, ALIAS, or URL record. DNSimple adds none of the service’s records when this happens, so nothing needs cleaning up.

The message can list more than one record. It can also show a second conflict on another name after you fix the first, for example the apex and then www. Repeat the steps until the service adds.

“This would bring this zone to … records”

A service’s records count toward the zone’s record limit. On plans that allow records above the limit, DNSimple adds the service and the extra records count toward the overage. If the zone cannot go above its limit and adding the records would take it over, DNSimple adds none of them and shows a message like this:

This would bring this zone to 102 records, above the Solo limit of 100. No records were added. Upgrade to add more records.

If your account chose to block new records above the limit, the message says Your account does not allow records above the limit. When a zone that cannot go above its limit is already at it, the Add buttons on the One-click services page are turned off.

To add the service, delete records the zone no longer needs, or upgrade to a plan with a higher limit. If your account blocks new records above the limit, you can allow them again. If the message says to contact support instead of upgrading, contact support.

The service is still listed after you deleted its records

Deleting a service’s records in the record editor does not remove the service. It stays under Applied one-click services, and its card shows Service installed instead of Add, so you cannot add it again over the top.

To clear it, remove the service. To get its records back, remove the service and then add it again.

Removing a service deleted records you had changed

Removing a service deletes every record linked to that service, including records you edited after adding it, such as a changed priority, TTL, or content. A record you added that the service did not use stays, even on the same name. If the zone already had the same record the service created, or an SPF record that the service combined with its own, removing the service deletes that record too.

Before you remove a service whose records you have changed, note their values. Afterward, add the records you still need by hand in the record editor.

The redirect works over HTTP but not HTTPS

With the URL Forwarding service, http://example.com redirects but https://example.com shows a certificate error. The redirect only works over HTTPS when the domain has an SSL certificate that covers the address the visitor typed. See HTTPS redirects.

The service records do not match the provider’s instructions

Providers change their setup over time, and a service’s records can fall behind. Check the article for that service in the Services category. Where a service no longer matches its provider, the article says so and lists the records to add by hand instead.

Records already on your domain do not change when DNSimple updates a service. To get the current records, remove the service and add it again.

The service is no longer in the list

DNSimple can retire a service, for example when the provider shuts down. A retired service disappears from the One-click services page, so it cannot be added again. If it was already on your domain, its records stay in place, and it stays under Applied one-click services, where you can still remove it.

For how services are added, updated, and retired, see What Are One-click Services?.

Have more questions?

If you have additional questions or need any assistance with one-click services, contact support, and we’ll be happy to help. You can also read more about DNSimple integrations.