Internal DNS

Internal DNS serves metadata-derived service discovery records, client-specific search paths, recursive forwarding, and DNS response caching for PastureStack environments.

PastureStack is an independent community effort to preserve, audit, and modernize the Rancher 1.6 ecosystem. It is not affiliated with or endorsed by Rancher Labs or SUSE.

Upstream: rancher/rancher-dns. This GitHub fork retains the upstream Git history, authorship, dates, and license notices unchanged; PastureStack maintenance is consolidated into one commit after the preserved upstream boundary.

Naming contract

• The internal service domain is pasture.internal.
• The metadata record is metadata.pasture.internal.
• Kubernetes service records remain under svc.cluster.local.
• Metadata-driven mode uses --metadata-url, which must include the API version, such as http://metadata/2016-07-29.
• Static metadata addresses use --metadata-answer.

The previous internal domain is intentionally not a public compatibility name. Upgrade tooling must perform an explicit, tested DNS cutover; see COMPATIBILITY.md.

Local checks

make test
make validate
make build

Linux integration tests require bats, dig, free local TCP/UDP port 15353, and controlled recursive DNS access:

make integration-test

Configuration file

JSON and YAML answer files may define client-specific and default records:

The Linux image reads and writes /etc/internal-dns/answers.json by default. Set PLATFORM_DNS_ANSWERS_FILE or pass an explicit --answers argument to use another path.

default:
  search:
    - pasture.internal
  recurse:
    - 1.1.1.1
  authorative:
    - pasture.internal
  a:
    api.example.pasture.internal.:
      answer:
        - 10.0.0.20

Security and license

Use only disposable DNS zones, metadata, and credentials in tests. See SECURITY.md, LICENSE, ORIGIN.md, and THIRD_PARTY_NOTICES.md.