Hi Guix and Savannah admins,
We're planning to change the IP address of ns1.gnu.org some time next
week, to fix an issue with the installation that would normally require
extended downtime. Because the server is a slave for the guix.gnu.org
and savannah.gnu.org zones, and because our other name servers are
merely slaves to ns1.gnu.org, we are doing this in a multi-step process.
If you could please add the IP address of `ns1-new.gnu.org` to the list
of servers that receive transfers from your zones, that would be great.
The new IP address is:
192.99.37.66
Note that this server isn't yet in our zone file or in our glue records
as ns1.gnu.org yet, so it's currently inactive. Therefore if you could
please keep the rules for the current ns1.gnu.org server, that would
allow us to keep serving your zones prior to the changeover.
You may need to add our IP address to your firewalls, and to use the
`also-notify` directive, if you're using `bind`, as our staging name
server is not in our zone file as a name server for gnu.org.
https://bind9.readthedocs.io/en/v9.18.14/reference.html#namedconf-statement-also-notify
There's no major rush, so if you don't get to this immediately, or if
you can't get it working, that's fine. Let us know if you run into
trouble. To debug the change, you could try running:
dig guix.gnu.org @ns1-new.gnu.org
dig sv.gnu.org @ns1-new.gnu.org
Anyhow, if you have any questions, please let us know. Thanks in advance
for your help! : )
Andrew
--
Join the FSF and help us defend software freedom: https://my.fsf.org/
US government employee? Use CFC charity code 63210 to support us through
the Combined Federal Campaign. https://cfcgiving.opm.gov/
