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?
@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 turned on my system and from my understanding most Linux desktops.
From my understanding the same problem will arise on windows if you turn on mDNS (which is off by default).
I will be happy to assist with anything, if needed.
Thank you.
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 .local tld for a long time, but you aren’t forced to use that default. You can change the domain suffix from the new-site defaults under “Preferences > New Site Defaults”
@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.
