Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Read offline with no ads or diagram watermarks!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  Name Systems and TCP/IP Name Registration and Name Resolution
           9  TCP/IP Name Systems: Host Tables and Domain Name System (DNS)
                9  TCP/IP Domain Name System (DNS)
                     9  DNS Name Servers and Name Resolution
                          9  DNS Name Server Concepts and Operation

Previous Topic/Section
DNS Name Server Load Balancing
Previous Page
Pages in Current Topic/Section
1
2
34
Next Page
DNS Resolution Concepts and Resolver Operations
Next Topic/Section

DNS Name Server Enhancements: DNS Notify, Incremental Zone Transfers, and DNS Update (Dynamic DNS)
(Page 2 of 4)

Automating Zone Transfers: DNS Notify

The first problem that many DNS administrators wanted to tackle was the reliance on polling for updating slave name servers. Imagine that you placed an order for a new music CD at your favorite online music store, but it was out of stock—backordered. Which makes more sense: having you call them every 6 hours to ask if it has arrived yet until it gets there, or having the store simply call you when it shows up?

The answer is so obvious that the question seems ridiculous. Yet DNS uses the first model: slave name servers must constantly “call up” their zone masters and ask them “has anything changed yet?” This both generates unnecessary traffic, and results in the slave name server being out of date from the time the master does change until the next poll is performed. Tweaking the Refresh time for the zone only allows one to choose between more polls or more staleness when changes happen; neither is really “good”.

To improve upon this situation, a new technique was developed; it was formalized in RFC 1996, published in 1996 (weird coincidence!) This standard, A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY), defines a new DNS message type called Notify, and describes a protocol for its use. The Notify message is a variation on the standard DNS message type, with some of the fields redefined to support this new feature.

When both the master and slave name servers support this feature, when a modification is made to a resource record, the master server will automatically send a Notify message to its slave server(s), saying “your CD has arrived!” er… “the database has changed”. J The slave then acts as if its Refresh timer has just expired. Enabling this feature allows the Refresh interval to be dramatically increased, since slave servers don't need to constantly poll the master for changes.

Key Concept: The optional DNS Notify feature allows a master name server to inform slave name servers when changes are made to a zone. This has two advantages: it cuts down on unnecessary polling by the slave servers to find out if changes have occurred to DNS information, and it also reduces the amount of time that slave name servers have out-of-date records.



Previous Topic/Section
DNS Name Server Load Balancing
Previous Page
Pages in Current Topic/Section
1
2
34
Next Page
DNS Resolution Concepts and Resolver Operations
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.