Page MenuHomePhabricator

Move some of to Netbox
Open, LowPublic



I suggest:


nat.cloudgw         5M  IN A  <- Move to Netbox
wan.cloudgw         5M  IN A <- move to a FQDN (as it's a 208.80.153.x IP) -
virt.cloudgw        5M  IN A  <- Move to Netbox

; neutron virtual router cloudinstances2b-gw
cloudinstances2b-gw 5M  IN A  <- Move to Netbox

Also I don't think there is any reason for the 5M TTL? and the default 1H is fine?


; neutron virtual router cloudinstances2b-gw
cloudinstances2b-gw 5M  IN A  <- move to Netbox
; general outgoing/egress NAT address (routing_source_ip)
nat                 5M  IN A  <- move to Netbox

Same question for the TTL.

The ns/ns-recursor A/AAAA records are more complex.

Ideally there should be no services records pointing to host IPs. For example "" is a VIP hosted on hosts with different host IPs.
One of the advantage, is that decommissioning an host will not required moving DNS records. It's also less snowflakes in the infra.
As they point to prod IPs (208.80...) we could move them there, so they end in a FQDN.

But in the meantime, to make some progress it's fine to keep them as it, in the operations/dns file.

Event Timeline

ayounsi created this task.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Note that is delegated to designate directly from the RIPE, so the PTR is out of scope here.

@nskaggs I'm triaging the netbox tasks. Does WMCS has an opinion on that task or it's fine to proceed?

It is fine to proceed. Moreover, after the cloudgw project, some of this may be already on netbox anyway! see

The other topics you mentioned:

  • Regarding the service FQDNs. We don't need them. These FQDNs related to the edge network are mostly here to help us make sense of the network topology (traceroute, tcpdump, ping, etc) there aren't any services listening on them (not a DNS server definitely)
  • regarding that whole range should probably be replace with the cloud-specific range in codfw. That's for another task though.
  • regarding the DNS server addresses. You are right, an intermediate service FQDN might be in order here.