This guide explains how a domain name and a DNS zone work.

Preamble

1. When you browse a website https://www.abc123.xyz for example, abc123.xyz is the domain name.
2. Each domain name has DNS (Domain Name System), which indicate where (with which provider, for example) the DNS zone is located.
3. The DNS zone then allows the management of various services related to the domain name to be entrusted to different providers.
   • For a unique domain name, it is possible, for example, to entrust:
     • web hosting to provider X (via the "A" type record)
     • and the Mail Service to provider Y (via the "MX" type record)

Domain name, DNS and DNS zone, then services

Who manages what?

1. Each domain name is reserved and managed by a registrar (registration office). For example, Infomaniak is a registrar, one of the cheapest in Switzerland.
2. The DNS of a domain name are configured with the registrar managing the domain name.
3. The DNS zone can be handled by the registrar or another provider.
4. Web hosting and the Mail Service can be handled by any host.

In the most complex case, it is therefore possible to have 1 different provider for the following services: domain name reservation and DNS management, DNS zone management, web hosting, Mail Service.

The following diagram summarizes these different possibilities with the involvement of different providers:

Infomaniak

As a registrar and host, Infomaniak can manage all these services. It's the simplest solution.

• In the case of Infomaniak, the DNS are generally of the form nsXX.infomaniak.com and nsXX.infomaniak.com (XX like 11 or 12 for example).
• You can modify the DNS of your domain name, as well as modify the "inside" of these DNS i.e. modify the DNS zone of a domain name.

And in these DNS zones, to redirect traffic to services, we distinguish:

• an MX record that allows you to point a domain name (domain.xyz for example) to a mail server.
• an A record that allows you to point a domain name (domain.xyz for example) or a subdomain (example.domain.xyz for example) to a web server that has a static IP address (otherwise you would have to constantly edit the A record to provide the new IP address - see this other guide on this subject)

Some possible situations

etc.

This guide explains the difference between the terms synonym and alias in the context of the Domain Name service offered by Infomaniak.

Domain synonym / domain alias

Domain names referred to as synonyms (i.e., domains that are entirely dependent on the main domain, without their own DNS configuration) and aliases (independent domains, with their own DNS configuration) can both serve as secondary domains associated with a main domain.

For example, the domains apple.xyz (alias) and banana.xyz (synonym) can redirect to a common main domain such as fruits.xyz.

Here is the technical distinction to remember:

• The synonym (also called a « linked domain » or « DNS mirror ») directly uses the DNS servers of the main domain. It has no DNS zone of its own.
• The alias (also called « autonomous redirected domain » or « DNS alias ») has its own DNS records (independent DNS zone), even though it points to the same hosting or services.

Learn more

• How to add a domain as an alias
• How to unlink an alias domain
• Understand the difference between domains and DNS zones

This guide explains how to transfer to Infomaniak data (Web, Mail, Domain, and even Cloud) currently hosted elsewhere. You remain the obvious owner of your data, without loss or interruption!

Specific guides

Click on the link corresponding to your current host:

• Swisscom: complete guide to migrate Web, Mail and domain name data

Guides for any other hoster

To retrieve any other data, follow the procedures below:

1. Import Web data (all PHP, HTML, etc. sites.)
   • For WordPress specifically, refer to this other guide…
      
2. Copy the Mail data (addresses and mailbox content, etc.) to kSuite or a simple Mail Service
    
3. Transfer the domain name (domain management, DNS zone, etc.)

You can also bring other types of data to the Infomaniak servers:

• Dropbox, Google Drive, etc. content: refer to this other guide
• Data on NAS Synology or QNAP: refer to this other guide

Why join Infomaniak?

By consolidating your domain names, websites, and email addresses with Infomaniak, you simplify the management of your invoices and services. Moreover, your domains will automatically link with your website and email address. You will therefore not need to manually configure the DNS of your domains with another registrar.

Learn more about Infomaniak

• Infomaniak, the Ethical Cloud
• Infomaniak's eco-responsible approach

DNS Fast Anycast replicates the DNS of your domain around the world to reduce latency and increase the availability of your websites.

Preamble

• Thanks to DNS Fast Anycast, the DNS of your domain are replicated within several Points of Presence (POP) around the world (list below).
• No matter where your visitors are, they are redirected to the nearest DNS server to them, which on average speeds up the access speed to your site by 34% (DNS resolution).
• Moreover, if one of your DNS servers were to be unavailable, the nearest server naturally takes over and your visitors can continue to access your site.
• The replication of your domain's DNS is automatic and no modification of your code is required.

Manage DNS Fast Anycast

Prerequisites

• DNS Fast Anycast is compatible with all websites, regardless of your host.
• All you need is a domain name managed by Infomaniak: transfer the management of your domain to Infomaniak if necessary
  • Refer to this other guide to manage external domains.

To access the DNS Fast Anycast option:

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 concerned.
3. Activate DNS Fast Anycast from the dashboard:
   

POP - 'Point of Presence'

By activating DNS Fast Anycast on your domain, your DNS will be automatically replicated in the following points of presence:

Network 1

New York, USA (2x)
Paris, France (2x)
Warsaw, Poland (2x)
Dublin, Ireland (2x)
Singapore (2x)
Johannesburg, South Africa
Stockholm, Sweden
Vienna, Austria (2x)
Frankfurt, Germany (2x)
London, United Kingdom
Dallas, USA
Los Angeles, USA (3x)
Amsterdam, Netherlands
Sydney, Australia
Sāo Paulo, Brazil
Miami, USA (2x)

Network 2

Hong Kong, China
San José, USA
Dallas, USA
Reston, USA
Chicago, USA
Seattle, USA
London, United Kingdom
Frankfurt, Germany
Amsterdam, Netherlands
Vienna, Austria
Toronto, Canada
Sydney, Australia
Sāo Paulo, Brazil
Johannesburg, South Africa
Miami, USA

The points of presence are distributed across two networks that are used randomly when one of your visitors accesses your website.

This guide explains how to restore backups of previous versions of your files and other web data from your Infomaniak hostings, and how to set up an effective backup policy if the backups automatically and freely provided do not meet your availability or security needs.

Web Hostings (Starter, Shared, Cloud Server)

Refer to these guides to restore automatic backups:

• of an entire hosting (FTP + MySQL),
• of specific files on the hosting,
• of specific databases,
• of a Web Application (Wordpress & Apps),
• of Cloud Server SSH crons.

Refer to these guides to backup and restore:

• a hosting with Swiss Backup and Acronis (simple),
• a hosting with Swiss Backup and Restic (advanced),
• WordPress with Swiss Backup,
• WordPress with an extension.

Also refer to https://faq.infomaniak.com/snapshot.

Hostings v1 (old 60 Go offer)

• View and/or download the automatic backup (versioning) of your data on your FTP space under /backups and /backup_mysql at the root of the domain (above /web).
• Restore this data.

Mail

• Restore messages from Infomaniak automatic backups.
• Restore contacts or calendar events.
• Save the current content of a mail account:
  • by downloading the current content locally,
  • by duplicating all current content to a backup box,
  • by copying future emails as they arrive to a backup box.

Domains / DNS Zones

• Restore deleted DNS records from Infomaniak automatic backups.
• Restore an expired domain in the redemption period.

This guide explains how to find and display DNS type information for any domain name registered with Infomaniak (or elsewhere).

Domain with Infomaniak

To access your domain names and view the DNS servers listed:

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 concerned.
3. Click on DNS Servers in the left sidebar:
   
   

WHOIS Search

To display the DNS information of another domain name, use a WHOIS service such as https://whois.infomaniak.com/ for example or https://who.is (be careful with ads on all these third-party services).

You will thus obtain a clear answer to the DNS situation of a domain name at a given time.

Often, DNS entries are displayed in pairs and start with ns... followed by numbers and the name of the registrar or host.

Thank you for entrusting the management of your domain names to Infomaniak.

This guide allows you to quickly use the essential functions of your new product.

Some important guides

Administrative

• Protect your personal information in the WHOIS
• Protect your domain from theft and loss
• Modify the domain name details
• Who owns a domain name?
• Use the free services (mail and Web 10 Mo) linked to a domain managed by Infomaniak
• Transfer another domain name to Infomaniak

Technical

• Edit the records (A, MX, Web, Mail, etc.) of a domain registered with Infomaniak to join, for example, a hosting service not managed by Infomaniak
• Modify the DNS servers
• Redirect traffic
• Configure DynDNS

• Link a domain name to another
• Unlink a domain alias from a domain name

• Link a domain name to the Mail Service
• Link an additional domain name to the Mail Service
• Unlink a domain linked to the Mail Service

• Link a domain name to an Infomaniak Web Hosting
• Link an additional domain name to a website
• Unlink a domain linked to the website

• Link a domain name to kSuite
• Link an additional domain name to kSuite

• Link a domain name to the Infomaniak Synology NAS
• Link a domain name to Wix
• Link a domain name to Site Creator
• Link a domain name to the Newsletter
• Link an Infomaniak domain name to an external service

Otherwise, find the desired topic among the rest of the FAQs.

Click here to share feedback or a suggestion about an Infomaniak product.

Thank you for trusting Infomaniak with the hosting of your website.

Preamble

• A web hosting is a storage space available on a computer, also called a "server", connected to the Internet and managed by a web host, Infomaniak.
• This storage space, made available to professionals and individuals, is used to install websites or other types of tools (CRM, extranet, intranet...) that need to be accessible via the Internet.
• These guides allow you to quickly use the essential functions of your new product, your web hosting, which can accommodate multiple websites.

Where to start?

1. Create a WordPress website
2. Build the site with Site Creator
3. Install a web application (ownCloud, Joomla, Typo3, Drupal, phpBB, Simple Machines Forum, Magento, Prestashop, ...)
4. Manage your FTP accounts/users
5. Manage and publish files on your hosting via FTP Manager
6. Manage your MySQL databases
7. Add a site or subdomain to your hosting (multisites/multi domains)
8. Link another domain name to an existing website (domain alias)
9. Preview your site even if your domain name does not yet point to Infomaniak's servers

IMPORTANT: the domain name...

A web hosting, to be visible to the public on the Internet, must be associated with a domain name!

Your domain name is not managed by Infomaniak? Or is it in a different Organization than that of your web hosting? Then refer to this other guide to configure the DNS or the "A records" in order to link the domain name to your web hosting.

In case of a problem

To resolve a problem, please consult the Web Hosting Knowledge Base before contacting Infomaniak support.

Click here to share a review or suggestion about an Infomaniak product.

This guide describes the meaning of TTL, an abbreviation for «Time To Live» as well as the principle of DNS propagation delays, important concepts in the operation of domain name-related services.

Preamble

• The TTL determines how long DNS information is cached before being updated.
• This directly influences the speed of DNS changes propagation across servers worldwide.
• Although reducing the TTL can speed up propagation, the behavior of ISPs and their caches can introduce additional delays.

The TTL (Time to Live)

The TTL (Time to Live) is a key parameter in managing DNS records. It represents the duration, expressed in seconds, during which DNS information can be cached before being updated. When a DNS server or an Internet Service Provider (ISP) queries a DNS zone, it temporarily stores the responses obtained to reduce the load on servers and speed up navigation for users.

For example, if the TTL is set to 24 hours (86400 seconds), the DNS information related to a domain will be cached and will not be updated for the entire duration, even if you have modified parameters such as the domain's IP address. This means that DNS changes will only take effect once this period has elapsed.

It is possible to speed up the application of changes by reducing the TTL before making updates. For example, lowering the TTL to one hour (3600 seconds) allows DNS servers to check the new information more quickly after a modification.

DNS propagation

The TTL is directly linked to the process of DNS propagation. DNS propagation refers to the time required for changes made to a DNS zone to be disseminated across all DNS servers worldwide. This delay depends not only on the configured TTL but also on how ISPs and other DNS servers manage their caches.

When you modify DNS records, DNS servers and ISPs must wait for the TTL delay to expire before retrieving the new information. Thus, the shorter the TTL, the faster the changes propagate across the network. However, some ISPs sometimes ignore the TTL duration and retain the information in cache for a longer period (e.g., 24 hours or more), which can slow down the propagation of DNS changes, even if you have configured a reduced TTL.

This guide concerns the configuration of the Infomaniak product Newsletter in the case where the domain name used to send your emails is not managed by Infomaniak.

Preamble

• For automatic use of the Newsletter tool, it is necessary to manage the domain name from which you send your newsletters (as well as its DNS zone) with Infomaniak.
• For example, if you send your newsletters from the address news@domain.xyz, the domain domain.xyz must be managed with Infomaniak.

Specific DNS configuration

To use the Newsletter tool with a domain not managed by Infomaniak, you will need to add specific entries to your DNS zone provided in your Manager:

Refer to this other guide to add the DNS entries mentioning ._domainkey making sure to choose the type DKIM first, then the subtype CNAME when adding the DKIM.

In case of outgoing domain transfer

If the domain name currently managed by Infomaniak (and corresponding to the Newsletter) is transferred to another registrar, the Newsletter tool will be deactivated within 30 days if no corresponding DNS modifications are made.

This guide explains how to modify the DNS (Name Servers) of a domain registered with Infomaniak.

Prerequisites

• Own 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 any DNS addition/modification may take up to 48 hours to propagate.

DNS Modification

To modify the DNS of a domain managed by Infomaniak and thus control the direction that web and mail traffic should take:

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 Servers from the left sidebar.
4. Click the blue button Edit DNS Servers:
   
5. If your website is hosted with Infomaniak, check Infomaniak Name Servers; otherwise, check Custom Name Servers:
   

Batch modification

To modify the DNS of multiple domain names in bulk:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Select the relevant domain names.
3. Click on ⋮ at the bottom of the screen if necessary.
4. Click on Edit DNS servers:
   

This guide shows you how to use the Newsletter tool provided by Infomaniak to create and send newsletters, i.e., recurring messages to multiple recipients.

Why use Newsletter instead of a Mail Service

A newsletter is a periodic communication tool sent by email to a specific group of subscribers. It generally aims to inform, share news, updates, or relevant content on a specific topic, and maintain a relationship with a targeted audience.

They can contain articles, announcements, promotions, links to recent content, upcoming events, and sometimes exclusive offers for subscribers. The main goal is to provide interesting and relevant content to engage and maintain the interest of subscribers.

Newsletter Infomaniak allows you to schedule and send newsletters to a list of email recipients who are waiting for your emails; you thus effectively and personally distribute email marketing campaigns and maintain regular and relevant communication with your customers and subscribers.

The features include creating templates, managing the subscriber list, analyzing performance, and none of this is directly possible with a traditional Mail Service. Moreover, the tool has its own interface, autonomous within your browser, completely separate from Mail Infomaniak and does not require a messaging application. This means that if you already have contacts to whom you wish to write with their consent, you will need to import them into the tool first.

Prerequisites

• Have a domain name on which you will activate the Newsletter:
  • Access to your DNS zone if the domain name is not with Infomaniak.
  • Create a new domain name if necessary.
• Have Newsletter credits to allow sending (1 credit = 1 newsletter sent to 1 subscriber).

Activate the Newsletter tool

To activate the Newsletter tool for the first time:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on START FOR FREE to subscribe to the Newsletter offer.
3. Enter the domain name that will be used (and that must belong to you - read the prerequisites above).
4. Click the blue button to Approve.
5. Start using the tool - or refer to this other guide if you encounter any issues or if additional configuration is requested on the screen.

Access the Newsletter tool

To access the Newsletter once activated:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on the domain name concerned in the table that appears:
   

Go further with the tool

• Import contacts
• Create and send a newsletter
• Newsletter credits
• Newsletter subscription form
• Double opt-in to avoid being marked as a spammer
• Resend a newsletter to specific types of subscribers
• Variables to personalize your content
• Use the Newsletter API

See all Newsletter FAQs ; click here to share feedback or a suggestion on an Infomaniak product.

This guide explains how to resolve issues that may occur with a Web Hosting if the latter has undergone modifications at the IP address level (for example, a server move) and your computer retains the old position in its DNS cache.

Flush the DNS cache...

When you visit a website, your computer stores a local association between the domain name and its IP address in the DNS cache. This speeds up the DNS resolution process for future visits to the same site, as the computer can avoid re-consulting the DNS servers to obtain the IP address.

By flushing the DNS cache, you force your computer to query the DNS servers again to obtain the latest up-to-date information on the IP addresses of the sites you visit.

... on Windows

Run the following command from a Terminal type application (command line interface, CLI / Command Line Interface) on your device. Example:

1. Open the Start menu.
2. Type cmd.
3. In the search results, click on Command Prompt.
4. Run the command ipconfig /flushdns.

... on macOS

Run the following command from a Terminal type application (command line interface, CLI / Command Line Interface) on your device:

• Run the command lookupd -flushcache (in case of failure: dscacheutil -flushcache).

... on Linux

Run the following command from a Terminal type application (command line interface, CLI / Command Line Interface) on your device:

• Run the command sudo systemctl restart nscd or sudo /etc/init.d/nscd restart to restart nscd.

This guide explains how to order a DNS zone from Infomaniak.

Preamble

• Having the DNS zone with Infomaniak is useful if your domain name is registered elsewhere (third-party provider/registrar) and you want to easily link this domain with Infomaniak products.
• Indeed, it is not enough to own a site domain.xyz with Infomaniak and to indicate the 2 DNS addresses of Infomaniak with the domain name registrar (if it is not Infomaniak) for the site to be displayed when you type domain.xyz in a browser.
• You must add a DNS zone in the same place as the hosting to make the site work easily.
• This will also be particularly useful if the service provider managing your domain name does not offer DNS zone management.

Order a DNS zone

To do this:

1. Click here to access the Infomaniak domain Shop.
2. Start a search with the name of the domain registered elsewhere.
3. Click on the action menu ⋮ located to the right of the result obtained.
4. Select Order a DNS zone:
   
5. Complete the purchase.
6. Once added to your Manager, the zone can be edited.

This guide explains how to add, modify, or delete specific entries (records of type A & AAAA, MX, TXT, etc.) within the DNS zone of a domain name registered with Infomaniak.

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.
  • The DNS zone presented here is valid and used only if the server names are those of Infomaniak.
  • Any DNS addition/modification can take up to 48 hours to propagate.

Add a record (simple mode)

To configure the services associated with the domain and allow the appropriate resolution of domain names to the corresponding resources (such as external websites, third-party mail servers, etc.):

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 concerned.
3. Click on DNS Zone in the left sidebar.
4. The entries currently in place are listed in the Simple Mode table:
    
   
    
5. Click the blue Add an entry button:
    
   
    
6. Choose the desired record type (records of type A & AAAA, MX, TXT, etc.)
7. Click on Next.
8. Complete the different fields according to your information:
   1. Under Source leave blank or specify any subdomain concerned.
   2. Under Target enter the information obtained from your external provider or any other useful indication.
   3. Leave the TTL indicated.
9. Save the addition made.

Modify an existing record

To modify an existing DNS record:

1. Follow points 1 to 4 above.
2. Click on the action menu ⋮ to the right of the record to be modified.
3. Click on Modify to access the editing page:
    
   
    
4. Proceed with the editing of the desired information and then save your changes.

Delete an existing record

To delete an existing DNS record:

1. Follow points 1 to 4 above.
2. Click on the action menu ⋮ to the right of the record to be modified.
3. Click on Delete and confirm the deletion:
    
   

DNS diagnostic

A tool available on your Manager allows you to easily correct certain problematic records. You can also use a free external service such as the one mentioned at the bottom of this other guide.

Expert mode

To edit the DNS zone in advanced (expert) mode, which in particular allows you to restore a previous version of the different records, refer to this other guide.

This guide explains how to generate and then automatically renew a wildcard certificate via DNS challenge using Certbot and the dns-infomaniak plugin.

1. Installing the Infomaniak DNS plugin

DNS plugins are not installed by default with Certbot. To correctly install certbot and the dns-infomaniak plugin, to avoid a possible error The requested dns-infomaniak plugin does not appear to be installed, refer to the official Certbot instructions and choose the correct Software → System and then consult the Wildcard tab.

2. Generate the wildcard certificate

From a Terminal, run the following Certbot command to manually generate the certificate:

certbot certonly --manual \
-d *.domain.tld \
--preferred-challenges dns-01 \
--server https://acme-v02.api.letsencrypt.org/directory

3. Create the TXT record

From the domain management of the Infomaniak Manager, create the requested TXT record for _acme_challenge.domain.tld.

4. Create the renewal configuration file

From a Terminal, create or edit the file: /etc/letsencrypt/renewal/domain.tld.conf. Example of recommended configuration:

cert = /etc/letsencrypt/live/domain.tld/cert.pem
privkey = /etc/letsencrypt/live/domain.tld/privkey.pem
chain = /etc/letsencrypt/live/domain.tld/chain.pem
fullchain = /etc/letsencrypt/live/domain.tld/fullchain.pem
[renewalparams]
authenticator = manual
manual_auth_hook = /root/infomaniak-auth.sh
manual_cleanup_hook = /root/infomaniak-clean.sh
server = https://acme-v02.api.letsencrypt.org/directory
pref_challs = dns-01
account = xxxxx
key_type = rsa

Some errors come from files automatically generated by Certbot containing obsolete or incorrect fields (version = ..., cert-path = ..., etc.). Always recreate the renewal file following the example above.

5. Create the infomaniak-auth.sh script

From the API management of the Infomaniak Manager, create an Infomaniak API token with the domain scope, which will replace XXXXXXX in the script below.

The file indicated in your configuration must absolutely match the real name of the script. Example: if you use infomaniak-auth.sh in the configuration, do not create infomaniak-auth-domain.xyz.sh.

From a Terminal, create the file /root/infomaniak-auth.sh without trailing tabs (they cause errors in Bash) with:

#!/bin/bash
INFOMANIAK_API_TOKEN="XXXXXXX"
# Ajout de l'enregistrement TXT via le plugin DNS Infomaniak
/usr/bin/certbot \
  --authenticator dns-infomaniak \
  --server https://acme-v02.api.letsencrypt.org/directory \
  -d "$CERTBOT_DOMAIN" \
  --agree-tos

The script must be made executable:

chmod +x /root/infomaniak-auth.sh

6. Create a cleanup script

Create the file /root/infomaniak-clean.sh

#!/bin/bash
# Optionnel : suppression de l'entrée DNS temporaire
exit 0

The script must be made executable:

chmod +x /root/infomaniak-clean.sh

7. Test the renewal

Before using a cron, always test with this command that will display any potential errors (script not found, incorrect file name, missing permissions, missing plugin, etc.):

certbot renew --dry-run

8. Configure a cron task

0 0 */30 * * /usr/bin/certbot renew --quiet --config /etc/letsencrypt/renewal/domain.tld.conf

Modify 30 days above according to the desired frequency. The cron will automatically use:

• the file domain.tld.conf
• the authentication script infomaniak-auth.sh
• the plugin dns-infomaniak

This guide explains how to modify in advanced (expert) mode specific entries (records of type A & AAAA, MX, TXT, etc.) within the DNS zone of a domain name registered with Infomaniak.

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 presented here is valid and used only if the name servers are those of Infomaniak…
  • that any DNS addition/modification can take up to 48 hours to propagate.

Modify an existing record

To configure the services associated with the domain and allow the appropriate resolution of domain names to the corresponding resources (such as external websites, third-party mail servers, etc.):

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 concerned.
3. Click on DNS Zone in the left sidebar
4. Click on Advanced View:
   
   • The syntax is accepted in BIND format.
5. Proceed with the editing of the desired information.
6. Save your changes:
   

Restore a DNS zone

Thanks to the Expert mode, you can use versioning to find a previous version of the DNS zone of your domain name and thus restore it as it was at a given time:

1. Once in the Advanced View tab (see above) click on Current Version to expand the menu containing previous dates.
2. Click on the desired date to get a preview of the changes.
3. Click on the blue Save button on the right to return to the selected version:
   
4. Click on the second drop-down menu if necessary to access the restoration of delegated subdomain configurations.

DNS Diagnostic

A tool available on your Manager allows you to easily correct certain problematic records.

This guide presents the Domain Status tool, which allows you to verify that the relationships between…

• DOMAIN NAME with Infomaniak
  
  and
   
• WEB HOSTING with Infomaniak

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

Preamble

• To verify, the tool checks 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, in short, 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 must be done manually.

Diagnose a DNS problem

To access the DNS diagnosis of 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 concerned.
3. Click on Web in the left sidebar (or on the possible indication to go directly to point 6):
   
4. Click on Domain Status in the left sidebar.
5. If DNS issues are detected, a display on the dashboard indicates it.
6. Correct all errors at once by clicking on the button:
   

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 presents the DNS Diagnostic tool, which allows you to check that the relationships between…

• DOMAIN NAME at Infomaniak
  
  and
   
• MAIL SERVICE at Infomaniak

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

Introduction

• To check, the tool verifies the MX, SPF, etc. records.
• You will thus be able to detect and correct certain Mail problems, especially if they are related to DNS (technical information that, broadly speaking, determines where such and such Mail 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 Domain Management 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 it:
     1. Correct each error individually by clicking the button to the right of the concerned element…
     2. … or all errors at once.

Refer to this other guide regarding the same automatic verification process but for Web Hosting.

And if necessary, familiarize yourself with the mail-related security diagnostic.