{"id":8443,"date":"2015-03-17T18:50:00","date_gmt":"2015-03-17T18:50:00","guid":{"rendered":"https:\/\/wp.okra.host\/article\/creating-an-addon-domain\/"},"modified":"2021-03-07T14:11:04","modified_gmt":"2021-03-07T13:11:04","slug":"creating-an-addon-domain","status":"publish","type":"ht_kb","link":"https:\/\/kb.okra.host\/de\/article\/creating-an-addon-domain\/","title":{"rendered":"Erstellen einer Addon-Domain"},"content":{"rendered":"

\u00dcbersicht<\/h2>\n

An addon domain is a domain in addition<\/em> to your primary domain. Every package supports an unlimited number of addon domains, limited only by the amount of storage and bandwidth allotted to your account.<\/p>\n

Adding a new domain<\/h2>\n

A new domain may be added within the Bedienfeld<\/a> unter\u00a0DNS<\/strong> > Addon-Domains<\/b>. There are a couple\u00a0tunable parameters of interest. First is the\u00a0domain document root<\/em>, which indicates from where site content<\/a>\u00a0for this new domain will be served.<\/p>\n\n\n\n\n\n
Domain Document Root<\/strong><\/caption>\n
Site Root<\/strong><\/td>\nServe from a directory within\u00a0\/var\/www<\/code>; in single-user\u00a0scenarios this is optimal<\/td>\n<\/tr>\n
User Home<\/strong><\/td>\nServe from a directory within a user home directory<\/a>;\u00a0this domain will be managed by a secondary user<\/td>\n<\/tr>\n
Subdomain<\/strong><\/td>\nServe from a preexisting subdomain, this domain is aliased to the subdomain and vice-versa<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Second,\u00a0enable e-mail for this domain<\/em><\/strong>\u00a0<\/em>will authorize the server to handle mail for the domain. If you are using a third-party mail service, this option must\u00a0be disabled to avoid problems<\/a>.<\/p>\n

Once enabled, visit\u00a0Mail<\/strong> >\u00a0Mailboxen verwalten<\/strong> to create new e-mail addresses for users on this domain. In certain situations, an e-mail address username may overlap. In these situations, it’s prudent to use a namespacing technique<\/a>\u00a0to separate e-mail delivery.<\/p>\n

After adding the domain, ensure you have changed nameservers for the domain to our Nameserver<\/a>. Nameserver settings are changed through the company through which you registered the domain. If you registered the domain through our registrar<\/a>, then this has been done for you already.<\/p>\n

Validating ownership<\/h3>\n

If a domain is already registered and already has nameserver records set to those\u00a0other than our nameservers<\/a>, additional verification is necessary. This is to prevent unlawful hijacking of domains and mail routing that would otherwise be disastrous to clients on the same server. Complete 1 of 3 options available to verify that you are the owner.<\/p>\n

\"Addon<\/a><\/p>\n

Addon domain verification error that must be completed before a domain may be added to an account.<\/p>\n<\/div>\n

Wichtig:<\/strong><\/span> there are two caveats with regards to DNS that may take longer to complete verification if done\u00a0after<\/em> attempting to add the domain as a consequence of how DNS caching<\/a> (TTL) works:<\/p>\n