What the service includes
DNS directs website traffic and identifies the servers handling email. A domain can connect several services from different providers, so changes need to consider the entire zone. We help configure records and identify where DNS is actually managed.
Website and subdomain records
A and AAAA records identify IPv4 and IPv6 addresses. CNAME points a name to another domain name. We review hosting and application requirements before changing entries. Operators may offer different ways to configure the root domain. Existing subdomains and service verification records should be included in the plan.
Email and domain verification
MX directs email, while TXT can hold SPF, service verification and other settings. DKIM and DMARC need the correct names and values. Copying unrelated records can create conflicts. Before making changes, we identify all senders using the domain, including forms, CRM and newsletter systems, to preserve their legitimate sending configuration.
Propagation and change checks
DNS uses caching, so a new configuration does not appear everywhere at once. TTL affects how long answers are stored but does not guarantee an instant change. Before moving services, we record the existing setup. Afterwards we check DNS responses and the actual operation of the website and email.
One configuration connecting several providers
When services use different operators, DNS connects them. The site may run on hosting, email with another provider and subdomains in external systems. We help describe these dependencies and preserve needed records. A clear service list reduces the chance that changing one entry disrupts something that was overlooked during planning.
Prepare DNS changes
Provide the domain, operator and services that must work afterwards. Include current records and new values supplied by providers. For email, account for every sender. Do not remove the old zone before reviewing it. We agree on change order, checks and confirmation of website, email and integration operation.