https://coredns.io/tags/meshname/ Recent content in meshname on CoreDNS: DNS and Service Discovery Hugo -- gohugo.io en-us CoreDNS - All Rights Reserved Mon, 15 May 2023 12:00:00 +0000 https://coredns.io/explugins/meship/ Mon, 15 May 2023 12:00:00 +0000 https://coredns.io/explugins/meship/ Background Currently, a strict hierarchy is followed when resolving DNS names. It is centrally designed. To address the problem of centrality, there are several approaches. One of these approaches is Meshname. With a meship domain, the address to which the domain is to be resolved is encoded in the domain name. Thus, when a meship domain is to be resolved, the domain name is decoded first and then returned as a AAAA record. https://coredns.io/explugins/meshname/ Mon, 15 May 2023 12:00:00 +0000 https://coredns.io/explugins/meshname/ Background Currently, a strict hierarchy is followed when resolving DNS names. It is centrally designed. To address the problem of centrality, there are several approaches. One of these approaches is Meshname. With meshname, the IPv6 address of the authoritative name server responsible for the meshname domain is already encoded in the domain name. Thus, when a meshname domain is to be resolved, the first thing that is done is to decode the encoded authoritative DNS server from the domain.