DNS zonefiles for the `cosi.clarkson.edu`, `cslabs.clarkson.edu`, and `csprojects.clarkson.edu` subdomains
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Alextopher 95d7d193a5 remove csprojects 3 months ago
webhook add ender 10 months ago
.DS_Store 233; add final-samuraihawks CNAME for the cs350 team 7 months ago
.gitignore migrated off of fork 2 years ago
README.md updated readme 1 year ago
check_zones.py remove csprojects 3 months ago
db.cosi serial 235; add auth 3 months ago
db.cslabs serial 235; add auth 3 months ago
db.cslabs.rvs.144 serial 235; add auth 3 months ago
db.cslabs.rvs.145 serial 235; add auth 3 months ago
db.cslabs.rvs.146 serial 235; add auth 3 months ago
db.cslabs.rvs.c051 serial 235; add auth 3 months ago
update_serial.py remove csprojects 3 months ago



This is the repository where we track our DNS zone files

Instructions to add records

The way that you update a configuration is as follows:

  1. Clone down the repository locally to your computer
  2. Add the changes you want (remember to add reverse DNS entries if you are adding A or AAAA records)
  3. Run ./update_serial.py which auto increments serials for all zone files
  4. Run ./check_zones.py to check your work
  5. Commit & Push your changes with a meaningful Git message. For example, "Serial 126, added random.cosi.clarkson.edu"

The webhook attached to this repo should trigger atlas to pull down and load any changes. However if this fails:

  1. Log into atlas and become root
  2. cd /etc/nsd/zones
  3. git pull
  4. systemctl reload nsd

If you are going to do it a different way, please make sure that you update the Git server with the newest version of the configuration, and be sure to make it so that we only need to "fast forward" on the DNS server itself.

Other notes

dns01.cosi.clarkson.edu and dns02.cosi.clarkson.edu are glue records from Clarkson's nameservers, for and, respectively. should not be used for any other purpose than a legitimate DNS server.


Remember that this DNS is propogated back to the public DNS servers. Please keep the record names apropriate. If you even slightly question the name, please contact a lab director for their input.