dhosty

Domains, DNS & HTTPS · 6 min read

Change A entry: Set domain to the right destination

The question "a-entry change" does not only concern one entry in the customer account. The responsibility for the domain name, the correct DNS zone and a prepared technical goal is crucial. This guide separates the individual tasks and shows what you should check before changing.](/domains/) You can find the entry point at dhosty. Technical information does not replace the mandatory verification of an order or a careful control of the existing website and mail settings.

Set the correct host name and IPv4 target

An A entry links a host name to an IPv4 address. Before you change it, it must be clear which address to move: the main domain, www or another subdomain. The main domain and www may have separate entries. Therefore, a change in a name does not automatically act like a change in all addresses of the project.

Use the specific target address of the intended hosting. Do not use an example IP from a manual and not the administrative address of another system. In case of doubt, check the information belonging to your project in the customer area or ask in advance. Do not use the old value. This gives you a comprehensible relapse possibility and can clearly assign later queries.

Store the change in the relevant DNS zone

Open the DNS administration at the provider that manages the authoritarian zone of the domain. This can be a provider other than your web hosting. Registration a customer account does not change this responsibility. Search the existing A entry for the desired host name and check the type, name and previous target value before you edit it.

Save the new IPv4 address in exactly this entry. Do not add a second contradictory entry unnoticed if an existing target is to be replaced. The spelling for the main domain can look different depending on the interface. Only take over the display provided by the respective DNS provider. Then note the stored value and the change date for the control.

Determine responsibilities and existing services

Note before a change, which registrar has the domain, where the DNS zone is managed and on which hosting the website is running. These tasks can be with different providers. The place where you upload your website files is therefore not automatically the place for DNS changes. The actual responsible name servers and the associated login data are decisive.

Also create a list of existing services: website, email, subdomains and, if necessary, external applications. Determine their previous entries. This will identify which parts are affected by the planned step and what should continue to run unchanged. Secure the information outside of the system to be moved so that you can still look it up on a temporarily unavailable website.

Consider caches and other address entries

After saving, different resolvers can still provide different answers. Already stored DNS data does not disappear by a new customer login or a browser click. Therefore, check the value stored by the provider as well as the answer described by a resolver. These are different control points in the process.

Also note existing AAAA entries for IPv6 and possible CNAME links. A correctly changed A entry does not help if visitors continue to use another, unsuitable destination for the same website. Do not remove any entries unchecked: First, it must be known which addresses the target system actually supports and how the affected host name has been built up so far. Document any change made consciously.

Then test Web server assignment and HTTPS

The new server must know the domain and assign it to the right project. Otherwise, the DNS resolution can already be correct, while the browser displays a default page, another project or an error. This is to be distinguished from a wrongly stored IP address. Therefore, first check the domain assignment on the target system and then the delivered website.

Call the important addresses with HTTPS and check the certificate, forwarding and internal links. Test not only the start page, but also central subpages and required logins. If the change causes problems, the documented old value helps with the planned return. Keep in mind data changes on the new system so that a return does not lose any content received by now.

Check website, e-mail and DNS separately

A domain can address a website and several other services at the same time. MX entries, for example, control the receipt of emails, while an A entry indicates an IPv4 destination address. TXT entries can be required for proof of ownership or Maila authentication. Therefore, do not change the entire zone if only the website is to switch to a new server.

After a change, check the website with and without www as well as the actually used subdomains. In addition, test email with a controlled sending and receiving process. A home page visible in the browser does not yet prove a working mail delivery. If you need help, call the affected domain, the entry type, the exact error message and the change date. Secret access data does not belong in a support message.

Distinguishing Mission, Hosting and Domain Costs

Under Domains You can prepare the appropriate project. Information about the address is not yet a reservation and not a completed registration. New registrations and transfers are first processed manually at dhosty. An existing domain contract remains, as long as you do not explicitly order a change and this has been completed.

The selected hosting package regulates the technical website functions. Registration of a domain name is to be considered separately from this. A platform address in free hosting is therefore not a claim to any own .de or .com domain. Before closing, check the agreed prices, the runtimes and the responsibility for renewals.](/hilfe/) you will find further information about the connection and the order process.

Frequently asked questions

Is a domain information already a completed registration?

No. The query provides a technical status and does not reserve the name. A job will be submitted separately and first processed manually. Check domain name, conditions and final availability before completion; plan a useful alternative for an open address.

Does an existing mail service need to be changed when changing the website?

Not only because of the website. First check which MX and TXT entries the previous mail delivery needs. A change of the website destination is to be distinguished from a mail transfer. Test after the conversion website and email separately and keep the previous entries on.

Does PHP or databases arise through a separate domain?

No. The domain name addresses a target; the software functions depend on hosting and the set-up application. Therefore, compare the required technical scope of services before selecting a package. The choice between main domain and subdomain does not answer this question.

What information helps with a connection problem?

Name domain, affected hostnames, entry type, exact errors and change date. This allows you to view DNS, project assignment and HTTPS separately. Don't send passwords or secret transfer codes in a general support message. For several changes, a chronological list of stored values helps.

More hosting topics