From Fedora Project Wiki

(15 intermediate revisions by 8 users not shown)
Line 1: Line 1:
= DNS - SOP =
== Contact Information ==
{{admon/important|All SOPs have been moved to the Fedora Infrastructure [ SOP git repository]. Please consult the [ online documentation] for the current version of this document.}}
Owner: Fedora Infrastructure Team
Contact: #fedora-admin, sysadmin-main group, Jesse Keating (f13) and Mike !McGrath (mmcgrath)
[[Category:Infrastructure SOPs]]
Location: Duke University and a Colo in Detroit
Purpose: Provides DNS to our users
== Description ==
We have two DNS server, the primary is at and is hosted at Duke University, from there it replicates to
== Troubleshooting, Resolution and Maintenance ==
{{Admon/note |  Note, is not run by Fedora's Infrastructure Team.  Its resources have been donated by Jesse Keating.}}
=== DNS update ===
DNS config files are puppet managed on puppet1.  The update is standard to the puppet configs at
From puppet1:
cvs -d /cvs/puppet co configs
cd configs/dns/master
vi # 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:
== resolv.conf ==
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.
{{Admon/important | Any machine that is not on our vpn or has not yet joined the vpn should _NOT_ have the search until after it has been added to the vpn (if it ever does)}}
=== Phoenix ===
=== Non-Phoenix ===
The idea here is that we can, when need be, setup local domains to contact instead of having to go over th 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.

Latest revision as of 12:01, 16 February 2017

Infrastructure InfrastructureTeamN1.png

All SOPs have been moved to the Fedora Infrastructure SOP git repository. Please consult the online documentation for the current version of this document.