m (1 revision(s)) |
mNo edit summary |
||
| Line 18: | Line 18: | ||
== Troubleshooting, Resolution and Maintenance == | == Troubleshooting, Resolution and Maintenance == | ||
{{ | {{Admon/note | Note, dns1.j2solutions.net is not run by Fedora's Infrastructure Team. Its resources have been donated by Jesse Keating.}} | ||
}} | |||
=== DNS update === | === DNS update === | ||
| Line 47: | Line 46: | ||
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. | 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 vpn.fedoraproject.org search until after it has been added to the vpn (if it ever does)}} | ||
}} | |||
=== Phoenix === | === Phoenix === | ||
Revision as of 20:03, 3 June 2008
DNS - SOP
Contact Information
Owner: Fedora Infrastructure Team
Contact: #fedora-admin, sysadmin-main group, Jesse Keating (f13) and Mike !McGrath (mmcgrath)
Location: Duke University and a Colo in Detroit
Servers: ns1.fedoraproject.org, DNS1.J2SOLUTIONS.NET
Purpose: Provides DNS to our users
Description
We have two DNS server, the primary is at ns1.fedoraproject.org and is hosted at Duke University, from there it replicates to dns1.j2solutions.net.
Troubleshooting, Resolution and Maintenance
DNS update
DNS config files are puppet managed on puppet1. The update is standard to the puppet configs at http://fedoraproject.org/wiki/Infrastructure/Puppet/QuickStart
From puppet1:
cvs -d /cvs/puppet co configs 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
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.
Phoenix
search fedora.phx.redhat.com vpn.fedoraproject.org fedoraproject.org
Non-Phoenix
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 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.