Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S sysadm-environment
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 167
    • Issues 167
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Platform
  • Infrastructure
  • sysadm-environment
  • Issues
  • #4439
Closed
Open
Issue created Aug 16, 2022 by Nicolas Dandrimont@olasdOwner

ns0.euwest.azure stops responding for internal.admin.swh.network when pergamon is unreachable

The SOA TTLs for internal.admin.swh.network were set before they were updated in puppet, with the old (way too low) values.

Update them with decent values instead:

olasd@pergamon:~$ (echo update add internal.admin.swh.network 86400 IN SOA pergamon.internal.softwareheritage.org. sysop.softwareheritage.org. 19 3600 120 604800 120; echo send) | sudo nsupdate -k /etc/bind/keys/local-update

(19 is a valid serial for this zone)


Migrated from T4439 (view on Phabricator)

Assignee
Assign to
Time tracking