[Dibbler] DDNS problem with dibbler-server and ISC-client

Tomek Mrugalski thomson at klub.com.pl
Thu Aug 2 19:11:20 CEST 2012


On 12-08-02 05:06, Klose, Dieter wrote:
> forward resolving seems to be running, but I have problems with 
> reverse resolving:
> 
> 2012.08.01 18:30:29 Server Info      FQDN: Client requested 
> (crema42test.ipv6.osd.abg.fsc.net), assigning 
> (crema42test.ipv6.osd.abg.fsc.net). 2012.08.01 18:30:29 Server Debug 
> FQDN: Adding FQDN Option in REPLY message: 
> crema42test.ipv6.osd.abg.fsc.net, FQDNMode=2 2012.08.01 18:30:29 
> Server Notice    FQDN: About to perform DNS Update: 
> IP=fd12::b040:19c8:649a:cf0d and 
> FQDN=crema42test.ipv6.osd.abg.fsc.net 2012.08.01 18:30:29 Server
> Info DDNS: Performing DNS Update over TCP, DNS address=fd12::1: Add
> PTR record. 2012.08.01 18:30:29 Server Error     DDNS: Attempt to get
> old DNS record failed. 2012.08.01 18:30:29 Server Debug     DDNS:
> PTR record created: 
> d.0.f.c.a.9.4.6.8.c.9.1.0.4.0.b.0.0.0.0.0.0.0.0.0.0.0.0.2.1.d.f.ip6.arpa.
> -> crema42test.ipv6.osd.abg.fsc.net 2012.08.01 18:30:29 Server Error
> DDNS: Nameserver returned NOTAUTH error. 2012.08.01 18:30:29 Server 
> Error     DDNS: Update failed. Error: NOTAUTH. 2012.08.01 18:30:29 
> Server Warning   DDNS: DNS Update failed: server returned NOTAUTH. 
> 2012.08.01 18:30:29 Server Info      DDNS: Performing DNS Update
> over TCP, DNS address=fd12::1: Add AAAA record. 2012.08.01 18:30:29
> Server Info      DDNS: AAAA update:crema42test.ipv6.osd.abg.fsc.net.
> -> fd12::b040:19c8:649a:cf0d 2012.08.01 18:30:29 Server Debug
> DDNS: DNS Update (add) successful.
> 
> Reverse resolving with nsupdate was successful:

Do you have reverse zone length specified correctly? While it is
possible to discover zone length (e.g. ISC DHCP does that), Dibbler does
not have support for it coded. Therefore you must explicitly specify
zone length. That's the second parameter passed to fqdn. It is typically
64, but it doesn't have to be.

> DNS-Server is on a SUSE SLES11 system (bind 9.5.0P2-20.1); Perhaps, 
> are there known problems in this combination ( DNS-Server - 
> dibbler-Server)?
What does the BIND log say?

Try to increase logging in your BIND setup if necessary. I'm no BIND
expert, but you will possibly have to tweak it, but the general way to
do that is:

channel ddns_log {
        file "/var/log/bind ddns.log";
        severity info; (or even debug)
        print-time yes;
        print-severity yes;
        print-category yes;
    };

    category update {
        ddns_log;
    };

Greetings from IETF meeting,
Tomek


More information about the Dibbler mailing list