Skip to content

dns.md

Latest commit

 

History

History
46 lines (39 loc) · 1.37 KB

dns.md

File metadata and controls

46 lines (39 loc) · 1.37 KB
Raw

DNS records

npmctl schema v2 supports provider-backed DNS records through dns_records. DNS records are declared with the same owner-scoped metadata contract as NPM resources, so adoption and pruning can remain explicit and owner-scoped when DNS apply support is enabled for a provider.

apiVersion: npmctl.com/v1
schemaVersion: 2
dns_records:
  - provider: namecheap
    zone: npmctl.com
    type: A
    name: "@"
    value: 172.16.0.10
    ttl: 300
    meta:
      managed_by: npmctl
      owner: npmctl-lander
      resource_id: dns.npmctl-com.root-a

DNS provider inspection is available through:

npmctl plugins list
npmctl dns providers
npmctl dns doctor --provider namecheap
npmctl dns zones --provider namecheap
npmctl dns records --provider namecheap --zone npmctl.com

DNS records also participate in plan and apply when the selected provider implements write support:

npmctl plan desired-state/dns.yaml --owner npmctl-lander
npmctl apply desired-state/dns.yaml --owner npmctl-lander

plan reports DNS creates, updates, deletes, and no-ops under a separate DNS summary. apply fails closed when a desired DNS mutation targets a read-only provider. Owner-scoped pruning removes only records that carry npmctl ownership metadata for the selected owner; unmanaged records in the same provider zone are preserved in the reconciled provider payload.