Best practices for coding new RR Types
Mark Andrews
marka at isc.org
Fri Oct 16 23:08:26 UTC 2015
In message <A05B583C828C614EBAD1DA920D92866BA5DDF69D at PODCWMBXEX501.ctl.intranet
>, "Woodworth, John R" writes:
>
> Hello,
>
> I am trying to implement logic for an experimental (Internet Draft) RR
> type and follow most of the code flow but am curious if there is a common
> methodology beyond trying to duplicate another record with similar
> attributes.
That's basically what we do. Cut and paste different field types
from existing RR types. Take extreme care as this is a extremely
security sensitive area of the nameserver as it is parsing data
received from untrusted sources. Think edge cases.
B.T.W. which RR are you trying to implement? All the ones with
assigned values are implemented.
Mark
> Any help/ tips to get ramped up quickly with the process and avoid
> pitfalls would be greatly appreciated. I am new to the codebase so any
> documents to limit silly questions are also appreciated.
>
>
> Thanks,
> John
> This communication is the property of CenturyLink and may contain
> confidential or privileged information. Unauthorized use of this
> communication is strictly prohibited and may be unlawful. If you have
> received this communication in error, please immediately notify the
> sender by reply e-mail and destroy all copies of the communication and
> any attachments.
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka at isc.org
More information about the bind-users
mailing list