This is documentation for the next version of Grafana Mimir documentation. For the latest stable release, go to the latest version.

Documentation Grafana Mimir Configure DNS service discovery

About Grafana Mimir DNS service discovery

Some clients in Grafana Mimir support service discovery via DNS to locate the addresses of backend servers to connect to. When using DNS service discovery, search domains are not supported. As a result, all domain names must be fully qualified. The following clients support service discovery via DNS:

• Memcached server addresses
  • -blocks-storage.bucket-store.chunks-cache.memcached.addresses
  • -blocks-storage.bucket-store.index-cache.memcached.addresses
  • -blocks-storage.bucket-store.metadata-cache.memcached.addresses
  • -query-frontend.results-cache.memcached.addresses
• Memberlist KV store
  • -memberlist.join
• Alertmanager URL configured in the ruler
  • -ruler.alertmanager-url

Supported discovery modes

DNS service discovery supports different discovery modes. You select a discovery mode by adding one of the following supported prefixes to the address:

• dns+
  The domain name after the prefix is looked up as an A/AAAA query. For example: dns+memcached.local:11211.
• dnssrv+
  The domain name after the prefix is looked up as a SRV query, and then each SRV record is resolved as an A/AAAA record. For example: dnssrv+_memcached._tcp.memcached.namespace.svc.cluster.local.
• dnssrvnoa+
  The domain name after the prefix is looked up as a SRV query, with no A/AAAA lookup made after that. For example: dnssrvnoa+_memcached._tcp.memcached.namespace.svc.cluster.local.

The Alertmanager URL must also contain the scheme. For example: dns+http://alermanager.local:8080.

If no prefix is provided, the provided IP or hostname is used without pre-resolving it.