[Pdns-users] PDNS Reverse DNS delegation

[Wouter de Jong]

On Wed, Apr 02, 2003 at 08:07:34PM +0200, bert hubert wrote:

> It works in the exact same way. The PowerDNS documentation does not document
> DNS, it documents PowerDNS - reverse works with PTR records, and PowerDNS
> fully supports these.

PTR yes ... but how about NS records?

I have 8.9.8.0.1.0.0.2.ip6.arpa (in ns1.widexs.nl), and in there
(pdns-style):

4.0.0.3.8.9.8.0.1.0.0.2.ip6.arpa NS ns1.widexs.nl

We want this so we can maintain our reverse-zones more easily :)

In the 4.0.0.3.8.9.8.0.1.0.0.2.ip6.arpa zone, I have:

4.0.0.3.8.9.8.0.1.0.0.2.ip6.arpa NS ns1.someother.domain

I can dig 4.0.0.3.8.9.8.0.1.0.0.2.ip6.arpa perfectly, and it is also
correct in ns1.someother.domain, BUT if i do a lookup somewhere on
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.0.0.3.8.9.8.0.1.0.0.2.ip6.arpa,
I get this error:

Apr  8 17:08:19 ns1 pdns[96414]: Authoritative NXDOMAIN to 213.206.99.2
for
'1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.0.0.3.8.9.8.0.1.0.0.2.ip6.arpa'
(PTR)



Somehow it doesn't seem to work to delegate a part of a reverse-zone to
the same nameserver and then delegate it fully to another nameserver.

It works perfectly when I forward 4.0.0.3.8.9.8.0.1.0.0.2.ip6.arpa in
8.9.8.0.1.0.0.2.ip6.arpa directly to ns1.someother.domain

> Regards,
> 
> bert

-- 
Met vriendelijke groet/With kind regards,

Wouter de Jong
System-Administrator

CABLE & WIRELESS
Delivering the Internet promise(tm)
URL:    http://www.widexs.nl

Email:  Wouter.deJong at cw.com
Tel:    +31 (0) 23 5698070
Fax:    +31 (0) 23 5698099


***************************************************************************************
This message may contain information which is confidential or privileged.
If you are not the intended recipient, please advise the sender immediately
by reply e-mail and delete this message and any attachments without retaining a copy.
***************************************************************************************