https://bugs.kde.org/show_bug.cgi?id=456746
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |NOT A BUG
--- Comment #5 from Harald Sitter <sit...@kde.org> ---
I think you are suffering from a setup problem. Workgroup does more or less
nothing these days so it's configuration is moot.
The reason dolphin wants to access gallifrey.local is because the Samba on it
probably has multicast enabled (or rather, you haven't disabled it as per your
instructions) and we prefer DNS-SD multicast addresses over any other option.
Why that fails to resolve I couldn't possibly say but supposedly either your
client or server has a bad/incomplete mdns/dns-sd configuration.
gallifrey works because we will still resolve based on netbios names when
possible/requested and that would be the netbios name of your configuration
(assuming nmbd is running on the server anyway).
gallifrey.atlantis not erroring but also not showing anything is a bit odd and
I don't really have an explanation, it's a bit besides the point anyway because
as per your instructions you haven't really set up name resolution properly it
seems.
What I would suggest is not trying to use adhoc domains like you are trying to.
Either get a proper name server. Or just use the .local multicast domain. Or
drive your custom domain using mdns
(https://wiki.archlinux.org/title/avahi#Configuring_mDNS_for_custom_TLD).
Alternatively you could set up your server as proper samba DC but that is a
whole lot of work. I would very much suggest you simply rely on .local for name
resolution (or use a different suffix as in the arch wiki explanation), it's
supported on all Linuxes, OSX and Windows 10+
--
You are receiving this mail because:
You are watching all bug changes.
