Page MenuHomePhabricator

Cloud: define relationship between domain, CIDR prefixes and netbox automation
Open, MediumPublic


This task is to define some potentially weird data status on the domain.

It might contains mixed data from inside the cloud realm and prod realm, not making it very clear where is the boundary regarding DNS data hosting and administration.


arturo@endurance:~ $ host domain name pointer
arturo@endurance:~ $ host domain name pointer domain name pointer domain name pointer domain name pointer domain name pointer

In the example above, the CIDR ( contains data from both operations/dns.git and designate @ eqiad1.

Additional context:

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
aborrero triaged this task as Medium priority.Oct 23 2020, 11:57 AM
aborrero moved this task from Inbox to Needs discussion on the cloud-services-team (Kanban) board.

I was able to discuss this with @faidon briefly. I'll summarize the discussion below.

Note, while this summary may feel authoritative or provide answers, that's not my intent. I would appreciate clarity that we've thought about the right questions this ticket is highlighting.

What's in scope for netbox automation?

  • cloudservices *hosts*, cloudcontrol, cloudvirt, etc. are servers in the production realm and use domains under .eqiad.wmnet, etc. and are in scope of the netbox automation project
  • cloudservices *VPS*, are in the "labs" realm, in separate domains, and out of scope for netbox automation. This includes

Where should DNS allocation of be?

  • Keep the entire address space in the "labs" realm, and DNS allocation should stay in realm as well accordingly

How should we handle

  • Have a separate service IP (not tied to a specific box), in the space, with matching A+PTRs under

And an open question; Are there potential mismatched records today? How is this intended to work?

$ host has address

$ host has address

$ dig -x 3599 IN	PTR