How can we help you today?

How to Use the DNS Check

Created by: Sophie van Vrijberghe de Coningh

Modified on: Fri, 4 Jun, 2021 at 11:50 AM


Use the DNS check in the Control Panel to ensure your externally hosted domain is properly configured to send email via Hypernode. The DNS check also verifies whether the domain is correctly pointed to the Hypernode by checking the CNAME- and A-records. 

Please note that if you are using Cloudflare or another CDN type product, we cannot check your records.

TABLE OF CONTENTS

Email Records

The TransIP records below do not apply when your Hypernode does not have TransIP mail enabled. The DNS Check will not check the DKIM A, DKIM B and Mail Auth records when TransIP mail is not enabled.

If your domain is hosted externally and you want to send email via a TransIP mail enabled Hypernode, there are some DNS records that need to be added to the external DNS. When these records are set the external domain can send email via TransIP. 

DKIM A Record

This record should be as follows: 

LabelTypeTTLContent

ns0-a._domainkey

CNAME600

 _dkim-A.ns0.email

This record is needed for automatic DKIM signing and DMARC.

DKIM B Record

This record should be as follows: 

LabelTypeTTLContent

ns0-b._domainkey

CNAME600

 _dkim-B.ns0.email

This record is needed for automatic DKIM signing and DMARC.

Mail Auth Record

This is the mail auth record required by TransIP and should be as follows: 

LabelTypeTTLContent

x-transip-mail-auth

TXT600

"f491ddb3e61d1c92ab6de9f81257b1c0b95986d6550517f005c8e5e895da6fd2"

SPF Record

This is the TransIP SPF record. If you already have an SPF record, you need to add the TransIP SPF include (include: _spf.transip.email).

LabelTypeTTLContent

@

TXT600

v=spf1 include:_spf.transip.email ~all

When TransIP mail is not enabled the DNS Check still verifies whether the SPF record is valid and does not contain any errors. Please see this article for how to set up your SPF records for Hypernode.

Web Records

The DNS Check verifies whether the domain is correctly pointed to the Hypernode by checking the CNAME- and A-records. 

CNAME Record

The recommended way to configure your DNS is to create a CNAME record in your DNS configuration, pointing to Hypernode:

LabelTypeTTLContent

www.example.com

CNAME600

example.hypernode.io

This means that www.example.com will point to wherever example.hypernode.io points, and we will make sure that that always points to the correct IP address.

A Record

One way to redirect your apex (or naked) domain, when the domain is not hosted on the Byte name servers, is to use the www-izers:

LabelTypeTTLContent

example.com

A600

 46.21.232.141

example.comA600

 46.21.233.172

Add both for redundancy!

This is the preferred way for the DNS Check because if for whatever reason the IP of your Hypernode changes, your shop will still be reachable. 

NB: Note that if you make use of the www-izer redirect servers, users that visit https://example.com directly will get an error message, either indicating that there is no HTTPS available or a plain connection refused error. The www-izers actually work as a forwarding service to the direct IP address of the Hypernode. This way we can manage any IP changes for you. That is the advantage, the disadvantage is that these records do not cooperate with SSL and that therefore the certificate does not work properly on the domain name without the www. 

It's also an option to use the direct IP address of your Hypernode. You can find your IP with the “ping example.hypernode.io” command. 

LabelTypeTTLContent

example.com

A600

IP of your Hypernode

Please note that if you use the direct IP, the DNS Check will show a warning, as you will encounter DNS downtime if the IP-address of your Hypernode changes. 

Hypernode Reachable

The DNS Check verifies whether the Hypernode is reachable via the URL you entered.

Using Cloudflare or Other CDN

If you are using Cloudflare or another CDN type product, we cannot check your records with our DNS Check. Use the records below to check the DNS records yourself to make sure your Hypernode is reachable via your domain.

CNAME Record

The recommended way to configure your DNS is to create a CNAME record in your DNS configuration, pointing to Hypernode:

LabelTypeTTLContent

www.example.com

CNAME600

example.hypernode.io

This means that www.example.com will point to wherever example.hypernode.io points, and we will make sure that that always points to the correct IP address.

A Record

One way to redirect your apex (or naked) domain, when the domain is not hosted on the Byte name servers, is to use the www-izers:

LabelTypeTTLContent

example.com

A600

 46.21.232.141

example.comA600

 46.21.233.172

Add both for redundancy!

It's also an option to use the direct IP address of your Hypernode. You can find your IP with the “ping example.hypernode.io” command. 

LabelTypeTTLContent

example.com

A600

IP of your Hypernode


S
Sophie is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.