Why does Apple Calendar fail in Automatic mode?
Published · 3 min read
TL;DR
Automatic asks only for your email and password, so the app has to work out where the server is. The CalDAV standard finds it through DNS records or a /.well-known/caldav address on your domain. If your domain publishes neither, choose Manual and type the server address.

When you add a CalDAV calendar to Apple Calendar on a Mac, the app offers three account types, and the first one, Automatic, can fail on a custom domain while Manual works with the same email and password. We ran into this ourselves: Automatic failed, Manual connected. The reason is not the password. Automatic has to find the calendar server on its own, and on many domains there is nothing for it to find.
This applies to any CalDAV provider on your own domain. Forum threads such as "Cannot create a CalDAV account on Synology Server" describe the same setup screen with different servers behind it.
What does Apple Calendar do in Automatic mode?
It asks for the least information and has to work out the rest. In Calendar, Add Account, Other CalDAV Account, the Account Type menu offers three options, which Apple describes this way. Automatic is for when "you just need to enter your email address and password." Manual is for when "you need to enter your user name, password, and the server address." Advanced adds the server path and port number, with options for SSL.
So Automatic gets an email address and nothing else about the server. From the address it has only the domain, the part after the @, to go on. Apple's guide does not say how Calendar uses it.
Why does it fail on my own domain?
Because the domain does not say where its calendar server is. The CalDAV standard for finding a server, RFC 6764, describes how a client should look it up from the domain. It first asks DNS for a service record named _caldavs._tcp on the domain, which points to the server and port for CalDAV over TLS, and it can fall back to _caldav._tcp. A separate TXT record can give the path on that server. Without a path, the client tries the address /.well-known/caldav. If there is no service record at all, the RFC says the client will need to prompt the user or use some other heuristic.
A custom domain usually serves your website and your mail, and none of these lookups are there unless someone added them. Our own domain is an example: on 16 November 2026, open.email had no _caldavs._tcp, _caldav._tcp or _carddavs._tcp records, and https://open.email/.well-known/caldav answered 404. A client following the standard finds nothing, and the app asks you for the server, which is what Manual and Advanced are for.
How do I connect in Manual mode?
Choose Manual, then enter your user name, your password and the server address your provider gives you. If Calendar still cannot connect, choose Advanced and add the server path and port, with SSL on. Your provider's setup instructions give all three values.
For OpenEmail (open.email, not OpenMail at openmail.sh), the server, path, port and the iPhone steps are in CalDAV and CardDAV settings.
How do I make Automatic work for my domain?
Publish the records the standard defines, so a client looking up your domain finds the server. That means a _caldavs._tcp SRV record pointing to your provider's calendar server and port, and, if the server needs a path, a TXT record with path= on the same name. The alternative the standard describes is to make https://yourdomain/.well-known/caldav redirect to the server. Your provider has to tell you the exact values, since they point at its servers. Apple does not document which of these lookups Calendar uses, so after publishing, add the account again with Automatic to check.
In OpenEmail, a domain's settings have an option, "Advertise CalDAV / CardDAV". It adds the calendar and contacts discovery records to the domain's DNS checklist, and you then add them at your DNS host like the other records. Without them, Manual works the same as before.
Does the same apply to contacts (CardDAV)?
Yes. Contacts use the same mechanism with their own names: a _carddavs._tcp service record and the address /.well-known/carddav. Publish them next to the calendar records, or use Manual with the server address, the same way as for Calendar.