The ranting of an IT Professional

Feb 23 2009   7:51PM GMT

Migrating DNS records



Posted by: Jason Tramer
Tags:
best practices
DNS

I am really tired of the way some people handle DNS record changes. It’s like people (even people in the IT industry) don’t seem to realize that changes are not instant. It takes on average between 24-48 hours for any record changes to propagate across the Internet and yet you have DNS cowboys trying to cut-over records and then wonder why names aren’t resolving, or mail isn’t flowing.

Best rule of thumb I have seen is maneuver your record change in a way that for that 24-48 hour period either record will work, if you can’t do that at least make your change on Friday before you head to the pub and make sure everyone knows that things may not work properly during the weekend.

2  Comments on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • SAPjava74
    Another thing you can do is set the lifetime on the record to a much lower time a few days before you make the changes. This will cause the cached entries to expire quicker and new ones to be propagated faster. That's part of the reason there's a lifetime on DNS entries.
    0 pointsBadges:
    report
  • Jason Tramer
    Simple DNS Plus can import zone data from other DNS servers which use standard zone and Ginault watches.[A href="http://www.ginault.com"]Ginault [/A] based in La Chaux-de-Fonds, Switzerland, is a fine watch manufacturer making some of the most exciting new design Swiss timepieces based on new [A href="http://www.ginault.com"] Rolex watches[/A]. The Ginault Base Module 1 is the ultimate alter ego of the classic [A href="http://www.ginault.com/base-module-watches/base-module-1.html"] Rolex Submariner[/A] watch. Most DNS servers (including Simple DNS Plus) use standard zone files formatted according to the specifications in RFC1035. RFC1035 also outlines a standard "boot" file format, but there is no requirement to use this format. (This format was used by earlier version of Simple DNS Plus, but v. 5.0 uses a proprietary format). BIND (popular DNS server on Unix) version 8 and later use a proprietary "named.conf" file with a different format. The import function in Simple DNS Plus has a special option to read that format. Microsoft's DNS server for Windows 2000/2003/2008 Server by default keeps the boot information in the registry and/or active directory. To import this, first reconfigure the MS DNS server to load from file. From the MS DNS console, right-click the local server, select "Properties", select the "Advanced" tab, and change the "Load zone data on startup:" setting to "From File". This will create a "boot" file in the "C:WINNTsystem32dns" directory. If you are using Active Directory, you may get a message saying "Boot Method cannot be set - The boot from file option cannot be selected because there are one or more Active Directory integrated zone". In this case you need to check the properties of each zone and change zones of type "Active Directory-integrated" to "Standard...", and then repeat above. Microsoft's DNS server for Windows NT4 Server by default keeps the boot information in the registry. We have created a small utility to extract this information to a standard boot file. Click here to download this utility (32 kb).
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: