Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Looks like someone made a conflict by misusing a reserved domain. The IETF reserves the ".local" TLD for IETF ZeroConf (Apple calls their IETF ZeroConf implementation "Bonjour"). That means it's only for local multicast DNS (mDNS). You should never set up a unicast DNS server as if ".local" is its TLD. If you need a fake TLD for a DNS server, don't use ".local", use ".test".
    – Spiff
    Commented Nov 3, 2023 at 12:14
  • The venerable old dig and nslookup commands are for troubleshooting traditional unicast DNS servers. They have never been updated for the ZeroConf era (mDNS, etc.), so they don't know that ".local" has been reserved. To be good troubleshooting tools, they have their own built-in unicast DNS resolvers and don't use the system's DNS resolver. To use the system's DNS resolver from the command line, use the dns-sd command.
    – Spiff
    Commented Nov 3, 2023 at 12:27
  • Thank you for your comment, I will give a try to 'dns -sd'. domain.local was for the example, I replace the local domain fqdn by domain.local, sorry for the misunderstanding. Thereal local domain is another one I don't want to publish here.
    – tasseb
    Commented Nov 3, 2023 at 12:54
  • There's no space in dns-sd. The hyphen is part of the command name. BTW "example.com" is a domain name reserved for examples.
    – Spiff
    Commented Nov 3, 2023 at 13:03