search

matje / mixfr

Minimal IXFR
0 stars 4 forks source link

Behavior for MIXFR unaware servers and resolvers #14

Open matje opened 6 years ago

matje commented 6 years ago

Pieter Lexis: Some words need to be added about the fact that current resolvers will pass through the MIXFR query and not reply with NOTIMPL. In a similar vein, unaware auths will respond with an NXDOMAIN or (more likely) a NODATA in that case.

matje commented 6 years ago

IXFR solved this by saying "If the query type is not recognized by the server, an AXFR (preceded by a UDP SOA query) should be tried, ensuring backward compatibility." Probably MIXFR can say something similar.

A resolver should behave similar for MIXFR as it does for AXFR and IXFR. I can't find words about this in RFC 1995 or RFC 5936, so I am not sure if this document should add something about that.

Ray Bellis mentioned that a Meta RRType should never be passed through resolvers - they're only used on the wire between client and server, and not end-to-end.