One-click Services Glossary

Last updated

Table of Contents


A reference for the terms used in DNSimple’s one-click services articles. For DNS terms such as zones and record types, see the DNS Glossary. For connectors and Integrated DNS Providers, see the Integrations Glossary.

Services

One-click service

A ready-made set of DNS records for a specific provider, such as Shopify or Google Workspace, that you add to a domain in one step. One-click services are included on every plan.

Learn more:

Service template

The definition of a service: its name, tab, setup form fields, and the records it creates. Templates live in the open-source dnsimple-services repository on GitHub, and DNSimple loads them into the app.

Learn more:

Tab

One of the six groups on the One-click services page: , , , , , and . Each service is on exactly one tab.

Learn more:

Setup form

The page that asks for the details a service needs from your provider account, such as a site name or a verification value, before it adds the records. It ends with a button. A service with no form fields skips this page and adds its records as soon as you click .

Learn more:

Default subdomain

A subdomain set in a service’s template that its records go on, such as www for SupaDupa or blog for WordPress. You cannot choose a different subdomain when you add a service. The list on the service shows the full record names.

Learn more:

Retired service

A service DNSimple no longer offers, for example because the provider shut down. A retired service is not on the One-click services page, so it cannot be added. On domains that already have it, its records stay in place and it can still be removed. The dnsimple-services repository calls this deprecated.

Learn more:

Adding and removing

Applied service

A service that has been added to a domain. Applied services are listed in the card, where you remove them, and their card on the tab shows instead of .

Learn more:

Service records

The records linked to a service on a domain. They are ordinary records in the zone, and DNSimple remembers which service they belong to. Removing the service deletes them, even if you edited them after adding the service. 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.

Learn more:

Record conflict

A record already in the zone that a service’s record cannot share a name with, such as an A record on a name where the service adds a CNAME or ALIAS record. If there is a conflict, DNSimple adds none of the service’s records and shows an error ending in “cannot both exist on the same name”.

Learn more:

Record limit

The number of records a zone includes on your plan. A service’s records count toward it. 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 the service’s records would take it over, DNSimple adds none of them. When a zone that cannot go above its limit is already at it, the buttons are turned off.

Learn more:

Have more questions?

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