Speed and accuracy are two crucial components of end user experience. This is why Dyn made the decision to be one of the first providers to allow EDNS0-Client-Subnet data to be used in geolocation responses.
EDNS0-Client-Subnet (ECS) uses BIND functions to return geolocation of the requesting client’s subnet instead of the recursive server’s subnet. This allows for even further accuracy in DNS responses when using Traffic Director. Keep in mind, at this time ECS responses can only be returned for answers in Traffic Director, not just in RFC-type resource records. Other records will be responded to the same way they are today, with the record being caches at the resolver level for everyone.
You Queried, We Answered
Each query with ECS data will need to be resolved by a recursive DNS provider that includes ECS information in queries. Luckily, Google Public DNS and OpenDNS both support ECS data, and together make up for about 20% of the world’s DNS traffic, according to some reports.
When a DNS query is received, Dyn’s nameservers will automatically look to see if ECS data is provided and then check to see if the hostname has an associated Traffic Director. So long that the answer to both of these question is yes, the ECS data passed along will be used in the geolocation lookup, at which point Dyn will provide the appropriate geo-located answer, based on the Traffic Director configuration. Then, the recursive resolver will cache the response for the corresponding subnet, allowing for even faster answers the next time a similar query is received for the subnet. All of this, of course, happens in milliseconds.
Now, this all sounds fine and dandy, and the best part is that ECS is available to customers at no direct cost, as long as Traffic Director is included in the contract. Just keep in mind that ECS will rely less on recursive cache, which can mean an uptick in QPS.
The final piece would be to actually configure ECS. This will allow ECS data to be used in queries solving for each domain specified. Enabling ECS is as easy as reaching out to our Support Team. Keep in mind, this is enabled on a per-domain basis, so include which domains should be included in any reach outs. Once the Support Team has turned this on, new queries will immediately start including ECS data when geolocating the end user. Anyone interested in adding Traffic Director and enabling ECS on top of this is encouraged to reach out to either their respective Account Manager, or our Sales Team.