confusion of edns in dns request, get wrong response

113 views
Skip to first unread message

tangzh...@gmail.com

unread,
Apr 19, 2017, 5:30:43 PM4/19/17
to public-dns-discuss

custom resolver ------ google public dns ------ authoritative dns server
                                                                    A
                                                                    |
                                                                    -- tcpdump

i uesed "dig @8.8.8.8 t.ttspace.xyz" command
i think google public dns should payload custom ip in subnet of ends0, and  i used tcpdump to capture dns request packet like blow
packet 1


packet 2


why google public dns lost data of edns at somttimes,  for this reason,  i am get wrong response at custom resolver.


Best Regards
tom

Alex Dupuy

unread,
Jul 9, 2017, 2:59:35 PM7/9/17
to public-dns-discuss, tangzh...@gmail.com
Google Public DNS does auto-detection of support for EDNS Client Subnet (ECS), your name server probably wasn't sending responses with ECS (even NXDOMAIN and other errors) to all queries with ECS. A common error is not to handle IPv6 addresses in ECS data when your name server is IPv4 only (clients contact Google Public DNS via IPv6 and it may resolve those queries via IPv4, or vice versa).
 
Reply all
Reply to author
Forward
0 new messages