1. Caddy version (
caddy version 2.4.6
a. System environment:
Mac OS Monterey
Firefox Developer Edition
c. Service/unit/compose file:
Paste full file contents here.
Make sure backticks stay on their own lines,
and the post looks nice in the preview pane.
d. My complete Caddyfile or JSON config:
3. The problem I’m having:
I have a
Caddyfile with the following config with the TLD configured as
.local but it isn’t resolving when I open it with the browser or if I try a
When I change
.localhost and then restart Caddy it works. Does anyone know why
.local isn’t working? Is it a Mac thing? Or a mis-configuration?
4. Error messages and/or full log output:
5. What I already tried:
6. Links to relevant resources:
I’m not sure how Mac resolves .local. Local might mean on the LAN to MacOS, not localhost, hence the two different TLDs. You might have to set up a DNS resolver to ensure that your .local domain resolves to the IP you expect.
.local is usually take up by Apple devices for multicast DNS. It’s not recommended to use
.local for web servers.
In computer networking, the multicast DNS (mDNS) protocol resolves hostnames to IP addresses within small networks that do not include a local name server. It is a zero-configuration service, using essentially the same programming interfaces, packet formats and operating semantics as unicast Domain Name Service (DNS). It was designed to work as either a stand-alone protocol or compatibly with standard DNS servers.
Multicast DNS was first proposed by Bill Woodcock and Bill Manning in the IETF in ...
The domain name .local is a special-use domain name reserved by the Internet Engineering Task Force (IETF) so that it may not be installed as a top-level domain in the Domain Name System (DNS) of the Internet. As such it is similar to the other special domain names, such as .localhost. However, .local has since been designated for use in link-local networking, in applications of multicast DNS (mDNS) and zero-configuration networking (zeroconf) so that DNS service may be established without The I...
Instead, you should use
.localhost if this is just something you’re reaching from the same machine, or
.home.arpa if you need it to work in your LAN.
.home.arpa won’t automatically resolve though, you’ll need to run a DNS server in your network that would resolve it and forward any other DNS queries to some publicly authoritative DNS server.
Thanks, we decided to use
.localhost instead and we are up and running
This topic was automatically closed after 30 days. New replies are no longer allowed.