Bug#499396: IPv6 addresses directly on the toplevel of the zonefile

2008-11-03 Thread Philipp Kern 
On Thu, Sep 18, 2008 at 01:10:41PM +0200, Philipp Kern wrote:
 I am using pdns with the bind backend and am experiencing trouble with
  records since the upgrade from Etch to Lenny.  Interestingly only
 on records on the toplevel of the zonefile (in my case 2nd level
 domains).  It seems that there is some memory corruption going on.
 The addresses are different whenever I reload pdns and I think that they
 also vary when they got pulled from the cache.
 
 The server in question is publically reachable.

Is there any progress on this?  Could you maybe forward this upstream?
It's so annoying that it's completely a show-stopper for my server,
as it returns crap on CNAMEs pointing to the TLD entry, too.  Of course
it only affects IPv6, I hope it's not based on that this seems to be
ignored.  (And it happens with the bind backend, not just with some
random database.)

Kind regards,
Philipp Kern


signature.asc
Description: Digital signature

Bug#499396: IPv6 addresses directly on the toplevel of the zonefile

2008-11-03 Thread Christoph Haas 
Hi, Philip...

On Montag, 3. November 2008, Philipp Kern wrote:
 On Thu, Sep 18, 2008 at 01:10:41PM +0200, Philipp Kern wrote:
  I am using pdns with the bind backend and am experiencing trouble with
   records since the upgrade from Etch to Lenny.  Interestingly only
  on records on the toplevel of the zonefile (in my case 2nd level
  domains).  It seems that there is some memory corruption going on.
  The addresses are different whenever I reload pdns and I think that
  they also vary when they got pulled from the cache.
 
  The server in question is publically reachable.

 Is there any progress on this?  Could you maybe forward this upstream?
 It's so annoying that it's completely a show-stopper for my server,
 as it returns crap on CNAMEs pointing to the TLD entry, too.  Of course
 it only affects IPv6, I hope it's not based on that this seems to be
 ignored.  (And it happens with the bind backend, not just with some
 random database.)

Sorry, I missed to set the upstream tag on the bug report. I had 
instantly informed the upstream about your finding. He told me that he was 
very busy (~1 month ago) but that he will deal with them as soon as 
possible.

 Christoph


signature.asc
Description: This is a digitally signed message part.

Bug#499396: IPv6 addresses directly on the toplevel of the zonefile

2008-09-18 Thread Philipp Kern 
Package: pdns-server
Version: 2.9.21.1.0-1
Severity: important

Hi there,

I am using pdns with the bind backend and am experiencing trouble with
 records since the upgrade from Etch to Lenny.  Interestingly only
on records on the toplevel of the zonefile (in my case 2nd level
domains).  It seems that there is some memory corruption going on.
The addresses are different whenever I reload pdns and I think that they
also vary when they got pulled from the cache.

The server in question is publically reachable.

 snip 
~  dig  philkern.de @durotan.0x539.de

;  DiG 9.3.4   philkern.de @durotan.0x539.de
; (2 servers found)
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 39014
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;philkern.de.   IN  

;; ANSWER SECTION:
philkern.de.10800   IN  
6b65:726e:2e64:6500:517c:414e:597c:2d31

;; Query time: 10 msec
;; SERVER: 88.198.49.206#53(88.198.49.206)
;; WHEN: Thu Sep 18 13:07:25 2008
;; MSG SIZE  rcvd: 57
 snip 

Some snippets from the zonefile:
[...]
@   IN A88.198.49.206 ; durotan
@   IN  2001:6f8:900:17a::2 ; durotan
[...]
durotan.ipv6IN  2001:6f8:900:17a::2
[...]

The A query works just fine.  Normal zone entries work, too:

 snip 
~  dig  durotan.ipv6.philkern.de @durotan.0x539.de

;  DiG 9.3.4   durotan.ipv6.philkern.de @durotan.0x539.de
; (2 servers found)
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 34610
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;durotan.ipv6.philkern.de.  IN  

;; ANSWER SECTION:
durotan.ipv6.philkern.de. 10800 IN  2001:6f8:900:17a::2

;; Query time: 9 msec
;; SERVER: 88.198.49.206#53(88.198.49.206)
;; WHEN: Thu Sep 18 13:10:07 2008
;; MSG SIZE  rcvd: 70
 snip 

Kind regards,
Philipp Kern

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-6-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pdns-server depends on:
ii  adduser3.110 add and remove users and groups
ii  debconf [debconf-2.0]  1.5.22Debian configuration management sy
ii  libc6  2.7-13GNU C Library: Shared libraries
ii  libgcc11:4.3.1-9 GCC support library
ii  libstdc++6 4.3.1-9   The GNU Standard C++ Library v3
ii  ucf3.007 Update Configuration File: preserv
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages pdns-server recommends:
pn  pdns-doc  none (no description available)

Versions of packages pdns-server suggests:
ii  pdns-backend-pgsql [pdns-ba 2.9.21.1.0-1 generic PostgreSQL backend for Pow
ii  pdns-recursor   3.1.7-1  PowerDNS recursor

-- debconf information excluded



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