Difference between revisions of "BXadmin:DNS"
From CCGB
| Line 2: | Line 2: | ||
| − | Production data is stored under | + | Production data is stored under ''prod/'' |
| Line 13: | Line 13: | ||
To make changes to dns: | To make changes to dns: | ||
| − | * git clone /afs/.bx.psu.edu/service/dns/bxdns.git | + | * ''git clone /afs/.bx.psu.edu/service/dns/bxdns.git'' |
* make changes | * make changes | ||
| − | * git commit | + | * ''git commit [<filename> -m <comment>|-a -m <comment>]'' |
| − | * git push | + | * ''git push'' |
| − | * /afs/bx.psu.edu/service/dns/scripts/export-to-prod.sh | + | * ''/afs/bx.psu.edu/service/dns/scripts/export-to-prod.sh'' |
| + | |||
| + | |||
| + | Afterwards, make sure to do a ''git pull'', or a ''git fetch'' followed by a ''get merge'' afterwards to help avoid merge conflicts when pushing to the central repository. | ||
Revision as of 10:22, 14 June 2010
DNS configuration is stored in /afs/bx.psu.edu/service/dns
Production data is stored under prod/
Each dns server (ns1, ns2, ns3) runs a script every minute that creates a new PAG, gets a kerberos ticket, afs token, and then runs /afs/bx.psu.edu/service/dns/scripts/cron-update-dns.sh. This copies over named.conf, and rsyncs the zone files, performing an rndc reload only if necessary.
/afs/bx.psu.edu/service/dns/scripts/export-to-prod.sh is used to perform a git pull under prod/, then releases the svc.dns volume.
To make changes to dns:
- git clone /afs/.bx.psu.edu/service/dns/bxdns.git
- make changes
- git commit [<filename> -m <comment>|-a -m <comment>]
- git push
- /afs/bx.psu.edu/service/dns/scripts/export-to-prod.sh
Afterwards, make sure to do a git pull, or a git fetch followed by a get merge afterwards to help avoid merge conflicts when pushing to the central repository.
