DDNS update timed out

Danny Mayer mayer at gis.net
Tue Jan 29 01:44:08 UTC 2002


At 08:42 AM 1/28/02, Mark_Andrews at isc.org wrote:
> > zone "in-addr.arpa" {
> >          type master;
> >          file "100.168.192";
> >          allow-transfer { any; };
> >          allow-update { 192.168.100.45; 127.0.0.1; };
> > };
> >
> > /var/named/intra.imc
> > $ORIGIN .
> > $TTL 86400 ;
> > intra.imc.               IN      SOA     imcdt.intra.imc.
> > root.imcdt.intra.imc. (
> >                          2002012800      ; serial
> >                          28800   ; refresh
> >                          7200    ; retry
> >                          604800  ; expire
> >                          86400   ; minimum
> >                          )
> >                          NS      imcdt.intra.imc.
> > $ORIGIN intra.imc.
> > $TTL 3600       ;
> > imcdt                   A       192.168.100.47
> > localhost               A       127.0.0.1
> >
> >
> > /var/named/100.168.192
> > $TTL    86400   ;
> > imcdt.intra.imc.                IN      SOA     imcdt.intra.imc.
> > root.imcdt.intra.imc. (
> >                  2002012800      ; serial
> >                  28800   ; refresh
> >                  7200    ; retry
> >                  604800  ; expire
> >                  86400   ; minimum
> >                  )
> >
> > @               IN      NS      ns.imcdt.intra.imc.
> > 44              IN      PTR     imcdt.intra.imc.
> >
> > To be honest, I think I made a mistake in my zone files, but can't see
> > where.
>
>         The IP address for imcdt.intra.imc is wrong.

Actually, it's far worse than that. You claim to be authorative for the whole
"in-addr.arpa" zone.  The zone should be "100.168.192.in-addr.arpa".

         Danny



More information about the bind-users mailing list