Bug Summary By Arch wiki .local should be only used with mDNS protocol, and not in hosts file. Other TLDs work fine. avachi on Arch wiki Systemd-resolved mDNS Steps to reproduce Install localWP from AUR. create website with default environment .local domain is not resolved Environment Info Des…

Hey @kostiya – Welcome to the community forums! I read through the Avahi wiki and it sounds like this is only an issue if configuring this service for systems on your network AND you use Local to create sites with domains that end in .local – is that correct? Out of the box, Local has used the .lo…

Hi @kostiya Thank you for raising this. I’m not able to test at the moment but I can pass it along to the Devs to check. When you change your Router Mode to Localhost does that work as normal? Preferences>Advanced>Router Mode>Localhost

@Nick-B As I said, localwp works as expected with any other TLD or directly from localhost. I checked just in case and it works right as expected with localhost router mode. From reading documentation, it’s the expected behavior to reserve .local for mDNS. By default systemd-resolve mDNS is turn…

@ben.turner Yes, it’s correct. That’s is an easy fix. In my opinion if more Linux users complain, maybe it should be considered to change the default for Linux. Thank you.

.local TLD is not resolved when in hosts file if used on Arch based Linux

Bugs

Topic		Replies	Views
Server not found! Support	2	32	December 25, 2025
Can’t view local sites in browser: “localhost refused to connect” in Linux Manjaro Support linux-manjaro	1	462	October 7, 2023
[Arch Linux] ERR_NAME_NOT_RESOLVED / 404 Site Not Found Archived Support linux , linux-arch	5	366	March 28, 2024
.local domains not resolving osx Support mac	2	276	July 24, 2023
Local keeps resetting .local domain to localhost:10029 Uncategorized	1	652	March 19, 2020

.local TLD is not resolved when in hosts file if used on Arch based Linux

Related topics