Re: RFC8482: Implementation through HINFO record
And named already handles ANY being used as an reflection amplifier. This was written for servers using databases where getting the ANY response is actually hard. Cloudflare was using a response model that most thought was not really correct but wasn’t broken enough to say “Don’t do that”. If their customers where happy with this behaviour then ok. This RFC was written to allow them to continue doing what they where doing without having to fight that they where not RFC compliant. It was not written to say this is how you should respond to ANY. It also requires online signing for DNSSEC or adding a HINFO record for every name in your zone when offline signing. Mark -- Mark Andrews > On 21 May 2024, at 00:31, Ondřej Surý wrote: > > I would suggest you to create a feature request in our GitLab. This way it > won't get lost > in the tides of time. > > Personally, I actually quite like the idea, but it would have to be an option > to turn off and on, > so it's not going to save us from having a code that supports ANY anyway. > > Ondřej > -- > Ondřej Surý (He/Him) > ond...@isc.org > > My working hours and your working hours may be different. Please do not feel > obligated to reply outside your normal working hours. > >> On 20. 5. 2024, at 16:03, Amaury Van Pevenaeyge >> wrote: >> >> Hello everyone, >> >> How is it possible to set up a resource record of type HINFO so that it is >> returned on every ANY request without all the other records in the zone? I'm >> looking to implement RFC8482 as Cloudflare can do in the following article: >> https://blog.cloudflare.com/rfc8482-saying-goodbye-to-any >> >> Thanks in advance for your help. >> -- >> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from >> this list >> >> ISC funds the development of this software with paid support subscriptions. >> Contact us at https://www.isc.org/contact/ for more information. >> >> >> bind-users mailing list >> bind-users@lists.isc.org >> https://lists.isc.org/mailman/listinfo/bind-users > > > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from > this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: RFC8482: Implementation through HINFO record
I would suggest you to create a feature request in our GitLab. This way it won't get lost in the tides of time. Personally, I actually quite like the idea, but it would have to be an option to turn off and on, so it's not going to save us from having a code that supports ANY anyway. Ondřej -- Ondřej Surý (He/Him) ond...@isc.org My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 20. 5. 2024, at 16:03, Amaury Van Pevenaeyge > wrote: > > Hello everyone, > > How is it possible to set up a resource record of type HINFO so that it is > returned on every ANY request without all the other records in the zone? I'm > looking to implement RFC8482 as Cloudflare can do in the following article: > https://blog.cloudflare.com/rfc8482-saying-goodbye-to-any > > Thanks in advance for your help. > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from > this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: RFC8482: Implementation through HINFO record
Named does not support this. There is no requirement to support this. -- Mark Andrews > On 21 May 2024, at 00:04, Amaury Van Pevenaeyge > wrote: > > > Hello everyone, > > How is it possible to set up a resource record of type HINFO so that it is > returned on every ANY request without all the other records in the zone? I'm > looking to implement RFC8482 as Cloudflare can do in the following article: > https://blog.cloudflare.com/rfc8482-saying-goodbye-to-any > > Thanks in advance for your help. > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from > this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RFC8482: Implementation through HINFO record
Hello everyone, How is it possible to set up a resource record of type HINFO so that it is returned on every ANY request without all the other records in the zone? I'm looking to implement RFC8482 as Cloudflare can do in the following article: https://blog.cloudflare.com/rfc8482-saying-goodbye-to-any Thanks in advance for your help. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: RFC8482: Implementation
Hi. In BIND, since 9.11, there is an option/view statement called "minimal-any", which defaults to "no". That might be what you're after. Cheers, Greg On Sat, 20 Apr 2024 at 17:29, Amaury Van Pevenaeyge < avanpevenae...@outlook.fr> wrote: > Hello everyone, > > I've been looking for days and days for a way to implement the principle > documented in RFC8482 (Providing Minimal-Sized Responses to DNS Queries > That Have QTYPE=ANY) as Cloudflare is currently doing. I can't find the > solution to do this. Can anyone help me with this? > > Thanks in advance > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users > -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RFC8482: Implementation
Hello everyone, I've been looking for days and days for a way to implement the principle documented in RFC8482 (Providing Minimal-Sized Responses to DNS Queries That Have QTYPE=ANY) as Cloudflare is currently doing. I can't find the solution to do this. Can anyone help me with this? Thanks in advance -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
