DNS Infrastructure SOP
We have two DNS server, the primary is at ns1.fedoraproject.org and is hosted at ServerBeach, from there it replicates to dns1.j2solutions.net.
Owner: Fedora Infrastructure Team
Contact: #fedora-admin, sysadmin-main group, Jesse Keating (f13) and Mike McGrath (mmcgrath)
Location: ServerBeach and a Colo in Detroit
Servers: ns1.fedoraproject.org, DNS1.J2SOLUTIONS.NET
Purpose: Provides DNS to our users
Troubleshooting, Resolution and Maintenance
DNS config files are puppet managed on puppet1. The update is standard to the puppet configs at http://fedoraproject.org/wiki/Infrastructure/Puppet/QuickStart
git clone /git/puppet cd configs/dns/master vi fedoraproject.org # Don't forget to increment the serial! cd ../.. cvs commit -m "What you did" make install
It should update within a half hour. You can test the new configs with dig:
dig @ns1.fedoraproject.org fedoraproject.org dig @dns1.j2solutions.net cvs.fedoraproject.org
In order to make the network more transparent to the admins we do a lot of search based relative names. Below is a list of what a resolv.conf should look like.
search fedora.phx.redhat.com vpn.fedoraproject.org fedoraproject.org
search vpn.fedoraproject.org fedoraproject.org
The idea here is that we can, when need be, setup local domains to contact instead of having to go over the VPN directly but still have sane configs. For example if we tell the proxy server to hit "app1" and that box is in PHX, it will go directly to app1, if its not, it will go over the vpn to app1.