Maradns forgets TXT records with asked for ANY ?
Sam Trenholme
strenholme.usenet at gmail.com
Tue May 18 17:49:08 EDT 2010
>>> Is this [not seeing a TXT record] a maradns bug ? I'm not a DNS expert,
>>> but it looks so for me.
>>
>> Which version of MaraDNS are you using?
>
> I use the package provided by my distribution (Debian Etch AMD64) ; maradns
> version 1.3.07.09. (package is latest available ; 1.3.07.09-2).
Works for me. In window 1, I did the following as root:
→ # ./server/maradns --version
This is MaraDNS version 1.3.07.09
Compiled on a Linux system at mar may 18 16:40:45 CDT 2010
For usage information, 'man maradns'
→ # ./server/maradns
THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
To not display this message, add the follwing to your mararc file:
hide_disclaimer = "YES"
Log: Root directory changed
Log: Binding to address 127.0.0.4
Log: Socket opened on UDP port 53
Log: Root privileges dropped
Processing zone example.com. right now.
Filename: db.simple
MaraDNS proudly serves you 8 DNS records
MaraDNS maximum memory allocation set to 2633728 bytes
Log: All RRs have been loaded
And, in window two:
→ $ cat /etc/mararc
csv2 = {}
csv2["example.com."] = "db.simple"
ipv4_bind_addresses = "127.0.0.4"
chroot_dir = "/etc/maradns"
16:44:21 deadwood $ cat /etc/maradns/db.simple
example.com. +1 SOA z.%
y@% 1 1 1 1 1 ~
example.com. +3600 NS ns1.example.net. ~
example.com. +3600 NS ns2.example.net. ~
example.com. +3600 NS ns3.example.net. ~
example.com. +3600 MX 10 mail.example.net. ~
example.com. +3600 MX 20 mail2.example.net. ~
example.com. TXT 'dns.' ~
example.com. TXT 'hello';'world' ~
→ $ dig @127.0.0.4 example.com ANY
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @127.0.0.4 example.com ANY
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27124
;; flags: qr aa rd; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;example.com. IN ANY
;; ANSWER SECTION:
example.com. 3600 IN NS ns1.example.net.
example.com. 3600 IN NS ns3.example.net.
example.com. 3600 IN NS ns2.example.net.
example.com. 60 IN SOA z.example.com.
y.example.com. 1 1 1 1 1
example.com. 3600 IN MX 10 mail.example.net.
example.com. 3600 IN MX 20 mail2.example.net.
example.com. 86400 IN TXT "dns."
example.com. 86400 IN TXT "hello" "world"
;; Query time: 48 msec
;; SERVER: 127.0.0.4#53(127.0.0.4)
;; WHEN: Tue May 18 16:44:38 2010
;; MSG SIZE rcvd: 218
To make this more readable, lines where I entered commands at the
shell prompt are marked with → at the beginning of the line.
So, if you want to see this fixed: Come up with the simplest mararc +
zone file combination that reproduces the problem. Once you do this,
post the mararc and zone file to the list, ideally not as an
attachment.
- Sam
Note: I do not answer MaraDNS (including Deadwood) support requests
sent by private email without being compensated for my time. A MaraDNS
support request is any and all discussion you may wish to have about
MaraDNS in private email; if you want to email me to talk about
MaraDNS then, yes, that is a support request. I will discuss rates if
you want this kind of support. Thank you for your understanding.
MaraDNS security vulnerability reports, however, will be dealt with
without charge and kept confidential. If you don't know what Bugtraq
is, then, no, your email is not a security report. It is not a
security report unless you've done due diligence to determine how the
security bug you think you found can reasonably be exploited.
More information about the list
mailing list