GREAT!
it works like a charm now, thanks!

On Friday 8 October 2010 15:32:25 Lyle Giese wrote:
> You are telling dhcp to talk to your DNS server at ip address
> 192.168.1.250 and it's not listening on that ip address. According to
> your named.conf, it's only listening on 127.0.0.1.
> 
> Plus you need an A record for ns.localzone.local.
> 
> Lyle Giese
> LCR Computer Services, Inc.
> 
> tangonig...@yahoo.it wrote:
> > hello everybody..
> > 
> > I was playing on my gentoo box: a couple of virtual machines, client and
> > dhcp/bind server.
> > both services do their job - separately. I tried to configure the dynamic
> > update, but my log said (weird things *highlighted):
> > 
> > named[17833]: starting BIND 9.4.3-P5 -u named -n 1
> > named[17833]: using up to 4096 sockets
> > named[17833]: loading configuration from '/etc/bind/named.conf'
> > *named[17833]: max open files (1024) is smaller than max sockets (4096)
> > named[17833]: listening on IPv4 interface lo, 127.0.0.1#53
> > *named[17833]: automatic empty zone: 0.IN-ADDR.ARPA
> > *named[17833]: automatic empty zone: 254.169.IN-ADDR.ARPA
> > *named[17833]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
> > *named[17833]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
> > *named[17833]: automatic empty zone:
> > 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
> > *named[17833]: automatic empty zone:
> > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
> > *named[17833]: automatic empty zone: D.F.IP6.ARPA
> > *named[17833]: automatic empty zone: 8.E.F.IP6.ARPA
> > *named[17833]: automatic empty zone: 9.E.F.IP6.ARPA
> > *named[17833]: automatic empty zone: A.E.F.IP6.ARPA
> > *named[17833]: automatic empty zone: B.E.F.IP6.ARPA
> > named[17833]: command channel listening on 127.0.0.1#953
> > named[17833]: zone 127.in-addr.arpa/IN: loaded serial 2008122601
> > amed[17833]: zone 1.168.192.in-addr.arpa/IN: loaded seril 50named[17833]:
> > zone localarea.local/IN: NS 'localarea.local' has no address records (A
> > or AAAA) named[17833]: zone localarea.local/IN: loaded serial 50
> > named[17833]: zone localhost/IN: loaded serial 2008122601
> > named[17833]: running
> > *dhcpd: Unable to add forward map from pc-0251.localarea.local. to
> > 192.168.1.4: connection refused
> > dhcpd: dhcp.c(3998): non-null pointer
> > dhcpd: DHCPREQUEST for 192.168.1.4 from 08:00:27:aa:f6:64 (pc-0251) via
> > eth0 dhcpd: DHCPACK on 192.168.1.4 to 08:00:27:aa:f6:64 (pc-0251) via
> > eth0 dhcpd: Unable to add forward map from pc-0251.localarea.local. to
> > 192.168.1.4: connection refused
> > dhcpd: dhcp.c(3998): non-null pointer
> > dhcpd: DHCPREQUEST for 192.168.1.4 from 08:00:27:aa:f6:64 (pc-0251) via
> > eth0 dhcpd: DHCPACK on 192.168.1.4 to 08:00:27:aa:f6:64 (pc-0251) via
> > eth0
> > 
> > I guess it was something wrong with my bind configuration, but google has
> > not been my friend this time :-)
> > 
> > I post also my bind config files:
> > 
> > ******
> > NAMED.CONF (192.168.1.0, domain localarea.local, server 192.168.1.250,
> > client hostname pc-0251)
> > ******
> > include "/etc/bind/rndc.key";
> > 
> > controls {
> > 
> >  inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
> >  };
> > 
> > options {
> > 
> >     directory "/var/bind";
> >     
> >     forwarders {
> >     
> >             62.94.0.41;
> >             62.94.0.42;
> >     
> >     };
> >     recursion       yes;
> >     version         "REFUSED";
> >     
> >     listen-on-v6 { none; };
> >     
> >         listen-on { 127.0.0.1; };
> >     
> >     pid-file "/var/run/named/named.pid";
> > 
> > };
> > 
> > zone "." IN {
> > 
> >     type hint;
> >     file "named.cache";
> > 
> > };
> > 
> > zone "localhost" IN {
> > 
> >     type master;
> >     file "pri/localhost.zone";
> >     allow-update { none; };
> >     notify no;
> > 
> > };
> > 
> > zone "127.in-addr.arpa" IN {
> > 
> >     type master;
> >     file "pri/127.zone";
> >     allow-update { none; };
> >     notify no;
> > 
> > };
> > 
> > zone "1.168.192.in-addr.arpa" {
> > 
> >     type master;
> >     file "pri/192.168.1.zone";
> >     allow-update { key "rndc-key"; };
> >     notify yes;
> > 
> > };
> > 
> > zone "localarea.local" {
> > 
> >     type master;
> >     file "pri/localarea.local.zone";
> >     allow-update { key "rndc-key"; };
> >     notify yes;
> > 
> > };
> > 
> > *****
> > LOCALAREA.LOCAL.ZONE
> > *****
> > $TTL 86400
> > @   IN      SOA     localarea.local.                root.localarea.local. ( 
> > 50 28800 
7200
> > 604800 86400 )
> > 
> >             NS      localarea.local.
> > 
> > pc-0250     IN      A       192.168.1.250
> > ns  IN      A       192.168.1.250
> > ldapsrv     IN      A       192.168.1.250
> > 
> > *****
> > 192.168.1.ZONE
> > *****
> > $TTL 86400
> > @   IN      SOA     localarea.local.        root.localarea.local. ( 50 
> > 28800 7200 
604800
> > 86400 )
> > 
> >             NS      localarea.local.
> > 
> > 250 IN      PTR     ns
> > 
> > 
> > and, just in case, my dhcpd.conf too:
> > 
> > server-identifier   server;
> > ddns-updates                on;
> > ddns-update-style   interim;
> > ddns-domainname             "localarea.local.";
> > ddns-rev-domainname "in-addr.arpa.";
> > ignore                      client-updates;
> > include                     "/etc/bind/rndc.key";
> > 
> > zone localarea.local. {
> > 
> >     primary 127.0.0.1;
> >     key rndc-key;
> > 
> > }
> > 
> > option                      domain-name             "localarea.local.";
> > option                      domain-name-servers     192.168.1.250, 
> > 62.94.0.41,
> > 62.94.0.42;
> > option                      ip-forwarding           off;
> > 
> > default-lease-time  600;
> > max-lease-time              7200;
> > 
> > authoritative;
> > log-facility                local7;
> > 
> > subnet 192.168.1.0 netmask 255.255.255.0 {
> > 
> >     range           192.168.1.251 192.168.1.254;
> >     option          broadcast-address       192.168.1.255;
> >     option          routers                 192.168.1.254;
> >     allow           unknown-clients;
> >     
> >     zone localarea.local. {
> >     
> >             primary 192.168.1.250;
> >             key     rndc-key;
> >     
> >     }
> >     
> >     zone 1.168.192.in-addr.arpa. {
> >     
> >             primary 192.168.1.250;
> >             key     rndc-key;
> >     
> >     }
> > 
> > }
> > 
> > 
> > Could somebody tell me why that 'connection refused' and where am I
> > wrong?
> > 
> > Thanks,
> > Stefano.
> > _______________________________________________
> > bind-users mailing list
> > bind-users@lists.isc.org
> > https://lists.isc.org/mailman/listinfo/bind-users
> 
> _______________________________________________
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to