Edns-client-subnet
In the past, when a nameserver received a query, it was only aware of the remote IP of the other nameserver. It had no awareness of the end user client or device making the request, unless they just happened to be on the same host or device.
This can be a problem when trying to do things such as geo-target your DNS responses, especially if end users are employing large public resolver infrastructures that are themselves anycasted (think Google Public DNS, OpenDNS, or Quad9).
edns-client-subnet (https://trac.tools.ietf.org/html/rfc7871) addresses this by sending a subnet of the client stub-resolver, usually the first three octets of an IPv4 address or 56 bits of an IPv6 address.
The authoritative nameserver, or any middleware ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access