Bug#444639: pdnsd unable to handle 2 mx entries

[Eric Van Buggenhaut]

Package: pdnsd
Version: 1.2.4par-0.2
Severity: important

I have my pdnsd server setup with two mx entries for a domain. Still the
server only responds dns queries with the second entry and seems to forget
about the first one:

rr {
        ttl=86400;
        #owner="ns.amps.es.";
        name="amps.es";
        mx="piano.amps.es",10;
        soa="ns.amps.es.","root.ns.amps.es.",42,86400,900,86400,86400;
}

rr {
        ttl=86400;
        #owner="ns.amps.es.";
        name="amps.es";
        mx="smtp.proyectosolidario.org",20;
        soa="ns.amps.es.","root.ns.amps.es.",42,86400,900,86400,86400;
}

but when queried:

mekas:/home/eric# host -t mx amps.es localhost
Using domain server:
Name: localhost
Address: 127.0.0.1#53
Aliases:

amps.es mail is handled by 20 smtp.proyectosolidario.org.


If I comment the second entry:

rr {
        ttl=86400;
        #owner="ns.amps.es.";
        name="amps.es";
        mx="piano.amps.es",10;
        soa="ns.amps.es.","root.ns.amps.es.",42,86400,900,86400,86400;
}

#rr {
#        ttl=86400;
#        #owner="ns.amps.es.";
#        name="amps.es";
#        mx="smtp.proyectosolidario.org",20;
#        soa="ns.amps.es.","root.ns.amps.es.",42,86400,900,86400,86400;
#}

I get:

mekas:/home/eric# host -t mx amps.es localhost
Using domain server:
Name: localhost
Address: 127.0.0.1#53
Aliases:

amps.es mail is handled by 10 piano.amps.es.
mekas:/home/eric#

AFAIR in the past pdnsd supported various mx entries. Has that behaviour
changed since then ?



-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)

Versions of packages pdnsd depends on:
ii  adduser                3.102             Add and remove users and groups
ii  libc6                  2.3.6.ds1-13etch2 GNU C Library: Shared libraries

pdnsd recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]