Chris Thompson wrote:
On Dec 7 2009, Kevin Darcy wrote:
[...snip...]
Or, you can run a script on the slaves which consults some
centralized "zone slaving database" to determine what zones to slave,
or to stop slaving. This "zone slaving database" can take many forms.
One idea is to represent this list as a special zone within DNS
itself, containing just one entry per zone to be slaved. I prefer
using PTR records for this, over, say, TXT records, since PTR records
can benefit from label compression.
Not to mention that they guarantee correct domain name syntax, and the
absence of duplicates (due to case-insensitivity). Ever since I first
saw you recommend this, I have wondered "why did I ever think TXT records
were the right way to do it?" ...
Flexibility is both the greatest strength and greatest weakness of TXT
records. We don't use TXT records for *anything* in production, although
we have an LDAP database maintained in parallel with DNS that gets
populated with various forms of textual data. Keeping that stuff in LDAP
makes it a lot more searchable.
- Kevin
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
