Knowledge base

This guide explains how to optimize a website hosted on a Web Hosting plan to make it faster and provide a smooth browsing experience for all your visitors, regardless of their connection speed.

The role of the hosting provider

1. Your hosting server is operating normally and has not experienced any incidents in the last 48 hours.
2. The network infrastructure has not experienced any disruptions during the same period.

The role of the website owner and webmaster

Infomaniak does not intervene in the content of the servers or in the development of websites. The creation and maintenance of a website are distinct professions, although they use the tools and services provided by the hosting provider.

Analyze the cause of slowdowns

Here are the steps to take if you notice slowdowns on your website:

1. Apply the Google PageSpeed Insights recommendations. These points relate to the website design and not the server configuration. Consult this other guide if the test recommends enabling resource compression.
2. If slowness is observed from abroad, activate DNS Fast Anycast.
3. Install a caching system to reduce redundant database access and speed up page loading.
4. Consider using a CDN.
5. Test the server response time or TTFB.
6. Scan your hosting to detect any viruses.
7. Regularly purge your databases by deleting unnecessary entries.
8. Use the latest version of PHP compatible with your website or CMS.
9. Avoid images, counters, or media hosted on external servers: if they are unavailable, your site will appear slow.
10. Disable unnecessary or resource-intensive WordPress extensions.
11. Keep your CMS and web applications updated regularly.
12. Limit the impact of overly aggressive indexing bots by configuring a Crawl-delay.
13. Analyze the error logs: correcting errors generated by your site improves its performance.
14. Review the slow logs to identify SQL queries that take more than 5 seconds to execute and optimize them (optimization examples).
15. Add a server-side cache engine such as Memcached (available only on Cloud servers).
16. Increase the max_children value (only on Cloud servers).

If the problem persists

If you or your webmaster cannot identify the cause of the slowdown, contact Infomaniak support in writing, providing the following information:

1. Name of the hosted website.
2. Precise dates and times when slowdowns occurred.
3. Name of the database or FTP account potentially involved.
4. Your public IP address during the tests (visible on https://www.infomaniak.com/ip).
5. Type of slowdown (display, FTP transfers, etc.).
6. Indicate whether you normally access the Infomaniak website during these episodes.
7. Complete result of a traceroute to 84.16.66.66.
8. Result of a speed test on speedtest.net, selecting Infomaniak as the destination server.

If your needs evolve

If shared hosting is no longer sufficient, consider switching to a Cloud Server. Your website can be easily migrated to benefit from dedicated resources and advanced caching technologies.

This guide helps you troubleshoot various issues related to setting up and using a DMARC policy with your email service.

Refer to this other guide if you encounter a DMARC problem specifically when using Google services.

DMARC error or rejection...

...during a redirection, even though the initial destination address received the message (SPF error)

Email redirection without SRS generating an SPF error

Imagine that you have configured an email redirection from the address "user@example2.com" to the address "user@yourdomain3.com", without using the SRS mechanism. When a message is sent to "user@example2.com", it is received by the first email server and then automatically forwarded to "user@yourdomain3.com". Example:

• sender: john.doe@gmahoo1.com
• initial recipient: user@example2.com
• final destination: user@yourdomain3.com

In simplified terms: when John sends an email to "user@example2.com", the "example2.com" email server redirects it to "user@yourdomain3.com". The destination server therefore receives the message from the "example2.com" servers, while the sender's envelope address still indicates "john.doe@gmahoo1.com".

In detail: during the redirection, the recipient's envelope address is replaced with "user@yourdomain3.com", but the sender's envelope address remains "john.doe@gmahoo1.com". The sender's address visible in the message also remains unchanged.

The SPF check may then fail because the "example2.com" servers are not normally authorized by the SPF record of "gmahoo1.com" to send messages for that domain.

An SPF error, however, does not always result in a DMARC failure. DMARC only fails if no valid SPF or DKIM mechanism is aligned with the domain of the sender's visible address. If the original DKIM signature is missing, invalid, or not aligned, the DMARC policy of the sending domain may then cause the message to be quarantined or rejected.

To prevent SPF from failing solely due to redirection, the provider performing the redirection must support the SRS mechanism.

How redirections work at Infomaniak

When an email received by an Infomaniak address is redirected to another address, Infomaniak uses SRS to rewrite the sender's envelope address. The sender's address visible to the recipient remains unchanged.

This rewriting allows the destination server to verify that the Infomaniak server performing the redirection is authorized to use the new envelope address. SRS does not modify the original DKIM signature and does not, on its own, guarantee DMARC validation. In the context of a redirection, DMARC can be validated, in particular, if the original DKIM signature remains valid and aligned.

...related to an incorrect DNS entry

The DMARC record must be published as a single TXT record on the "_dmarc" subdomain of the domain in question.

Malformed DMARC Record: if the DMARC record is not correctly formatted, it may be considered invalid. Check the syntax, semicolons, tags used, and their values.

Invalid DMARC Policy: the value of the main "p" tag must be "none", "quarantine", or "reject". Any other value renders the DMARC policy invalid.

Multiple DMARC records: a domain should only have one TXT DMARC record. If multiple records are published on the "_dmarc" subdomain, the configuration is considered invalid, and the policy cannot be applied correctly.

Combine all necessary DMARC settings into a single TXT record.

Check your current DMARC entry using a dedicated tool, such as the ones below:

• https://dmarcadvisor.com/dmarc-check
• https://mxtoolbox.com/dmarc.aspx

...related to an email that fails to validate any aligned SPF or DKIM mechanism

DMARC does not require both SPF and DKIM to be valid. DMARC verification succeeds as long as at least one of these two mechanisms is valid and aligned with the sender's address domain.

A DMARC error or rejection can therefore occur when neither SPF nor DKIM validates a domain aligned with the sender's domain.

This can happen, for example, if you send an email with your Infomaniak address using the SMTP server of another provider. The server used may not be authorized by your domain's SPF record and may not apply a valid DKIM signature for that same domain.

To resolve this issue:

• Check the overall security of the Mail Service,
• use Infomaniak's SMTP servers to send messages from an Infomaniak address,
• if you are using an external sending service, configure your domain with that provider so that it properly supports SPF, DKIM, and their DMARC alignment.

Messages from a newly created domain are arriving in the spam folder

This behavior does not necessarily indicate a DMARC error. A newly created domain has little or no sending history, and its reputation is therefore not yet established with the various email providers.

Start by sending a small volume of legitimate messages to consenting recipients, then gradually increase the number of sends. Also, make sure that SPF, DKIM, and DMARC are configured correctly and avoid sudden or large-scale sends.

Sending messages to yourself can help test the configuration and mark a message as legitimate in the recipient's inbox. However, this is not enough to establish a general reputation with other email providers.

Successful SPF, DKIM, and DMARC checks do not guarantee that messages will be delivered to the inbox. Providers also take into account the reputation of the domain and sending servers, the volume of messages, their content, and the recipients' reactions.

I'm sending an email from my Infomaniak address and I'm receiving a "Reject DMARC" error message.

To resolve this issue:

• Check the overall security of the Mail Service,
• perform a test send from the Webmail mail.infomaniak.com,
• check the server settings of the software or email client, including the SMTP server used and the authentication of the sending address.

If the message is sent correctly from the Webmail, the problem is likely due to the configuration of the email software or the external SMTP server used for sending.

I'm sending an email from an external address (Microsoft, Google, Yahoo, Orange, etc.) and Infomaniak rejects it with a DMARC error.

The message probably does not comply with the DMARC policy published by the sender's domain. This may mean that SPF and DKIM have failed or that they are not aligned with the visible sender address.

To resolve this issue:

• Check with the sending address provider that messages are being sent in accordance with their recommendations.
• Forward the complete error message to the sending domain provider or administrator so they can check the SPF, DKIM, and DMARC configurations.

I want to receive an email on my Infomaniak address, but the sender is receiving a DMARC error

The message was blocked because it did not comply with the DMARC policy published by the sender's domain. The configuration of the recipient Infomaniak account does not allow for correcting an authentication error originating from the sender's domain.

To resolve this issue:

• Ask the sender to forward the complete error message to their email provider or domain administrator so that the SPF, DKIM, and DMARC configurations can be checked.
• If the Infomaniak address forwards messages to another address, also check at which stage of the redirection the rejection is generated.

This guide explains how to configure DNSSEC with Cloudflare for a domain registered with Infomaniak.

Prerequisites

• The domain's DNS zone must be managed by Cloudflare.

Configure DNSSEC in Cloudflare

To do this:

1. Click here to access the Cloudflare console.
2. Go to the DNS tab.
3. Click on Enable DNSSEC.
4. Keep the information you obtained handy:
   
   (see points 8 & 10 below)
   1. The information under a‍ will go under HASH
   2. The information under b‍‍ will go under HASH TYPE
   3. The information under c‍‍ will go under ALGORITHM
   4. The information under d‍‍ will go under KEY
5. Click here to access the domain management section in your Infomaniak Manager (❓: help).
6. Click on the name of the domain in question.
7. Enable DNSSEC from the Dashboard:
   
8. In the window that appears, enter the requested information using the data provided by Cloudflare (see point 4 above):
   1. Hash = Digest
   2. Hash Type = Digest Type
   3. Algorithm = Algorithm
   4. Key = Key Tag
9. Click on Activate:
   
10. In the case of a domain with an extension .eu, the necessary information may be significantly different (see point 4 above):
    • The information under FLAGS should be entered under FLAGS
    • The information under PUBLIC KEY should be entered under PUBLIC KEY

This guide explains how to link a domain name to an Infomaniak Mail Service.

If the domain name is located…

… with Infomaniak, same Organization

If your domain name is registered with Infomaniak and is in the same user account or Organization as your email, then there is nothing to do.

• Consult this other guide to check for and correct any configuration errors.

… with Infomaniak, different organization

If your domain name is registered with Infomaniak but in a different user account or Organization, then:

• Edit its DNS zone (❓: help) by specifying Infomaniak's MX (❓: help) + SPF (❓: help) & DKIM (❓: help).
  • Any DNS addition/modification may take up to 48 hours to propagate (❓: help).

OU

• Move it (❓: help) within the same Organization.

… with Infomaniak using external DNS

If your domain name uses DNS records that are not Infomaniak's, then:

• Edit the current DNS zone where it is hosted (if necessary, consult the help documentation of the provider in question) and specify Infomaniak's MX record (❓: help) + SPF (❓: help) & DKIM (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).

OU

• Change your current DNS settings and select the option to use Infomaniak's DNS servers.
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).
• Refer to this other guide to check and correct any potential configuration errors.

… or with external DNS servers

If your domain name uses DNS servers that are not Infomaniak's, then:

• Edit the current DNS zone where it is located (if necessary, consult the provider's help documentation) and specify the MX record (❓: help) for Infomaniak, as well as SPF (❓: help) and DKIM (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).

OU

• Change the current DNS servers (if necessary, consult the provider's help documentation) to use Infomaniak's DNS servers; this requires having a DNS zone with Infomaniak (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).
• This DNS zone with Infomaniak will be configured correctly, but please refer to this other guide to check for and correct any potential configuration errors.

… elsewhere, but you are moving it here

If your domain name is registered with another registrar and you would like to transfer it to the same location as your Infomaniak email, then:

• Transfer the domain name (❓: help) to Infomaniak (it will be configured correctly, but please refer to this other guide to check for and correct any potential configuration errors).

Alternatively, consider ordering a new domain name (❓: help) if necessary.

This guide explains how to link a domain name to an Infomaniak Web Hosting.

Where is your domain name located?…

… With Infomaniak, even for Organizations

If your domain name is registered with Infomaniak and is in the same user account or organization as your email, then there is nothing to do.

• Consult this other guide to check for and correct any configuration errors.

… At Infomaniak, Different Organization

If your domain name is registered with Infomaniak but in a different user account or Organization, then:

• Edit its DNS zone (❓: help) by specifying the website's IP address (❓: help) as an A record (❓: help).
  • Any DNS addition/modification may take up to 48 hours to propagate (❓: help).

OU

• Move it (❓: help) within the same Organization.

… With Infomaniak and external DNS

If your domain name uses DNS servers that are not Infomaniak's, then:

• Edit the current DNS zone where it is hosted (if necessary, consult the help documentation of the provider in question) and specify the IP address of the website (❓: help) as an A record (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).

OU

• Change your current DNS settings and select the option to use Infomaniak's DNS servers.
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).
• Refer to this other guide to check and correct any potential configuration errors.

… Elsewhere with external DNS

If your domain name uses DNS servers that are not Infomaniak's, then:

• Edit the current DNS zone directly (if necessary, consult the relevant provider's help documentation) by specifying the website's IP address in the form of an A record (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).

OU

• Change the current DNS settings (if necessary, consult the relevant provider's help documentation) by specifying Infomaniak's DNS servers (this requires having a DNS zone with Infomaniak (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).
• This DNS zone with Infomaniak will be configured correctly, but please refer to this other guide to check for and correct any potential configuration errors.

… Elsewhere, but you are migrating it here

If your domain name is registered with another registrar and you want to transfer it to the same location as your website on Infomaniak, then:

• Transfer the domain name (❓: help) to Infomaniak (it will be configured correctly, but please refer to this other guide to check and correct any potential configuration errors).
• If the domain name is intended to be an alias for your main website, you need to add the alias to your website (❓: help).

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

Prerequisites

• Own a domain name with Infomaniak or at least a DNS zone.
• Understand:
  • how a domain and a DNS zone work (❓: help) before modifying the latter,
  • that the DNS zone presented here is valid and used only if the name servers are those of Infomaniak (❓: help),
  • that any DNS addition/modification may take up to 48 hours to propagate (❓: help).

Setting up a zone delegation

To do this:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on DNS Zone in the left-hand menu.
4. Click on the Advanced View tab.
5. Click on the + button:
   
6. Enter the desired subdomain (e.g., test to obtain test.domain.xyz)
7. You can now edit the DNS zone of the delegated subdomain.

This guide explains how to link a domain name to any kSuite offer Infomaniak.

Manage the kSuite domain

To manage your domains, start by logging in with your credentials (user account with the necessary permissions for the relevant product):

1. Click here to access your kSuite management.
   • If nothing is displayed after logging in, you may not be in the Organization to which your kSuite is linked (❓: help).
2. If a domain is already linked, you can manage it by clicking on the action menu ⋮ to the right of the kSuite name, then Manage domains:
   
3. If no domain is yet linked, you can add one by clicking on the button:
   
4. Click the button to add a domain:
   
5. Choose the domain to associate from among those in your Organization (still available, i.e., not associated with any service) or enter an external domain name:
   
   • Depending on the status of your domain (also see the information below), you may need to perform some preliminary steps…
     
   • … or even purchase a domain if necessary:
     

If the domain name is located…

…with Infomaniak, within the same Organization

If your domain name is registered with Infomaniak and is in the same user account or Organization as your email, then there is nothing to do.

Simply add it to your kSuite:

The domain will then be added and visible on the dashboard:

• Refer to this other guide to check and correct any potential configuration errors.

... with Infomaniak, even if you already have an Organization and it's linked to a Mail service or kDrive

No problem, you can convert your existing products into kSuite (❓: help).

… with Infomaniak, Different Organization

If your domain name is registered with Infomaniak but in a different user account or Organization, then:

• Edit its DNS zone (❓: help) by specifying the Infomaniak MX record (❓: help) + SPF (❓: help) & DKIM (❓: help).
  • Any DNS addition/modification may take up to 48 hours to propagate (❓: help).

OU

• Move it within the same Organization (❓: help).

Generally, a message will notify you of this situation:

… and the technical information, which you should enter where the domain is located, will be provided:

… with Infomaniak using external DNS

If your domain name uses DNS servers other than Infomaniak's, then:

• Edit its current DNS zone where it is hosted (if necessary, consult the documentation provided by your current provider) and specify Infomaniak's MX record (❓: help) + SPF (❓: help) & DKIM (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).

OU

• Change your current DNS settings and select the option to use Infomaniak's DNS servers.
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).
• Refer to this other guide to check and correct any potential configuration errors.

You will be notified (see the images above).

… elsewhere, with external DNS

If your domain name is registered with another registrar and uses DNS servers that are not Infomaniak's, then:

• Edit its current DNS zone where it is hosted (if necessary, consult the provider's help documentation) and specify Infomaniak's MX record (❓: help) + SPF (❓: help) & DKIM (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).

OU

• Change your current DNS settings (if necessary, consult the documentation provided by your provider) and specify Infomaniak's DNS servers; this requires having a DNS zone with Infomaniak (❓: help).
  • Any DNS addition or modification may take up to 48 hours to propagate (❓: help).
• This DNS zone with Infomaniak will be configured correctly, but please refer to this other guide to check for and correct any potential configuration errors.

You will be notified (see the images above).

… elsewhere, but you bring it back

If your domain name is registered with another registrar and you want to transfer it to the same location as your Infomaniak email, then:

• Transfer the domain name (❓: help) to Infomaniak (it will be configured correctly, but please refer to this other guide to check for and correct any potential configuration errors).

Alternatively, consider ordering a new domain name (❓: help).

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

Introduction

• 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: see this other guide for an example of adding a TXT record to authenticate a domain).

Modify the DNS zone

To manage this type of record in a DNS zone:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on DNS Zone in the left-hand menu.
4. Click the button to add a record:
   
5. Click the TXT radio button to add a record.
6. Click the Next button:
   
7. Enter the TXT values required for your DNS zone.
8. Leave the default value for the TTL.
9. Click on the Save button:
   

This guide explains how to access a Fritzbox connected to the internet with a dynamic IP address via a domain name.

Prerequisites

• Have a device that allows you to configure a custom dynamic DNS provider.
• A dynamic DNS must have been created for the domain in question via the Infomaniak Manager (❓: help).

Connecting a Fritz!Box to a domain name

To do this:

1. Open the Fritzbox management interface by enabling Advanced mode if necessary.
2. Go to Internet then Access Authorization.
3. Click on the Dynamic DNS tab:
   
   
4. Choose the provider: “Custom”.
5. Fill in the following fields:
   • Update URL (as displayed below, or replace ipaddr with ip6addr if you want Fritzbox to replace the "placeholder" with the IPv6 address instead of the IPv4 address): https://infomaniak.com/nic/update?system=dyndns&hostname=<domain>&myip=<ipaddr>
   • Domain name: the URL configured in the Manager when adding the Dynamic DNS (❓: help).
   • Username: the ID defined in the Manager when adding the Dynamic DNS (❓: help).
   • Password: the password defined in the Manager when adding the Dynamic DNS (❓: help).
6. Click Apply to finish.

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

Introduction

• This type of record indicates which services are available for a domain.
• They are often used for XMPP, LDAP protocols, or to configure Microsoft Office 365.

Modify the DNS zone

To manage this type of record in a DNS zone:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on DNS Zone in the left-hand menu.
4. Click the button to add a record:
   
5. Click the SRV radio button to add a record.
6. Click the Next button:
   
7. Enter the values for the SRV record required for your DNS zone (the ._tcp.domain… is already entered).
8. Leave the default value for the TTL.
9. Click the Save button:
   

Verify that the complete SRV record has been added correctly in the records table:

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

Introduction

• The DKIM (Domain Keys Identified Mail) protocol authenticates your emails with a unique digital signature.
• It guarantees that your messages have not been modified during their transmission and certifies the identity of the sender, thus preventing spoofing by spammers.
• DKIM isenabled by default for all Mail Services whose DNS zone is managed with Infomaniak.
• All your emails are automatically signed, whether they are sent from the Infomaniak Mail app or the email software/client of your choice.

Check DKIM registration

If you have a Mail service with Infomaniak, the easiest way is to go to the Global Security tool to easily check and correct certain problematic records.

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

Manually modify the DNS zone (not recommended)

To manage this type of record in a DNS zone:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on DNS Zone in the left-hand menu.
4. Click the button to add a record:
   
5. Click the DKIM radio button to add a record.
6. Click the Next button:
   
7. Enter the DKIM values required for your DNS zone.
8. Leave the default value for the TTL.
9. Click on the Save button:
   

Add multiple DKIM records

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

If you use multiple third-party email providers, such as the Odoo ERP, it is necessary to add a DKIM for Odoo in addition to the one for Infomaniak.

Use unique DKIM selectors to avoid conflicts with existing records.

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

Prerequisites

• Have a device that allows you to configure a custom dynamic DNS provider.
• A dynamic DNS must have been created for the domain in question via the Infomaniak Manager (❓: help).

Linking a Sunrise Internet Box to a domain name

There are different models of Sunrise Internet Box (❓: help). Here is an example:

1. Log in to the Sunrise Box administration interface (e.g., http://192.168.1.1).
2. Enable expert mode (button in the top right corner).
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:
   • Hostname: the URL configured in the Manager when adding the Dynamic DNS (❓: help).
   • Username: the ID defined in the Manager when adding the Dynamic DNS (❓: help).
   • Password: the password defined in the Manager when adding the Dynamic DNS (❓: help).
8. Below, fill in the following fields:
   
   • Server: infomaniak.com
   • Port: 443
   • Request (copy and 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

The same principle applies to a 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 (such as Zyxel USG Flex or ax7501-B1, for example), fill in the fields using the data below:

1. Enable DDNS Profile: activate
2. DDNS Type: User custom
3. HTTPS: enable
4. Domain name: the URL configured in the Manager when adding the Dynamic DNS (❓: help).
5. Username: the identifier defined in the Manager when adding the Dynamic DNS (❓: help).
6. Password: the password defined in the Manager when adding the Dynamic DNS (❓: help).
7. Primary Binding Address > Interface : any
8. Backup Binding Address > Interface : none
9. DYNDNS Server: infomaniak.com
10. URL (copy and 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 explains how to access your Swisscom Internet Box, which is connected to the internet with a dynamic IP address, via a domain name.

Prerequisites

• Have a device that allows you to configure a custom dynamic DNS provider.
• A dynamic DNS must have been created for the domain in question via the Infomaniak Manager (❓: help).

Link your Swisscom Internet Box to a domain name

To do this:

1. Log in to the Swisscom Box administration interface (e.g., http://192.168.1.1).
2. Enable the expert view (toggle button at the bottom left).
3. Click on Network.
4. Click on the DynDNS tab.
5. Check the box to Enable DynDNS.
6. Select Infomaniak from the dropdown menu.
7. Fill in the following fields:
   • Hostname: the URL configured in the Manager when adding the Dynamic DNS (❓: help).
   • Username: the ID defined in the Manager when adding the Dynamic DNS (❓: help).
   • Password: the password defined in the Manager when adding the Dynamic DNS (❓: help).

If the box indicates that port forwarding is not possible because you do not have a public IP address, contact Swisscom to have them disable the CGnat (❓: help).

You have reached this page because a web redirection on your domain is incorrectly configured. Infomaniak is unable to identify the correct path for this redirection, so you are being redirected to this page to help you correct the situation.

DNS Zone Check

To restore the functionality of your redirection, you must first remove any traces of a previously misconfigured redirection:

1. Access your DNS zone (❓: help).
2. Delete the relevant records (refer to the list below) that correspond to your redirection.
3. Click on the action menu ⋮ to the right of the DNS entry in question and select Delete:
   
   • You probably won't find all the records listed, and that's perfectly normal.
   • Any DNS addition/modification may take up to 48 hours to propagate (❓: help).
4. Recreate the web redirection (❓: help).

List of records to check and delete

DNS records can be of the following types:

• A, which points to xx.xx.xx.xx (only numbers)
• AAAA records that point to an IP address xxxx:xxxx:x:x::x (a combination of numbers and letters).
• TXT records whose string resembles "(number)|(URL)"
  • for example, 1|infomaniak.com if your redirection points to infomaniak.com
• TXT where the string resembles "(letter)|(text)"
  • for example t|Text, d|Text or k|Text

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

Introduction

• An MX record tells mail servers to which server/provider to forward messages addressed to your domain name.
• Changes made in the Infomaniak Manager are only applied if the domain name uses the corresponding DNS zone.
• Any DNS addition/modification may take up to 48 hours to propagate (❓: help); during this period, some messages may still be routed according to the old configuration.

MX records for Infomaniak email

If your configuration requires manually adding the MX record to direct incoming messages to Infomaniak, enter the following values:

• Host / Source: leave this field blank to apply the record to the main domain
• Target: mta-gw.infomaniak.ch
• Priority: 5

The target must be entered as a hostname, without https://, without an email address, and without any additional path.

Variant specific to certain DNS interfaces

Some interfaces, notably Gandi's, require a period at the end of the target to indicate that it is a fully qualified domain name. In this case, enter:

mta-gw.infomaniak.ch.

Edit the DNS zone

To add an MX record to the DNS zone:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on DNS Zone in the left-hand menu.
4. Click on the button to add a record:
   
5. Select the type of MX record.
6. Click on the Next button:
   
7. Enter the requested values:
   • for the email of the main domain, leave the Host or Source field blank
   • enter the name of the email server provided by the provider in the Target field
   • enter the priority indicated by this provider
8. Keep the default value for TTL, unless your email provider indicates otherwise.
9. Click on the Save button:
   

Once saved, the MX record will appear in the DNS zone table:

Learn more

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

This guide details the different states in which a domain name can be.

Common statuses

"Active" or "OK"

The domain name is declared in the DNS, the domain name is active and unlocked. All administrative and/or technical operations are possible.

"Registrar-Lock / Registry-Lock" or "clientTransferProhibited"

The domain name is declared in the DNS. The domain name is active and locked to protect it, especially against unauthorized transfer requests.

Statuses requiring action or monitoring

"Registrar-Hold / Registry-Hold"

This status is applied when the domain has expired (not renewed). The only possible action is to renew it. Administrative and/or technical operations are not possible.

"RedemptionPeriod"

This status occurs if the domain has not been renewed. Please refer to this other guide if you are looking for information on this topic.

"PendingRestore"

This status appears during a restoration request. The registrar has 7 days to communicate all the necessary information to the registry for its restoration.

"PendingDelete"

This status follows the RedemptionPeriod status after 30 days if no restoration request has been made. The name will be deleted for a period of 15 days before reverting to the public domain.

In the case of a .fr domain extension

"Active"

The domain name is registered in the DNS (fully operational).

"Frozen"

The domain name is declared in the DNS, but no administrative or technical operations are possible. Possible causes: see article 6.1 of the AFNIC charter.

"Blocked"

The domain name is no longer declared in the DNS; it is no longer functional, and no administrative and/or technical operations are possible. Possible causes: see article 6.2 of the AFNIC charter.

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

Introduction

• This type of record allows you to point a domain name to a static IP address (usually a server), type A for IPv4 and AAAA for IPv6.
• This is the method generally used to redirect your domain name to the IP address of the web server hosting your website. Furthermore, this type of record is used automatically to link your domain name with your website if they are in the same location and within the same Infomaniak organization.
• You should only modify this type of record if you have a specific configuration to implement (e.g., pointing a subdomain to an external application).

Modify the DNS zone

To manage this type of record in a DNS zone:

1. Click here to access the domain management section in your Infomaniak Manager (❓: help).
2. Click on the name of the domain in question.
3. Click on DNS Zone in the left-hand menu.
4. Click the button to add a record:
   
5. Click the A or AAAA radio button to add a record.
6. Click on the Next button:
   
7. Enter the values required for your DNS zone.
8. Leave the default value for the TTL.
9. If necessary, you can request an adjustment to the AAAA record by activating the checkbox, which will allow you to specify an IPv6 address at the same time.
10. Click on the Save button:
    

This guide explains how to access a NAS Qnap connected to the internet with a dynamic IP address via a domain name.

Prerequisites

• Have a Qnap NAS connected to the internet with a dynamic IP address.
• A dynamic DNS must have been created on the domain in question from the Infomaniak Manager (❓: help).

Connect a Qnap NAS to a domain name

To do this:

1. Open the Qnap NAS management interface.
2. Go to Network & Virtual Switch:
   
3. Click on Add under Access Services > DDNS:
   
4. Enter the following information:
   
   • DDNS Server: Custom
   • Profile Name: Infomaniak (or whatever you want)
   • Hostname: the URL configured in the Manager when adding the Dynamic DNS (❓: help).
   • Username: the ID defined in the Manager when adding the Dynamic DNS (❓: help).
   • Password: the password defined in the Manager when adding the Dynamic DNS (❓: help).
   • URL: https://infomaniak.com/nic/update?hostname=%HOST%&myip=%IP%
5. Click on Apply.

From this point on, the dynamic IP address of your NAS will be automatically synchronized with your domain name.

This guide explains how to access your Jeedom home automation box (which is located behind a dynamic IP address provided by your ISP) using a domain name with Infomaniak via the free DynDNS option (❓: help).

Introduction

• The integration you install acts as a messenger: it continuously monitors the IP address of your local network.
• As soon as it detects that your internet provider has changed your IP, it instantly sends a signal to Infomaniak.
• Infomaniak then updates your domain name (e.g., jee.domain.xyz) so that it points to the new IP address.

Linking Jeedom to a domain name

Prerequisites

• You must have a Jeedom installation (e.g., on a Raspberry Pi 5) connected to the internet with a dynamic IP address.
• A dynamic DNS must have been created for the domain in question via the Infomaniak Manager (❓: help).

Then:

1. Install the official and free plugin on your Jeedom application from the Market (❓: help).
2. Activate the plugin as usual.
3. Configure a new device by selecting Infomaniak from the list of services:
   
   • Hostname: the URL configured in the Manager when adding the Dynamic DNS (❓: help).
   • Username: the ID defined in the Manager when adding the Dynamic DNS (❓: help).
   • Password: the password defined in the Manager when adding the Dynamic DNS (❓: help).

Jeedom will check the external IP address every 15 minutes. If it has changed, the DNS will be updated. This way, your domain name will continuously point to your home automation installation, even if your Internet Service Provider changes your public IP address.

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

Introduction

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

Add a DKIM on Cloudflare

Prerequisites

• Consult this other guide to learn how to display the DKIM record for your Infomaniak email account.
• Display the DKIM record so you can copy and paste it. Example:
  

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

1. Click here to access your Cloudflare account.
2. Select the domain in question.
3. In the DNS section, find and delete any NS records for "_domainkey" that point to Infomaniak.
4. Click the Add record button to open the input form.
5. Fill in the fields using the data obtained from the Infomaniak Manager, following the standard configuration for a DKIM record of type TXT:

Make sure the Proxy Status (cloud) is set to DNS Only (grayed out) for email authentication records.