Domains, DNS & HTTPS · 6 min read
Connecting your own domain: separating contract and DNS properly
The question "Join your own domain" does not only concern an entry in your 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 them.](/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.
What remains with the previous domain provider
You can connect an existing domain to another hosting without transferring it to a new registrar. The domain contract, the stored owner data and the extension remain with the previous provider. The name servers can also stay there. Only the DNS targets for the website are set to match the new hosting.
Don't confuse such a connection with a transfer. To connect, you need the correct target values of hosting and access to DNS management. An Auth code is intended for a registrar change and not required for every website connection. Decide in advance whether you want to move the website or also change domain management. This saves unnecessary interference with a working contract.
Assigning the domain to the right web project
First, specify which web project the address should be. Note the desired main address and whether visitors should also access the same website via www. In the customer area, the domain must be assigned to the intended project; a DNS entry alone does not replace this server-side assignment. Use the target values specified for exactly this project.
If a proof of ownership is requested, set the specified TXT entry at the responsible place and check the status afterwards about the intended process. Invent no own values. A visible domain in the form is not yet completed proof. If there are uncertainties, you clarify the assignment before the public conversion and keep the previous hosting as a relapse possibility for so long.
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.
Modify DNS from the responsible provider
Open the DNS management of the domain and search for the entries for the desired website address. Changes are part of the responsible provider of the zone; they are not made solely by creating a Dhosty customer account. If you want to change name servers, the new zone must contain all the remaining entries before switching.
A complete name server change is not always necessary for a pure website connection. It is often enough to adjust the appropriate website entries. Check the specific structure before you delete something. Keep old target values together with the time of the change. This allows you to understand whether a later error has been caused by an outdated cache, the new server assignment or an accidentally modified address.
Preparing HTTPS and the transition
The new website should be prepared on the target system before you change the domain to the public. This includes the correct content, the domain assignment and a matching HTTPS certificate. The connection to the server and the validity of the certificate are two different checks. A successful retrieval via an internal preview address does not prove that the final domain is set up correctly.
Plan a phase in which not all visitors receive the same DNS response immediately. Keep the old website accessible as far as possible until the connection has been reliably checked. Avoid contradictory content changes on two systems during the transition. Determine where new data may arise and how they should be retained when a change occurs.
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.