Adam, can you immediately make the following changes to the hcoop.net zone file in the /etc/domains/net/hcoop/.dns file on fyodor?
1) Remove the record for ns3.hcoop.net in the .dns file for hcoop.net, this record is broken anyway since it points to a host that doesn't exist. 2) Add "A records in the hcoop.net. zone for: ns1.hcoop.net 69.90.123.67 ns3.hcoop.net 69.90.123.68 Long-winded explanation follows for how I foresee the migration happening in terms of DNS, if you can't anticipate how this could work out based on the record suggestions above: Currently we have one name server for most of our zones since abulafia (which was also known as ns2) died a week ago. We want to make our migration as seamless as possible, without disrupting service. This makes it desirable to have "parallel" authoritative name servers running for different zones, those that migrated and those that haven't. We also want to make our name servers contiguous, e.g., ns1.hcoop.net, ns2.hcoop.net, etc., instead of using ns.hcoop.net A rather elegant (I think) plan can be devised in order to achieve both of these goals. Basically, we are making new authoritative name servers (ns1.hcoop.net and ns3.hcoop.net) for all of the zones that are migrated to the Peer 1 configuration. All users who migrate a zone will, after setting up the zone in domtool on the new machines, go to their registrar and change the authoritative name servers to ns1.hcoop.net and ns3.hcoop.net. Within 24 hours, other name servers on the internet will start pointing to our Peer 1 name servers for this zone. Once we are done with fyodor, we will cut it, thereby killing ns2.hcoop.net, which shouldn't be used at that point anyway. We are then free to re-direct the ns2.hcoop.net name to a different name server in our architecture, perhaps to abu again at the Peer 1 setup. At this point, we can tell users to add the ns2.hcoop.net name server to their registrar's database, and we will have the contiguous name servers ns1.hcoop.net, ns2.hcoop.net, and ns3.hcoop.net fully in operation. As always, comments and critiques of this plan welcome! Justin _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
