Email Domain Setup Guide for Business Mail

A message sent from `name@yourcompany.lu` does more than look professional. It tells customers, suppliers and colleagues that your business owns its communications, manages its reputation and can be reached at a stable address. This email domain setup guide explains how to put that foundation in place properly, from choosing addresses to configuring DNS authentication that helps your messages arrive.

For a small business, email is often the first system to be set up and the one people rely on most. A missed message, a reply sent to spam, or a former employee’s inbox left active can become an operational problem quickly. The right setup is not complicated, but it does need careful decisions at the beginning.

Your domain is the part after the `@` symbol, such as `yourcompany.lu`. It should be registered in your organisation’s name and held in an account that the business controls, rather than in an employee’s personal account or with a former agency. Keep the renewal contact, billing contact and recovery details current. Losing access to a domain can affect not only email, but also your website and other online services.

A domain that matches your business name is usually the clearest choice. If your company trades across borders, you may use more than one domain, but avoid creating unnecessary confusion. One primary domain for everyday communications gives customers a simple, recognisable point of contact.

Before configuring email, decide who has authority over the domain’s DNS settings. DNS is the directory that tells the internet where your website, email and other services are located. The person making changes needs access to the domain control panel and should understand that a small typo can interrupt delivery.

Create addresses around roles as well as people. A personal address such as `firstname.surname@yourcompany.lu` makes accountability clear, while shared role addresses ensure the business remains reachable when someone is away or changes role.

For most organisations, addresses such as `info@`, `sales@`, `support@` and `accounts@` are practical starting points. They should not all become separate inboxes by default. Depending on the size of your team, a role address can forward to selected people, deliver to a shared mailbox, or work as an alias that lets authorised staff send from that address.

This is a trade-off between simplicity and control. Forwarding is quick to set up, but it can make ownership of replies harder to track. A shared mailbox gives better visibility and continuity, but needs clear rules about who monitors it. For enquiries that affect customers or payments, make one person or team explicitly responsible.

Avoid using one shared password for a generic address. Each user should sign in with their own credentials wherever possible. That makes access easier to remove when staff leave and provides a clearer record of activity.

Once your addresses are planned, connect the domain to your email hosting service. This normally involves adding several DNS records. These records are technical, but their purpose is straightforward: they tell other mail systems where to deliver messages and how to verify those sent from your domain.

MX, or Mail Exchange, records specify the servers that receive email for your domain. Your hosting provider supplies the exact hostnames and priorities. Enter them exactly as provided, and remove old MX records that belong to an email platform you no longer use.

A common mistake is adding new MX records without removing the previous ones. In that situation, some messages may reach the new service while others are sent elsewhere. Check the full DNS zone, not just the records you have added today.

DNS changes can take time to appear across the internet. This is often described as propagation. Plan changes outside your busiest period where possible, and do not cancel an existing service until you have confirmed that new messages are arriving reliably.

An SPF record states which systems are allowed to send email using your domain. It helps receiving servers distinguish genuine messages from unauthorised ones.

Your domain must have only one SPF record. If you send from your email host, a website contact form, an accounting platform or a newsletter service, all legitimate senders need to be included in that single record. Adding a second SPF entry does not strengthen protection - it can cause validation failures.

Start by listing every system that sends as your domain. This is also a useful housekeeping exercise. If nobody can explain why a sending service still has permission, remove it after confirming it is no longer needed.

DKIM adds a digital signature to each outgoing email. Receiving servers can use it to confirm that the message was authorised by your domain and was not changed in transit. Your email provider will generate a DKIM record, usually with a selector name and a long public key.

Copy this record carefully. Long keys are easy to truncate or format incorrectly. After publishing it, send a test message and confirm that DKIM passes. Authentication should be checked, not assumed.

DMARC brings SPF and DKIM together. It tells receiving servers what to do when a message claiming to be from your domain fails authentication, and it can send reports about attempted use of your domain.

Do not begin with the strictest rejection policy unless every legitimate sending source has been identified. Start with a monitoring policy, review the reports, then move towards quarantine or rejection once you are confident that valid messages pass alignment. This gradual approach reduces the risk of blocking your own invoices, booking confirmations or customer replies.

For businesses that are regularly impersonated, a properly configured DMARC policy is one of the most useful protective controls available. It will not stop every fraudulent message, but it makes it harder for unauthorised senders to use your domain convincingly.

DNS authentication protects your domain’s reputation. It does not protect an inbox when a password is stolen. Require strong, unique passwords and enable multi-factor authentication for every account that supports it, particularly administrator accounts.

Use a password manager rather than asking staff to remember complex passwords or reuse familiar ones. It is a practical improvement, not an inconvenience. A compromised mailbox can expose contracts, reset links, contact lists and internal conversations.

Set up a simple joiner and leaver process. When a new colleague starts, create only the access they need. When somebody leaves, disable sign-in promptly, remove forwarding rules, review shared mailbox access and decide who owns their ongoing correspondence. In many cases, keeping a former employee’s address as an alias for a limited period is sensible, but leaving the mailbox active indefinitely is not.

Also review auto-forwarding. Forwarding business email to personal accounts may be convenient, yet it creates a copy of company information outside your managed environment. If it is necessary for a specific role, define the reason, the destination and when it will be reviewed.

A successful login is not proof of a successful email deployment. Send messages to several major external providers and ask trusted contacts to reply. Check whether messages arrive in the inbox rather than the junk folder, whether display names appear correctly and whether attachments can be sent and received as expected.

Test from mobile and desktop devices if your team uses both. Confirm that calendar invitations, shared addresses and automatic replies behave as intended. For a business that uses a website form or cloud applications to send messages, test those sources too. They are often overlooked during an email migration.

Keep a record of your DNS values, administrator accounts, renewal dates and the services authorised to send email. This does not need to be a complicated document. It needs to be accurate, stored securely and available to more than one trusted person.

Some issues need a closer look: recurring delivery failures, SPF records that exceed lookup limits, emails sent by several third-party platforms, or a migration from a legacy server. The cheapest-looking route can become expensive when messages go missing or a domain reputation is damaged.

A local provider with control of its hosting and network infrastructure can make these problems easier to resolve because the people supporting you can inspect the actual service path. Visual Online supports organisations in Luxembourg with email hosting and the human technical assistance needed when configuration moves beyond a standard mailbox.

Your domain is part of how people find, trust and remember your business. Set it up with the same care you would give your phone number or front door: clearly owned, properly protected and always ready when someone needs to reach you.