TXT records in reverse domains

[Cherney John-CJC030]

Thank you all for your information!

Chris, you bring up a good point that I hadn't really considered. It
wouldn't be anything major like below, but it wouldn't necessarily be
anything I would want everyone knowing, although 99.9% of the people who
would discover it probably wouldn't care about it. It is just that last
0.1%...

For these zones, I do have allow-updates and allow-transfer restricted.
The only way to discover if a zone has a text record in it, besides
knowing about it ahead of time, is to get a full zone transfer and parse
through it, right? There isn't a way to pull out all of the text records
of a zone with some type of wild-card, is there? Given that I've
restricted transfers to trusted hosts, is there anything else I
could/should do?

Thanks!
jwc

-----Original Message-----
From: Chris Thompson [mailto:cet1 at hermes.cam.ac.uk] 
Sent: Friday, May 16, 2008 12:08 PM
To: Cherney John-CJC030
Cc: bind-users at isc.org
Subject: Re: TXT records in reverse domains

On May 15 2008, Cherney John-CJC030 wrote:

>Is there any issue with putting TXT records in reverse domains? I want 
>to put some TXT records in the same domain as some of my PTR records to

>give additional information on the hosts in that domain.

As others have said, there's no technical problem here at all.

I would worry more about what sort of "information on the hosts" you are
going to publish, possibly world-wide. 

  TXT "Root password is M-6474ore"
  TXT "The one with a really expensive 3-D graphics card"
  TXT "Office 42, ground floor. Key is under the mat"

OK, I insult your intelligence! But I have seen things nearly that
stupid before now...

--
Chris Thompson
Email: cet1 at cam.ac.uk