[Pdns-users] database structure (records table)
Norbert Sendetzky
norbert at linuxnetworks.de
Sun Nov 30 13:28:27 UTC 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Markus
Just a few thoughts of mine:
> 1) Is it really neccessary to put the full name in the name
> coloumn? For instance the www-record of example.com:
> www.example.com ?
FQDN entries speed up queries because you only have to process one
result instead of two (one for example.com and one for the
corresponding www entry). Having two entries is a mistake also made
by the bind ldap developer in his latest scheme. The negative effects
simply outweights the positive ones.
> 2) "priority" only affects MX record types (preference), is there a
> specific reason on putting it in there for every record?
This was a design decision which requires some work to change it now,
but I would also prefer if the priority value would be in the content
entry. This would save me the code to do it myself in the ldap
backend.
The only other record type I've seen a priority value so far is in the
SRV record.
> 4) Naming of the attributes in the table. I think those should
> be named after RFC 1035: content = RDATA, prio = PREFERENCE,
> etc.
I think most of the people wouldn't understand the nameing scheme if
it would be changed to RDATA and PREFERENCES, so it isn't something I
would consider.
Norbert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj/J8HsACgkQxMLs5v5/7eDH7ACffxkPxivcGgSVnQkia/Eugx0Y
nqsAn10ITTpaPlJy1ZXNC8xE+FEsxuSO
=481m
-----END PGP SIGNATURE-----
More information about the Pdns-users
mailing list