Page MenuHomeSoftware Heritage
Create Task
Maniphest T1253

Generate correct SOA records for internal.softwareheritage.org.
Closed, MigratedEdits Locked
Actions

Description

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

$ dig @192.168.100.29 internal.softwareheritage.org soa

;; ANSWER SECTION:
internal.softwareheritage.org. 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 "pergamon.internal.softwareheritage.org." 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.

Related Objects
Search...

Event Timeline

ftigeot triaged this task as Normal priority.Oct 9 2018, 11:36 AM
ftigeot created this task.
olasd added a comment.Oct 10 2018, 11:05 AM

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 closed this task as Resolved.Jun 21 2019, 4:05 PM
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 $zone.168.192.in-addr.arpa 86400 IN SOA pergamon.internal.softwareheritage.org. sysop.softwareheritage.org. 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.

gitlab-migration changed the task status from Resolved to Migrated.Oct 19 2022, 5:54 PM
gitlab-migration claimed this task.
gitlab-migration added a subscriber: gitlab-migration.

This task has been migrated to GitLab.

About · Developer information · Legal