Custom-domain support depends on the local operator’s configuration and your invitation. TODO: confirm whether invited idler.me accounts may use custom domains.
If enabled, the usual AnonAddy flow is:
- Add the domain in the application.
- Publish the TXT record requested by the application to prove ownership.
- Point the domain’s MX records at the mail servers requested by the deployment.
- Add any SPF, DKIM, or other records required for sending from the domain.
- Wait for DNS propagation and complete the application’s verification.
A domain cannot normally deliver mail to two providers at once. If the domain already uses another mail provider, moving its MX records can interrupt that service. A subdomain such as mail.example.com can keep the main domain with its existing provider while aliases use the subdomain.
Do not publish or apply concrete record values without checking the records shown by the running instance.