|
1
|
| Check availability |
| Enter your desired domain in the domain check. Do the same for a domain transfer to MyWebspace. |
|
2
|
| Select domain |
| If the desired domain is still available, you can add it to your cart. For a domain transfer to MyWebspace, you need to enter a so-called auth code. You can find more information here. |
|
3
|
| Buy domain |
| A customer account is required to buy a domain. Once the invoice has been paid, the domain is registered automatically and is available in your MyWebspace Panel. |
| Billing | annually in advance, via bank transfer or PayPal |
| Notice period | 35 days before contract renewal |
| Invoicing | via e-mail |
| Setup fee | free of charge |
| Minimum contract term | 1 year |
| Availability | upon receipt of payment |
| Upon conclusion of contract | our terms and conditions apply |
How about a MyWebspace package?
Then you also need a suitable MyWebspace package that provides these features.
Individual domain solution
FAQ
Yes, your domain will be renewed automatically, and the e-mail is an annual standard e-mail from our domain provider confirming the automatic domain renewal once again.
All domains at MyWebspace are renewed automatically unless customers want to cancel them.
The e-mail usually looks roughly like this:
....
Domainname | Exp.-Date | Last Ren.-Date | Autorenewal
-------------------+------------+----------------+------------
domainnamen.net | 2026-08-08 | 2026-08-08 | yes
....
The "yes" confirms the domain renewal once again. You can ignore the e-mail.
Yes, you can. Simply send us a message with the desired domain extension via the contact form and we will get in touch with you.
When registering a domain, you have to provide some data such as your postal address, an existing e-mail address, phone number, etc. This data is required by the domain registry! Without it, domains unfortunately cannot be purchased. Please make sure the data is correct and complete so that you also have full legal rights to the domains you register. Of course, we handle your data with care and will never pass it on to third parties without asking, except for registering domains.
Data protection is very important to us!
Great! We're glad to hear that :)
To transfer a domain to MyWebspace, you need the following:
Apart from the domain costs mentioned, there are no extra fees for the domain transfer.
If you already have a website or e-mail address with your old domain provider, we can take these over as well. Depending on the effort involved, migration costs may apply, which we will clarify with you in advance.
If you would rather we handle the domain transfer for you, you can contact us via the contact form.
A subdomain such as "xyz.example.com" can be created under the menu item "Domain" in the MyWebspace Panel.
Enter the corresponding name in the "Subdomain" field, e.g. xyz.example.com.
The path points to the content location of the created subdomain. The directory is created automatically.
An entry with the prefix "www." is also added. (For example, if you enter "xyz" as a subdomain for example.com, your website will be reachable at xyz.example.com and www.xyz.example.com.)
When you create new subdomains, DNS records are added automatically. You should always check the DNS configuration to make sure they were added correctly and that no outdated records remain if you rename something.
| A | is used to point records to IPv4 addresses. |
| AAAA | is used to point records to IPv6 addresses. |
| ALIAS | fetches AAAA and A records from another domain and inserts them here. This works similarly to a CNAME but can be used at the domain apex and together with other records such as TXT. Please note that MyWebspace servers in Austria are used to resolve the records, which may affect geography-based routing. The domain is interpreted as it is and, unlike a CNAME, does not need to end with a dot. |
| CNAME | is used to point a record to another record. Note that the data must end with a dot (.) to point to another domain. |
| MX | is used to specify a mail server for the domain. The record data must be in the format \priority domainname\. Example: \20 mail.my-webspace.at.\. Note that the data must end with a dot (.) to point to another domain. |
| NS | is used to point to another name server. |
| TXT | is used to add arbitrary text to the DNS system. Google and other providers use this as a method to verify domain ownership. |
MyWebspace provides a simple REST API to update DNS entries automatically. This allows you to do a number of things:
The REST API can only update existing entries, not create new ones, so you have to create the entry in the my-webspace.at panel first.
Please keep in mind that the key must be kept private! With the key anyone could change your DNS records. If you think you key has been compromised, please delete the DNS entry in the my-webspace.at panel and re-create it. A new key will be provided for you.
At the moment you can use the API to update A, AAAA and TXT records. The API can be accessed via HTTPS (preferred) or plain HTTP:
| Endpoint | https | http |
|---|---|---|
| Default protocol | https://panel.my-webspace.at/dns | http://panel.my-webspace.at/dns |
| IPv4 | https://4.panel.my-webspace.at/dns | http://4.panel.my-webspace.at/dns |
| IPv6 | https://6.panel.my-webspace.at/dns | http://6.panel.my-webspace.at/dns |
You can supply the following parameters, either via GET or POST:
| Parameter | Value |
|---|---|
| key | Autoupdate-Key from the panel, mandatory to query or change DNS-records |
| a | Only for A records, IP address to set. Can use the special value "remote" to use the address the request is coming from. The address needs to be a valid IPv4 address. When using the "remote" feature the endpoint 4.panel.my-webspace.at should be used to ensure IPv4 is being used for the request and a valid IP address is returned for the record type. |
| aaaa | Only for AAAA records, IP address to set. Can use the special value "remote" to use the address the request is coming from. The address needs to be a valid IPv6 address. When using the "remote" feature the endpoint 6.panel.my-webspace.at should be used to ensure IPv6 is being used for the request and a valid IP address is returned for the record type. |
| txt | Only for TXT records, the new content of the record |
If no new record data is provided, only the existing data is returned.
The response is a JSON object with the following values:
| Key | Value |
|---|---|
| status | "error": In case of an error, more information is provided in the "error" key "unchanged": The current value was already stored in the DNS record "updated": The DNS record has been updated and the changes will be reflected in the DNS soon |
| error | Only if status == "error", the error message. One of "bad key", "key missing", "invalid A data" or "invalid AAAA data" |
| domain | The top-level domain being changed or queried |
| name | The subdomain being changed or queried |
| type | The type of the DNS record |
| data | The (new) value of the DNS record |
| remote-ip | The IP the query originated from. This is always included, even if no parameters are supplied. |
If you have a Linux (or BSD) server behind a dynamic IP Address you can use the following entry in your crontab to update a DNS entry on my-webspace.at to always point to your server:
15 * * * * wget -O - 'https://4.panel.my-webspace.at/dns-update.php?key=Key to your A record&a=remote' > /dev/null 2>&1
If you have an IPv6 enabled connection you probably want to update IPv6 entries as well:
15 * * * * wget -O - 'https://6.panel.my-webspace.at/dns-update.php?key=Key to your AAAA record&aaaa=remote' > /dev/null 2>&1
This API can also be used to fetch the current IP Address. For example with jQuery:
jQuery.get("https://panel.my-webspace.at/dns", function(data) {
var your_ip = data["remote-ip"];
alert("Your IP is " + your_ip);
}, "JSON");
A DNS challenge is currently the only way to get wildcard certificates. The MyWebspace DNS API allows you to use this feature.
Step 1: Create a TXT record in the panel, named _acme-challenge.example.com, replace example.com with your actual domain or subdomain. Wildcards only work for one level, so the above entry will work for example.com, foo.example.com and bar.example.com, but not foo.bar.example.com. The data entry of the txt dns-record can be a random string. Note, the entries Autoupdate-key for the next step. This is the key, which you have to use in the 2nd step.
Step 2: Create a file /root/dns-hook.sh on the machine which will receive the certificate. Note that this does not have to be the server which will host the content, but most likely it is:
#!/bin/sh wget -O - "https://panel.my-webspace.at/dns?key=**key-here**&sync=true&txt=$CERTBOT_VALIDATION" >&2
Don't forget to make it executable: chmod +x /root/dns-hook.sh
Step 3: Run certbot, replace example.com with your actual domain. Remove the -d *.example.com part if you only want a regular certificate, not a wildcard certificate.
certbot certonly --manual --preferred-challenges dns -d 'example.com' -d '*.example.com' --agree-tos --manual-auth-hook /root/dns-hook.sh
Note: You can also use this if your domain is not hosted by MyWebspace, as long as you have at least one MyWebspace hosted domain. Let's assume example.com is at MyWebspace but example.org isn't. You want to create a Certificate for *.example.org. The way you can do this, is that you first create a TXT record in example.com, for example _org-validation.example.com. Use its Autoupdate key in the steps above. Then you create a CNAME record on your other provider. Call it _acme-challenge.example.org and have it point to this new TXT record _org-validation.example.com at MyWebspace. Take into consideration that your external provider may take a while to publish the CNAME, so verify it has before continuing with Step 2.