nat.cloudgw 5M IN A 18.104.22.168 <- Move to Netbox wan.cloudgw 5M IN A 22.214.171.124 <- move to a wikimedia.org FQDN (as it's a 208.80.153.x IP) - https://netbox.wikimedia.org/ipam/ip-addresses/7044/ virt.cloudgw 5M IN A 126.96.36.199 <- Move to Netbox ; neutron virtual router cloudinstances2b-gw cloudinstances2b-gw 5M IN A 188.8.131.52 <- 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 184.108.40.206 <- move to Netbox ; general outgoing/egress NAT address (routing_source_ip) nat 5M IN A 220.127.116.11 <- 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 "ns0.wikimedia.org" 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 .wikimedia.org FQDN.
But in the meantime, to make some progress it's fine to keep them as it, in the operations/dns file.