DNS/Netbox

Part of the DNS records are or will soon be automatically generated from data that resides in Netbox.

Infrastructure

• Netbox data is exported via Netbox#DNS.
• Netbox data is checked out on the authoritative DNS servers in /srv/git/netbox_dns_snippets.
• When compiling the gdnsd final zones, the Netbox data is copied into /etc/gdnsd/zones/netbox for later inclusion.
• In the actual zonefiles, within an $ORIGIN, the related snippet file is included using the $INCLUDE directive.

DNS records involved

• Management forward (A) and reverse (PTR) records for both the hostname (foo.mgmt.eqiad.wmnet) and the asset tag (wmf1234.mgmt.eqiad.wmnet)
• Primary IPv4 (A) and IPv6 (AAAA) and related reverse (PTR) records for the hostname (foo.eqiad.wmnet or foo.wikimedia.org)

Active

Management

• ulsfo

Primary IPs

• NONE

To be migrated

Management

• eqsin
• esams
• frack in codfw
• frack in eqiad
• codfw
• eqiad

Primary IPs

• ulsfo
• eqsin
• esams
• frack in codfw
• frack in eqiad
• codfw
• eqiad

Operations

Update generated records

To update the dynamically generated records based on the current Netbox data and deploy them to all the authoritative DNS servers, the sre.dns.netbox cookbook must be run. See also Cookbooks#Cookbook_Operations. For example:

 sudo cookbook sre.dns.netbox -t T12345 "Add newly racked cp hosts in eqiad"

Convert an hardcoded $ORIGIN to Netbox

This is an example patch to convert an hardcoded $ORIGIN to the dynamically generated data.

Transition

The records involved in the transition from hardcoded records to the Netbox driven ones and the order of the transition is listed above, see the To be migrated section.

Here's an example patch of the transition of management records for ulsfo.

What changes

The changes in procedure are outlined in the Server_Lifecycle/DNS_Transition page.