DNS Real-time Initiative: Publishers
Who is a Publisher?
The most likely candidates to publish to Neustar’s DNS Real-time Directory are providers of Authoritative DNS services. They may include all players with a role in updating DNS records including Root Servers, TLDs, SLDs, Registrars, CDNs, and others.
Benefits
- Customer Experience: Provide the best possible level of DNS updates to your customers.
- Reliability and Speed: Give customers the ability to rapidly deploy changes, regardless of TTL settings.
- Security: Push out updates to domains suspected to be involved in cache poisoning attacks.
- Low Barrier to Adoption: The DNS Real-time Directory is easy to deploy, and transparent to support internally.
- Customer Service: Reduce support calls and costs related to DNS propagation.
- Innovation: Become an integral part of a team working collectively to improve the performance of the Internet!
How Does it Work?
Publishers provide a feed of domains to be updated using Neustar's DNS Real-time Directory service to propagate changes out to subscribers. Publishers will install a script in their Authoritative DNS system that publishes updates to the DNS Real-time Directory; when updates are received in the Directory, they are pushed out to all subscribers in near real-time. Then, once updates are received by subscribers, the corresponding domain records are purged from their Recursive DNS servers – and the next request that comes in will trigger the recursive server to obtain the latest record from the Authoritative source.
The Publisher controls the type of updates sent, and should provide domains that have been deployed across their Authoritative servers to ensure that subscribers will get updated records when they reload their caches.
How Do I Integrate My Authoritative DNS with the DNS Real-time Directory?
Similar to the subscriber side, publishers will download and install the DNS Real-time Directory publisher script in their Authoritative DNS systems. The script updates the domains in the DNS Real-time Directory, which subsequently instructs subscribers' recursive DNS servers to flush items from their caches. Each publisher provides source IP information for the servers running the script to configure their feeds to publish to the DNS Real-time Directory queues.
|
