Page MenuHomeSoftware Heritage

Generate correct SOA records for
Closed, MigratedEdits Locked


Current contents of internal.s.o's SOA record:

$ dig @ soa

;; ANSWER SECTION: 86400 IN	SOA	localhost. root.localhost. 173 60 30 300 10

We can see the name of the master name server is "localhost."
This is operationally wrong, it should be "" or another A record pointing to a network-reachable IP address.

It is unclear if this really represents a problem or not but it feels wrong nevertheless.

Event Timeline

ftigeot triaged this task as Normal priority.Oct 9 2018, 11:36 AM
ftigeot created this task.

After investigating, the puppet module we're using doesn't allow editing the SOA after the zone has been created on the primary server. To bootstrap the zone, it uses a plain text file ($source argument to the bind::zone call).

Updating the bogus SOA fields for already created zones would be doable by editing the files in /var/cache/bind/ on pergamon, and reloading the zones with rndc reload

olasd claimed this task.

I've manually fixed the SOAs with the following command:

for zone in 100 101 {200..207}; do (echo update add $ 86400 IN SOA 182 60 30 300 10; echo send) | sudo nsupdate -k /etc/bind/keys/local-update; done

182 is a serial that was above the current serial for all zones.