From bfaff66bddcd6ad20b4d5626fe128ad40e7b1f7d Mon Sep 17 00:00:00 2001 From: MOZGIII Date: Sat, 5 Apr 2025 05:29:45 -0300 Subject: [PATCH] doc/cluster: mDNS setup for cluster access Signed-off-by: MOZGIII --- doc/.wordlist.txt | 1 + doc/howto/cluster_access.md | 8 ++++++++ 2 files changed, 9 insertions(+) diff --git a/doc/.wordlist.txt b/doc/.wordlist.txt index cd2664c9c4..ab81f98870 100644 --- a/doc/.wordlist.txt +++ b/doc/.wordlist.txt @@ -164,6 +164,7 @@ macOS macvlan Makefile manpages +mDNS Mbit MiB Mibit diff --git a/doc/howto/cluster_access.md b/doc/howto/cluster_access.md index 7c486c7825..349f01aa85 100644 --- a/doc/howto/cluster_access.md +++ b/doc/howto/cluster_access.md @@ -89,3 +89,11 @@ Traffic will then get balanced between all servers and as soon as a server goes ```{note} To minimize fallback delay, one can make use of BFD alongside BGP to get sub-1s fallback time. ``` + +### mDNS in L2 Network +If you are running in an L2 network (for instance, in a typical home network) you can use mDNS +and publish the same `.local` domain (something like `incus.local`) from multiple hosts. + +More than one host may send a reply in response to the multicast request, and the client +will receive multiple mDNS response packets - this way, at the cost of packet flood, +you get a simple way to ensure you reach *some* cluster node.