Re: Regarding EDNS Responses.

It's not a perfect world. Even getting back a EDNS response does not indicate that the server understands EDNS. In message <002301ca579c$56deb0f0$21011...@china.huawei.com>, Ashwin writes: > > In message <001501ca5785$257c7220$21011...@china.huawei.com>, Ashwin writes: > > > > Hi All, > > > >

RE: Regarding EDNS Responses.

In message <001501ca5785$257c7220$21011...@china.huawei.com>, Ashwin writes: > > Hi All, > > RFC 2671 mentions in Section 5.3 > > Responders who do not understand these protocol extensions are > expected to send a response with RCODE NOTIMPL, FORMERR, or > SERVFAIL. > > However the above ment

Re: Regarding EDNS Responses.

In message <001501ca5785$257c7220$21011...@china.huawei.com>, Ashwin writes: > > Hi All, > > RFC 2671 mentions in Section 5.3 > > Responders who do not understand these protocol extensions are > expected to send a response with RCODE NOTIMPL, FORMERR, or > SERVFAIL. > > However the above ment

Regarding EDNS Responses.

Hi All, RFC 2671 mentions in Section 5.3 Responders who do not understand these protocol extensions are expected to send a response with RCODE NOTIMPL, FORMERR, or SERVFAIL. However the above mentioned error codes are shared [SERVFAIL, NOTIMPL] are shared, so how do we ascertain t