You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hypernode-platform/dns/dns-for-control-panel-users.md
+22-10Lines changed: 22 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,13 @@ More information about DNS settings for your webshop on Hypernode technology, fo
20
20
21
21
## Manage DNS With a Third Party
22
22
23
-
Please note that Hypernode cannot provide uptime guarantees for external DNS. Your SLA does not apply in this case. When a domain name is registered externally, please keep in mind that Hypernode has no influence on the functioning of the DNS. If you don't want to transfer your domain name to Hypernode, changing the name servers to the Byte name servers is a good second option. You will need a Presence plan to be able to manage your DNS from the Service Panel. When you have the DNS set up correctly you can ask your domain name provider to change the name servers to the Byte name servers:
23
+
Please note that Hypernode cannot provide uptime guarantees for external DNS, so your SLA does not apply in this case.
24
+
25
+
If your domain name is registered with an external provider, please be aware that Hypernode has no control over the availability or functioning of that provider’s DNS services.
26
+
27
+
If you prefer not to transfer your domain name to Hypernode, a good alternative is to update your domain’s nameservers to the Hypernode nameservers. To manage your DNS through the Service Panel, you will need a Presence plan.
28
+
29
+
Once your DNS has been configured correctly, you can ask your domain provider to update the nameservers to the Hypernode nameservers:
24
30
25
31
ns1.hypernode.com
26
32
@@ -94,11 +100,11 @@ Different DNS records have been created for the different types of internet traf
94
100
95
101
The NS records contain the "authoritative name servers" or prevailing name servers. When your domain name is listed with Hypernode, these will always be on Byte's name servers by default. This determines that we are the party that manages the DNS records. You can also find them in the WHOIS. The Byte name servers are:
96
102
97
-
nsa.byte.nl
103
+
ns1.hypernode.com
98
104
99
-
nsb.byte.nl
105
+
ns2.hypernode.com
100
106
101
-
nsc.byte.nl
107
+
ns3.hypernode.com
102
108
103
109
If you have set up other name servers, the DNS data will be downloaded from that server. Hypernode always recommends using the Byte name servers so that in the event of IP changes (if you switch from datacenter) we can switch quickly, without having to make changes to the DNS configuration. You can NOT change the name servers from the Service Panel. If you need to change the name servers (to for example Cloudflare) you can request this by sending an email to [support@hypernode.com](mailto:support@hypernode.com) (from the email address that is linked to the account).
104
110
@@ -114,13 +120,19 @@ This is the A record for IPv6 addresses.
114
120
115
121
### MX Records
116
122
117
-
The MX records contain the host names of the mail server(s). In addition to the hostname, you can assign a priority to each MX record. For example, you can give your own mail servers a higher priority (a lower number) than our smtp2.byte.nl server. This means that smtp2.byte.nl is only used as a mail server when your own servers are not available. We also call this "fallback server". Also make sure that you do not give every MX record a priority of 10, otherwise our server will not be able to determine which record is about the primary mail server. These are the MX records of the Hypernode mail servers:
123
+
MX records determine where email for your domain should be delivered. The value of an MX record must point to the mail server that handles incoming email for your domain. Each MX record also includes a priority: the lower the number, the higher the priority.
124
+
125
+
If you use multiple mail servers, the server with the lowest priority number is treated as the primary server. A second server can be configured as a fallback by giving it a higher priority number.
126
+
127
+
Make sure not all MX records use the same priority. If they do, sending servers may distribute delivery across them instead of treating one as the primary server.
0 commit comments