This guide explains how to set up a zone delegation for a subdomain.

Prerequisites

• Have a domain name with Infomaniak or at least a DNS zone.
• Understand:
  • the operation of a domain and a DNS zone before modifying the latter.
  • that the DNS zone shown here is only valid and used if the nameserver are those of Infomaniak.
  • that any DNS addition or modification can take up to 48 hours to propagate.

Setting up a zone delegation

For this:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on DNS Zone in the left sidebar.
4. Click on the Advanced view tab.
5. Click on the + button:
   
6. Enter the desired subdomain (e.g. test to get test.domain.xyz)
7. It is now possible to edit the DNS zone of the delegated subdomain.

This guide explains which DKIM to add to secure Infomaniak email if it is based on a domain name whose DNS is managed by Cloudflare.

Preamble

• If you manage your emails with Infomaniak, as well as the associated domain name, but DNS management is with Cloudflare, then you need to add a DKIM on the Cloudflare interface.

Add a DKIM on Cloudflare

Prerequisites

• Familiarize yourself with this other guide to allow you to display the DKIM corresponding to your Infomaniak email.
• Display the DKIM to copy and paste. Example:
  • 

Then follow the procedure below to correctly activate DKIM, thereby enhancing the security and deliverability of emails for the domain in question:

1. Click here to access your Cloudflare account.
2. Select the relevant domain.
3. In the DNS section, search for and delete all NS records for "_domainkey" pointing to Infomaniak.
4. Add a new TXT record for DKIM (it is not enough to paste the DKIM signature visible on the Infomaniak Manager for it to work):
   1. Type: TXT
   2. Name: Enter only the DKIM selector provided by Infomaniak (without "_domainkey" or the domain name), for example 20240112…
   3. Content : Paste the public DKIM key provided by Infomaniak (what comes after p=)
   4. TTL : Auto
5. Save the changes.
   • Any DNS addition/modification may take up to 48 hours to propagate.
6. Use an online DKIM verification tool to confirm the configuration.

This guide explains how to link a domain name to the NAS Synology that you rent from Infomaniak.

Associate a domain

To connect your domain name to the Synology:

1. Click here to access the management of your product on the Manager Infomaniak (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on Link a domain name (in the Associated domains section):
   
4. Enter a domain name.
5. Repeat the operation if necessary for your other domain names.

This guide concerns the possible messages you may receive mentioning terms such as WDPR (WHOIS Data Problem Report System) and WHOIS, which refer to notifications and policies associated with the management of domain names on the Web.

WDPR (WHOIS Data Problem Report System)

WDPR, or WHOIS Data Problem Report System, is a system established by the ICANN (Internet Corporation for Assigned Names and Numbers). This system allows users to report problems with WHOIS data. Here are the key points of this system:

• Reporting problems: users can report inaccuracies or incorrect data in the WHOIS information of a domain; common problems include outdated contact addresses, incorrect phone numbers, or fraudulent information
• Reporting process: to report a problem, users must fill out a form available on the ICANN website; this form requests details about the problem observed and the WHOIS information concerned
• Problem resolution: once a problem is reported, ICANN takes steps to investigate and resolve the inaccuracy; this may involve updating the WHOIS information by the concerned registrar
• WHOIS information: the information available via WHOIS includes the domain holder's name, contact address, phone number, and email address; this information is generally public and accessible to anyone performing a WHOIS search
• Confidentiality: although WHOIS information is public, many registrars like Infomaniak offer WHOIS privacy services; these services mask the personal information of the domain holder, displaying the contact details of the privacy service instead
• Updates: it is essential that domain holders keep their WHOIS information up to date; ICANN requires that the information be accurate and complete: incorrect information can result in the suspension or cancellation of the domain

Letters mentioning WDPR and WHOIS

Letters mentioning WDPR and WHOIS follow specific guidelines to inform domain holders of the next steps and necessary actions:

• WHOIS problem notification: an email informing that a problem with the WHOIS information has been reported; this email will contain instructions on how to verify and correct the inaccurate information
• Update reminder: an email reminding domain holders of the importance of keeping their WHOIS information up to date, often sent periodically to ensure continued compliance
• Resolution confirmation: an email confirming that the modifications or updates made to the WHOIS information have been successfully completed, following a problem report

These letters are essential to ensure that information related to domain names remains accurate and up to date, which is crucial for the security and effective management of domains. They also help protect domain holders from potential issues, such as missed notifications or legal actions due to inaccurate information.

By carefully following the instructions and reminders contained in these letters, domain holders can avoid service interruptions, domain loss, and other complications associated with the management of domain names on the Web.

Change the language of these letters

The French, English, German, etc. language applied to a WHOIS contact can be modified on the management page of its details related to domain names.

This guide explains how to add or modify one or more TXT record entries in the DNS zone (of a domain name) managed on the Manager Infomaniak.

Preamble

• The TXT record type allows you to insert readable text into the DNS zone of a domain name.
• This is the method generally used to help prevent spam and to verify domain ownership (Google may ask you to do this before using some of their services).

Modify the DNS zone

Refer to this other guide to manage this type of record in a DNS zone.

This guide explains how to add or modify one or more CAA type records in the DNS zone (of a domain name) managed on the Manager Infomaniak.

Introduction

• A CAA record allows you to specify a certification authority authorized to issue certificates for a domain.

Add a CAA

Refer to this other guide to manage this type of record in a DNS zone.

Adding CAA to validate an SSL certificate…

… Sectigo

In the case of a SSL certificate validation for Sectigo, follow the generic guide above but enter the following data specifically:

• Select "Issue for Certification Authority".
• Enter the flag: 0.
• Specify sectigo.com:

… Let's Encrypt

In the case of a SSL certificate validation for Let's Encrypt, follow the generic guide above but enter the following data specifically:

• Select "Issue for Certification Authority".
• Enter the flag: 0.
• Specify letsencrypt.org:

This guide explains how to add or modify a DKIM record in a DNS zone (domain name) managed on the Manager Infomaniak.

Preamble

• The DKIM (Domain Keys Identified Mail) record type is a protocol that allows emails to be signed when they are sent and ensures the optimal operation of your Infomaniak messaging.
• This ensures that the content of emails is not altered during transit and that they genuinely originate from the sender's domain. This standard thus prevents spammers from impersonating legitimate entities.
• DKIM will fail if it detects that a message has been altered and unauthorized changes have been made to the Fromof the message.
• The DKIM standard is enabled for all Infomaniak clients with a Mail Service whose domain name has its DNS zone managed at Infomaniak. All emails sent from Mail or your chosen email software/client are therefore automatically signed.
• DKIM is not available for subdomains.

Check the DKIM record

The Global Security tool allows you to easily check and correct certain problematic records.

And when your domain name is managed elsewhere, you will find the DKIM record to add in the DNS zone:

Manually modify the DNS zone (not recommended)

Refer to this other guide to manage this type of record in a DNS zone.

Add multiple DKIM

You can have multiple DKIM records on your domain without limit, unlike DMARC or SPF, as long as your DNS host allows it.

If you use several third-party email providers, for example the ERP Odoo, it is necessary to add a DKIM for Odoo in addition to that of Infomaniak.

Use unique DKIM selectors to avoid conflicts with existing records.

This guide explains how to add or modify one or more CNAME and DNAME type records in the DNS zone (of a domain name) managed on the Manager Infomaniak.

Preamble

• The CNAME record type allows pointing a subdomain to a website address.
  • This is the method generally used to operate the www subdomain with your site, or to redirect a subdomain to a folder on the web server where your website is hosted.
• The DNAME record type for «delegation name» is particularly useful when reorganizing domains or for smooth transitions of part of your infrastructure to another, while preserving the hierarchical structure of subdomains.
  • A DNAME creates an alias for an entire domain and all its subdomains.
• Unlike a CNAME which applies to a single specific host name, a DNAME automatically redirects all subdomains. Example:
  • A DNAME for abc.site1.com pointing to site2.com will automatically link xyz.abc.site1.com to xyz.site2.com, new.login.abc.site1.com to new.login.site2.com, and so on.
• ⚠ A DNAME record cannot be used at the root level of a domain (such as site1.com directly). It is generally used on a subdomain. If you want to redirect the main domain itself, you will need to use other types of records such as an A, AAAA or CNAME (with some restrictions for the latter).
   

Modify the DNS zone

Refer to this other guide to manage this type of record in a DNS zone.

This guide explains how to display the IP address of a site on your Web Hosting.

Preamble

• The IPv4 address is generally the same for each site on the hosting (unless you have acquired a dedicated IP).

Display the IP address of your site

The IP address is specified on the hosting management page (Starter or containing multiple sites):

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Then click on the chevron ‍ to expand the Information section of this hosting.
4. The IPv4 address is displayed on the page:
   
5. The IPv6 address is also displayed in the case of paid hosting:
   

This guide explains how to add or modify an MX record in the DNS zone (of a domain name) managed on the Manager Infomaniak.

Introduction

• The "MX" record type allows you to specify which provider should handle the email (= the target).
• You should only modify this type of record if you have a specific configuration to implement (e.g., domain name at Infomaniak and email service with an external provider).
• There can be several MX records (so that a second email service takes over in case of failure of the first) and in this case a number designates the priority of each of them (the smaller the number, the higher the priority).

MX for Infomaniak mail

Infomaniak automatically provides the MX record needed to link your domain name and your email, if both are managed within the same organization at the Manager level.

If your configuration requires you to add an MX record yourself to direct mail traffic to Infomaniak, then specify the following MX:

mta-gw.infomaniak.ch

with the priority 5.

On the interface of some providers like Gandi, it is necessary to add a dot at the end of the MX record:

mta-gw.infomaniak.ch.

A correct SPF record is also required for proper functioning of Infomaniak's email service.

Modify the DNS zone

Refer to this other guide to manage this type of record in a DNS zone.

Learn more

• Link a domain to an Infomaniak Mail Service
• Specify the Infomaniak MX with a third-party web provider

This guide explains how to access a Sunrise Internet Box connected to the Internet with a dynamic IP via a domain name.

Prerequisites

• Have a Box that allows configuring a custom dynamic DNS provider.
• A dynamic DNS must have been created on the domain in question.

Link a Sunrise Internet Box to a domain name

There are different models of Sunrise Internet Box. Here is an example:

1. Log in to the Sunrise Box administration interface (http://192.168.1.1 for example).
2. Enable expert mode (top right button).
3. Go to DynDNS (top left):
   
4. Click on the DynDNS tab.
5. Enable the Dynamic DNS client.
6. Choose the “Custom” provider:
   
7. Fill in the following fields:
   • Username = the identifier defined in the Manager when adding the Dynamic DNS
   • Password = the password defined in the Manager when adding the Dynamic DNS
   • Hostname = the URL configured in the Manager when adding the Dynamic DNS
8. Below, fill in the following fields:
   
   • Server: infomaniak.com
   • Port: 443
   • Request (to copy-paste as is): https://infomaniak.com/nic/update?hostname=[DOMAIN]&myip=[IP]&username=[USERNAME]&password=[PASSWORD]
   • Update interval (seconds): 300
   • Retry interval (seconds): 30
   • Max attempts: 3

The interface may be presented in this form but the principle remains the same:

Other routers

It's the same principle for an Omada SDN solution from TP-Link; the Update-URL is https://infomaniak.com/nic/update?hostname=[DOMAIN]&myip=[IP]&username=[USERNAME]&password=[PASSWORD]:

And for other models (type Zyxel USG Flex or ax7501-B1 for example) fill in the fields using the data below:

1. Enable DDNS Profile : enable
2. DDNS Type : User custom
3. HTTPS : enable
4. Username : the identifier defined in the Infomaniak Manager when adding the Dynamic DNS (help)
5. Password : the password defined in the Infomaniak Manager when adding the Dynamic DNS (help)
6. Domain Name : host name with the domain
7. Primary Binding Address > Interface : any
8. Backup Binding Address > Interface : none
9. DYNDNS Server : infomaniak.com
10. URL (to copy-paste as is) : /nic/update?password=password(point 5 above)&username=username(point 4 above)&hostname=DomainName
    • example /nic/update?password=abcd1234&username=admin&hostname=abc.domain.xyz

This guide details the monetization of domain names, generally carried out via domain parking while keeping the reseller's details hidden.

Domain parking

Domain parking is a technique that involves registering a domain name without immediately using it for a website.

Instead, the domain name is "parked" and typically displays a parking page with advertisements generated by an affiliate network.

The owner of the "parked" domain name can then earn money through these ads as a passive income source.

What if you are the visitor?

Be vigilant: some domain parking pages may resemble legitimate websites, which can cause confusion for users trying to access a particular website, and others may be infected with malware, which can be dangerous for users' cybersecurity.

This guide explains how to implement a DMARC policy for your email hosted by Infomaniak, an essential element to prevent potential delivery issues.

Preamble

• DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an essential tool for enhancing email security and protecting your domain against fraud by verifying the authenticity of outgoing emails (through authentication mechanisms such as SPF and DKIM) and allowing you to define policies for handling unauthenticated emails.
• DMARC is used to specify to other mail providers what they should do when they reject an email due to incorrect or missing SPF or DKIM.
• To do this, domain owners can define DMARC policies, such as "reject", "quarantine" or "none", to specify how these "suspicious" emails should be handled. Example:
  1. An email is sent from anna@domain.xyz to victor@yahoogle.abc.
  2. The Mail Service of domain.xyz contains a DMARC configuration of type reject at 100%.
  3. The Mail Service of yahoogle.abc is well secured and proceeds with the SPF/DKIM/DMARC analysis of the mail arriving from domain.xyz.
  4. If this analysis results in a failure of the SPF or DKIM, then the Mail Service of yahoogle.abc will reject (and therefore delete) the message.
  5. It will send a report by email if a report address is specified in the DMARC of domain.xyz.
     • These DMARC reports generated help you maintain and improve the security of your domain; you will thus be able to identify any authentication errors and phishing attempts using your domain.

DMARC policy and acceptance percentage

For the instructions that can be given to recipient servers when a suspicious message is detected, 3 policies (p = policy) exist and can be refined with a percentage (pct):

none

With "p=none", no email is rejected or quarantined based on DMARC verification. However, the percentage of reception can be used to collect data on unauthenticated emails, indicating how many of these emails should be subject to the DMARC policy. For example, "p=none; pct=10" means that 10% of unauthenticated emails will be subject to the DMARC policy, while the remaining 90% will be accepted.

quarantine

With "p=quarantine", unauthenticated emails may be placed in quarantine, but the reception percentage determines the proportion actually subject to this policy. For example, "p=quarantine; pct=50" means that 50% of unauthenticated emails will be placed in quarantine, while the remaining 50% will be accepted.

reject

With "p=reject", unauthenticated emails are rejected. The reception percentage determines the proportion of unauthenticated emails that will be effectively rejected. For example "p=reject; pct=20" means that 20% of unauthenticated emails will be rejected, while the remaining 80% will be accepted.

Create a DMARC record

There are 2 ways to manage DMARC.

If you have a Mail Service with Infomaniak, the easiest way is to go to the Global Security tool to manage your DMARC security policy and reports:

But since the DMARC record is a type of DNS record, typically of type TXT, you can also manage it from the DNS zone of the domain name:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on DNS Zone in the left sidebar.
4. Click the button to add a record:
   
5. Click on the radio button DMARC to add a record.
6. Click on the Next button:
   
7. Leave (or add if necessary) the value _dmarc in the Source field.

8. The Target field must contain the parameters you wish to use, separated by ;:

   Tag Name	But	Example
   v	Protocol version	v=DMARC1
   pct	Percentage of messages subjected to filtering	pct=20
   ruf	Report URI for forensic reports	ruf=mailto:authfail@domain.xyz
   rua	Aggregate report URI	rua=mailto:aggrep@domain.xyz
   p	Policy for the organizational domain	p=quarantine
   sp	Policy for the subdomains of the organizational domain	sp=reject
   adkim	Alignment mode for DKIM	adkim=s
   aspf	Alignment mode for SPF	aspf=r

   This can result in for example v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@dmarcdomain.com (source)

9. Leave the default value for the TTL.
10. Click on the Save: button
    

This guide explains how to use the Newsletter tool with an external domain name (not managed at Infomaniak).

Prerequisites

• The domain name must belong to you.
• Synonym domains and their primary domain cannot be used to send newsletters.
  • It is possible to set up your synonyms as aliases.

Link an external domain

To access the management of Newsletter sending domains:

1. Click here to access your product management on the Infomaniak Manager (need help?).
2. If you already have a Newsletter, click on Add a domain:
   
   • Otherwise, click on Start for free:
     
3. Select Other domain from the dropdown menu before entering (or enter directly) the domain name with which you want to send newsletters:
   
4. Click the blue Approve button.
5. Add the TXT / CNAME / DKIM records that you will receive by email and that are visible on the interface to your registrar by clicking the button:
   

This guide details the specifics related to expirations of domain names when they are transferred from one registrar to another.

Preamble

• The expiration dates of domain names refer to the period during which the owner of a domain name has paid for the registration of that name.
• It is crucial for domain name owners to carefully monitor expiration dates and renew their registration on time to avoid any service interruption or having to pay additional recovery fees.
   

Transferring a domain to Infomaniak

When a domain is transferred to Infomaniak, the new expiration date (the date until which the domain will be registered, valid and functional) after transfer will be the date…

• … already existing before transfer + 365 days minimum.
   

Example:

• Domain name with expiration date 01/12/2025 before transfer…
• Transfer takes place on 01/10/2025 for example (no importance or impact)…
• The expiration date becomes 01/12/2026 after transfer to Infomaniak (1 year is added after the transfer).

Exceptions depending on the domain extensions

Transfer policies and their effects on expiration dates may vary depending on the domain extension. Each domain extension (such as .com, .net, .org, etc.) is managed by a specific regulatory entity, and these may have different rules regarding transfers and expiration dates.

The rule described in the previous chapter does not apply to certain extensions for which the new expiration date after transfer will be the date…

• … already existing before transfer, without incrementation or change: .CH.
• … from the transfer date + 365 days minimum: .BE and .DE.

Domain name ownership transfers can also affect expiration dates. When a domain name is transferred from one owner to another, the expiration date may sometimes be changed according to the registrar's policies.

This guide explains how to convert a free Web Starter offer to a more complete and enhanced paid offer, such as a Web Hosting shared or a Web Hosting on Cloud Server.

Preamble

• By purchasing a domain name from Infomaniak, you get 1 free email address as well as a basic Web space of 10 MB.
• In just a few clicks, it is possible to upgrade these offers to enjoy an enhanced experience.

Modify the Starter Offer - Basic Web Page

To upgrade this free offer:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on the action menu ⋮ located to the right of the relevant item.
3. Click on Modify the offer:
    
   
    
4. Follow the assistant to select the new type of hosting, pay to complete the offer change.

This guide details the specifics of the .be domain extension (for Belgium), including the administrative steps to transfer the management of a .be domain to Infomaniak.

Preamble

• As with other extensions, but particularly for .be it is very important to keep the WHOIS details of your domain name up to date to avoid any suspension by DNS.be!
• The terms "EPP", "AuthCode", "AuthInfo", "transfer code" and "authorization code" all refer to alphanumeric sequences specific to the domain whose main purpose is to verify the owner's authorization before a transfer between Registrars.

Transfer a .be domain to Infomaniak

.be domains are subject to a specific procedure for their authorization code (EPP code). If your previous registrar provided you with an authorization code, it is likely that this one is not valid. Indeed, to obtain the authorization code for a .be, you must either:

• click on "Get the authorization code" from the page that asks for the code,
• or go to dnsbelgium.be and request the authorization code (EPP code).

You should absolutely not try to transfer the domain multiple times in a row with the wrong code otherwise you will lock the domain as well as the transfer (Command failed; please contact support - domain locked‍) for several dozen hours without Infomaniak being able to do anything about it. You will have to wait before trying again with another code that must absolutely be the correct one.

Remove a .be from quarantine

Outside of a transfer period, and following outdated WHOIS information or suspicious use of your domain, it is possible that dnsbelgium.be the Belgian registry temporarily suspends this .be domain.

A usual WHOIS request will mention "NOT AVAILABLE" but you will get the actual status directly on their site, and in particular a date of availability before which you must absolutely follow one of the three possible outcomes:

1. resolve the issue with DNSBelgium and transfer the domain to Infomaniak,
2. resolve the issue with DNSBelgium and transfer the domain to another registrar (or to Infomaniak if the problem occurred with another registrar),
3. ignore the problem and wait for this availability date to try to re-register the domain (not recommended).

In the first two outcomes, you will need to obtain from DNSBelgium the end of quarantine as well as the authorization code. The operation of (re)registering the domain with Infomaniak is paid (around a hundred €/CHF) so it is important to keep the information up to date as the T&Cs specify.

Verification required

If you encounter this type of errors in the WHOIS, on your site, or via an e-mail report:

• Verification required for domain.be
• This site can’t be reached Check if there is a typo in domain.be. DNS_PROBE_FINISHED_NXDOMAIN
• We only activate this domain name once the contact details of the domain name holder have been validated

… check and update your domain name information so that it works again.

This guide presents the DNS Diagnostic tool, which allows you to check that the relationships between…

• DOMAIN NAME at Infomaniak
  
  and
   
• WEB HOSTING at Infomaniak

… are correct, so that Web traffic goes to the right place.

Introduction

• To check, the tool verifies the A, CNAME records, etc.
• You will thus be able to detect and correct certain web issues, especially if they are related to DNS (technical information that, broadly speaking, determines where such and such web traffic should be directed) by acting at the level of your domain.
• Automatic correction is only possible when the domain name is present in the same Organization as the product to which it must be attached.
  • If this is not the case, then the correction will need to be done manually.

Diagnose a DNS issue

To access the DNS diagnostic for your domain name:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Web in the left sidebar.
4. Click on DNS Diagnostic in the left sidebar:
   
   • If DNS issues are detected, a red display on the table indicates this:
     1. Correct each error individually by clicking on the action menu ⋮ located to the right of the concerned element…
     2. … or all errors at once…
     3. … or, if necessary and you are sure, ignore these warnings.

Refer to this other guide regarding the same automatic verification process but for Mail Services.

This guide details the administrative steps to take to transfer management of a domain .lu to Infomaniak.

Transfer a .lu domain

The transfer of a .lu domain does not require a transfer code; instead, a validation email will be sent to the domain administrator (listed in the WHOIS information) to validate the transfer to Infomaniak.

The domain owner then has 15 days to validate the transfer, otherwise the transfer will fail.

Once the request is validated, the transfer is almost immediate.

This guide details the procedure to modify the WHOIS details of the owner of domain names, which you can apply to an entire batch of domains in your Organization with Infomaniak.

Change details in bulk

To modify the WHOIS details of multiple domain names at once:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Select the domains whose owner needs to be modified using the checkboxes.
3. Click on Change owner at the bottom of the table:
   • Choose an existing contact record
   • or click on the button Add to create an entirely new contact record
4. Check your selection as well as any potential modification fees in the box on the right.
5. Click on Confirm.