Adding a new Resource Record (RR) Type to BIND 9
David M Walker
davidw at datamgmt.com
Wed Jan 1 21:42:54 UTC 2020
The extra document is very useful - thanks
65634 should have been 65534 - I’m a full 55 years old and was brought up on 8-bit. I know this and just shows that working when tired and cut and paste confounds errors - thanks
The tests etc will be done, the idea we are working on may lead to an RFC so will have to be rigorously tested assuming I understand 8-bit to start with !
Thanks again - it worked
> On 1 Jan 2020, at 19:40, Evan Hunt <each at isc.org> wrote:
> On Wed, Jan 01, 2020 at 06:55:18PM +0000, David M Walker wrote:
>> There is a knowledge base that covers exactly the first part of what I want to do by adding a new RR Type
>> https://kb.isc.org/docs/aa-01140 <https://kb.isc.org/docs/aa-01140>
> Also might want to read doc/dev/rdata.md in the source directory.
>> I then created account_65634.c and account_65634.h
> 65634 is greater than 2^16. RR type codes can only go up to 65535, and
> it appears higher numbers are silently ignored when found by gen.c.
> (In hindsight, that's a mistake; it should at least have printed a
>> Any suggestions on what else over and over the instructions has to be done?
> I think changing the type code will be sufficient, but I'd suggest
> updating the tests to include your new type as well. Have a look at
> commit 3183663dd4ae for an example.
> Evan Hunt -- each at isc.org
> Internet Systems Consortium, Inc.
More information about the bind-workers