>The rfc says "Using '.local' as a private top-level domain conflicts with Multicast DNS and may cause problems for users.", as such I don't think we should be whitelisting .local, since it's suggested to not use it as a tld. I'm using the multicast DNS features on my Linux servers to make service discovery simpler on my local network. Some of those services have web frontends, like qBittorrent. I *never* mean to make these services accessible outside of multicast DNS and it works fine with it, but I actually ran into an annoying problem today trying to load up ruTorrent today - I typed in the URL today, and I ended up here: https://www.google.com/search?q=butter-server.local%3A9987 Oddly, none of this stuff have to do with ruTorrent - searches for .local domains aren't going to result in anything useful for *anyone*. If you have a better way of hosting my in network torrent client that doesn't use a .local domain, I am all ears - otherwise, this just looks like Firefox disrupting an already working use case for theoretical concerns that are actually not problems (Avahi *is* mDNS).
Bug 1634592 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>The rfc says "Using '.local' as a private top-level domain conflicts with Multicast DNS and may cause problems for users.", as such I don't think we should be whitelisting .local, since it's suggested to not use it as a tld. I'm using the multicast DNS features on my Linux servers to make service discovery simpler on my local network. Some of those services have web frontends, like qBittorrent. I *never* mean to make these services accessible outside of multicast DNS and it works fine with it, but I actually ran into an annoying problem today trying to load up ruTorrent today - I typed in the URL today, and I ended up here: https://www.google.com/search?q=butter-server.local%3A9987 Oddly, none of this stuff have to do with ruTorrent - searches for .local domains aren't going to result in anything useful for *anyone*. If you have a better way of hosting my in network torrent client that doesn't use a .local domain, I am all ears - otherwise, this just looks like Firefox disrupting an already working use case for theoretical concerns that are actually not problems (Avahi *is* mDNS). FWIW, the above string works fine in GNOME Web and Vivaldi on my machine.
>The rfc says "Using '.local' as a private top-level domain conflicts with Multicast DNS and may cause problems for users.", as such I don't think we should be whitelisting .local, since it's suggested to not use it as a tld. I'm using the multicast DNS features on my Linux servers to make service discovery simpler on my local network. Some of those services have web frontends, like qBittorrent. I *never* mean to make these services accessible outside of multicast DNS and it works fine with it, but I actually ran into an annoying problem today trying to load up ruTorrent today - I typed in the URL today, and I ended up here: https://www.google.com/search?q=butter-server.local%3A9987 Oddly, none of this stuff have to do with ruTorrent - searches for .local domains aren't going to result in anything useful for *anyone*. If you have a better way of hosting my in network torrent client that doesn't use a .local domain, I am all ears - otherwise, this just looks like Firefox disrupting an already working use case for theoretical concerns that are actually not problems (Avahi *is* mDNS). FWIW, the above string works fine in GNOME Web and Vivaldi on my machine -- it doesn't end up in a search.