Hiya,
On 20/06/2024 14:34, Ondřej Surý wrote:
Stephen,
you actually gave me an idea - you should use BIND version without HTTPS record
support and just convert the records to TYPExxx form. That way, there will be no
parser standing in your way and you can put all kind of rubbish to the zone.
Stephen,
you actually gave me an idea - you should use BIND version without HTTPS record
support and just convert the records to TYPExxx form. That way, there will be
no parser standing in your way and you can put all kind of rubbish to the zone.
P.S.: Why am I even helping you when the eduroam
Hi again,
Actually, it may well be that bind allows me sufficient
leeway to do most of the tests I want, so this is just
to check that there's no imminent plan to have bind
disallow the kind of rubbish HTTPS RRs below. If that's
not likely to change in the next few months, then I'd
say I'm fine.
Hiya,
Thanks all for the info/suggestions. I guess I'll have
to try what Ondřej suggests or something similar, and
that's ok.
Cheers,
S.
OpenPGP_0xE4D8E9F997A833DD.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
--
Visit https://lists.isc.or
> On 20 Jun 2024, at 15:29, Michael Richardson wrote:
>
>
> Mark Andrews wrote:
>> Named and nsupdate validate input for types they know about (both text
>> and wire). You would have to use versions that are not HTTPS aware and
>> use unknown type format.
>
> So, he could code it in Perl or
5 matches
Mail list logo
