New RR types?

[Radu "Ux" D.]

Well, I decided to take the hard way: we'll use libdns methods for 
making the packets, signing, interpret the answers and out own methods 
for send/recv. Still I am worried about using libdns, _not_ a 
development library. I just hope that the API won't change dramatically 
in the future.

Thx

Radu "Ux" D.



Gushi wrote:

>Speaking from a little experience.  I had a similar problem with dhis
>(www.dhis.org -- one of the less popular dynamic name services), they
>basically had pluggable "engines" to update things like firewall rules,
>or configs, or dns details.  Problem was, that their stuff was
>hardcoded against libbind, and as the source aged slightly, well, I'm
>sure you can imagine what happened.
>
>My solution was to rip it out and rewrite the engine as a wrapper in
>perl to call nsupdate (which would grow with my dns version)  I doubt
>your app has such a "drop-in" plug in mechanism, sadly, so you're
>probably looking at redoing the code.
>
>
>
>  
>