Servidor DNS Dinamico NO registra Usuarios DHCP

Forums: 

Buenas noches.
Quisiera que me colaboraran con el tema del ASUNTO, tengo 1 DNS y DHCP en misma maquina, he estado leyendo que es posible que los usuarios de red a la vez que el servidor DHCP le asigna direccion este a su vez actualice el registro DNS pero estoy teniendo el siguiente problema que anexo en el Log.

[root@proxy ~]# tail -f /var/log/messages
Jul 1 20:35:00 proxy dhcpd: Unable to add forward map from ABOG01105992P.lacastellaza.co. to 192.168.127.173: connection refused
Jul 1 20:35:00 proxy dhcpd: DHCPREQUEST for 192.168.127.173 (192.168.127.180) from 00:1c:bf:68:0f:02 (ABOG01105992P) via eth1
Jul 1 20:35:00 proxy dhcpd: DHCPACK on 192.168.127.173 to 00:1c:bf:68:0f:02 (ABOG01105992P) via eth1
Jul 1 20:35:26 proxy clamd[3312]: SelfCheck: Database status OK.
Jul 1 20:39:20 proxy named[21412]: zone cache/IN: refresh: non-authoritative answer from master 4.2.2.3#53 (source 0.0.0.0#0)
Jul 1 20:39:21 proxy named[21412]: zone cache/IN: refresh: non-authoritative answer from master 4.2.2.2#53 (source 0.0.0.0#0)
Jul 1 20:41:44 proxy dhcpd: DHCPDISCOVER from 2c:a8:35:1f:7b:82 (BLACKBERRY-845A) via eth1
Jul 1 20:41:45 proxy dhcpd: DHCPOFFER on 192.168.127.164 to 2c:a8:35:1f:7b:82 (BLACKBERRY-845A) via eth1
Jul 1 20:41:51 proxy dhcpd: Unable to add forward map from BLACKBERRY-845A.lacastellaza.co. to 192.168.127.164: connection refused
Jul 1 20:41:51 proxy dhcpd: DHCPREQUEST for 192.168.127.164 (192.168.127.180) from 2c:a8:35:1f:7b:82 (BLACKBERRY-845A) via eth1
Jul 1 20:41:51 proxy dhcpd: DHCPACK on 192.168.127.164 to 2c:a8:35:1f:7b:82 (BLACKBERRY-845A) via eth1
Jul 1 20:46:36 proxy named[21412]: zone cache/IN: refresh: non-authoritative answer from master 4.2.2.3#53 (source 0.0.0.0#0)
Jul 1 20:46:37 proxy named[21412]: zone cache/IN: refresh: non-authoritative answer from master 4.2.2.2#53 (source 0.0.0.0#0)
Jul 1 20:49:57 proxy dhcpd: Unable to add forward map from JuanPablo-PC.lacastellaza.co. to 192.168.127.172: connection refused
Jul 1 20:49:57 proxy dhcpd: DHCPREQUEST for 192.168.127.172 from 00:21:5c:2d:30:b7 (JuanPablo-PC) via eth1
Jul 1 20:49:57 proxy dhcpd: DHCPACK on 192.168.127.172 to 00:21:5c:2d:30:b7 (JuanPablo-PC) via eth1
Jul 1 20:51:22 proxy dhcpd: Unable to add forward map from JuanPablo-PC.lacastellaza.co. to 192.168.127.172: connection refused
Jul 1 20:51:22 proxy dhcpd: DHCPREQUEST for 192.168.127.172 from 00:21:5c:2d:30:b7 (JuanPablo-PC) via eth1
Jul 1 20:51:22 proxy dhcpd: DHCPACK on 192.168.127.172 to 00:21:5c:2d:30:b7 (JuanPablo-PC) via eth1
__________________________________________________________________________________________________________

Jul 1 21:41:11 proxy dhcpd: DHCPINFORM from 192.168.127.172 via eth1
Jul 1 21:41:11 proxy dhcpd: DHCPACK to 192.168.127.172 (00:21:5c:2d:30:b7) via eth1
Jul 1 21:43:09 proxy named[21412]: network unreachable resolving 'certrevoc.vo.msecnd.net/A/IN': 2001:503:a83e::2:30#53
Jul 1 21:43:09 proxy named[21412]: network unreachable resolving 'm.gtld-servers.net/A/IN': 2001:503:ba3e::2:30#53
Jul 1 21:43:09 proxy named[21412]: network unreachable resolving 'm.gtld-servers.net/AAAA/IN': 2001:503:ba3e::2:30#53
Jul 1 21:45:25 proxy clamd[3312]: SelfCheck: Database status OK.
Jul 1 21:51:16 proxy dhcpd: DHCPDISCOVER from 2c:a8:35:1f:7b:82 (BLACKBERRY-845A) via eth1
Jul 1 21:51:17 proxy dhcpd: DHCPOFFER on 192.168.127.164 to 2c:a8:35:1f:7b:82 (BLACKBERRY-845A) via eth1
Jul 1 21:51:17 proxy dhcpd: Unable to add forward map from BLACKBERRY-845A.lacastellaza.co. to 192.168.127.164: connection refused
Jul 1 21:51:17 proxy dhcpd: DHCPREQUEST for 192.168.127.164 (192.168.127.180) from 2c:a8:35:1f:7b:82 (BLACKBERRY-845A) via eth1
Jul 1 21:51:17 proxy dhcpd: DHCPACK on 192.168.127.164 to 2c:a8:35:1f:7b:82 (BLACKBERRY-845A) via eth1
Jul 1 21:54:21 proxy named[21412]: loading configuration from '/etc/named.conf'
Jul 1 21:54:21 proxy named[21412]: using default UDP/IPv4 port range: [1024, 65535]
Jul 1 21:54:21 proxy named[21412]: using default UDP/IPv6 port range: [1024, 65535]
Jul 1 21:54:21 proxy named[21412]: the working directory is not writable
Jul 1 21:54:22 proxy named[21412]: /var/named/dynamics/127.168.192.in-addr.arpa.zone:10: ignoring out-of-zone data (166.127.168.192.in-addr.arpa)
Jul 1 21:54:22 proxy named[21412]: /var/named/dynamics/127.168.192.in-addr.arpa.zone:11: ignoring out-of-zone data (174.127.168.192.in-addr.arpa)
Jul 1 21:54:22 proxy named[21412]: /var/named/dynamics/127.168.192.in-addr.arpa.zone:12: ignoring out-of-zone data (168.127.168.192.in-addr.arpa)
Jul 1 21:54:22 proxy named[21412]: /var/named/dynamics/127.168.192.in-addr.arpa.zone:13: ignoring out-of-zone data (171.127.168.192.in-addr.arpa)
Jul 1 21:54:22 proxy named[21412]: zone 127.168.192.160.in-addr.arpa/IN: loaded serial 2009081505
Jul 1 21:54:23 proxy named[21412]: zone cache/IN: refresh: non-authoritative answer from master 4.2.2.3#53 (source 0.0.0.0#0)
Jul 1 21:54:23 proxy named[21412]: zone cache/IN: refresh: non-authoritative answer from master 4.2.2.2#53 (source 0.0.0.0#0)

Estuve leyendo informacion aqui mismo pero parece ser problemas de permisos, Pero NO encuentro en ningun lado el usuario DHCP
Alguna ayuda al respecto les agradesco..
ATT

DHCP.CONF include

Enviado por Mirrortech en

Imagen de Mirrortech

DHCP.CONF

include "/var/named/chroot/etc/rndc.key";
server-identifier proxy.lacastellaza.co;
ddns-update-style interim;
ddns-domainname "lacastellaza.co.";
ddns-rev-domainname "127.168.192.in-addr.arpa.";
ignore client-updates;
authoritative;
default-lease-time 86400;
max-lease-time 608400;
option domain-name "lacastellaza.co";
option ip-forwarding off;

zone localdomain. {
primary 127.0.0.1;
key rndckey;
}
zone 127.168.192.in-addr.arpa. {
primary 192.168.127.180;
key rndckey;
}
zone lacastellaza.co. {
primary 192.168.127.160;
key rndckey;
}
shared-network Leonel {
# Red Local LACASTELLAZA
subnet 192.168.127.160 netmask 255.255.255.224 {
option broadcast-address 192.168.127.191;
option domain-name-servers 192.168.127.185;
option routers 192.168.127.190;
option ntp-servers 200.23.51.205 , 132.248.81.29 , 148.234.7.30;
range 192.168.127.162 192.168.127.179;
}
}

NAMED.CONF

options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
allow-recursion {
127.0.0.1;
192.168.127.160/27;
};
forwarders {
4.2.2.2;
4.2.2.3;
8.8.4.4;
};
forward first;
listen-on port 53 {
192.168.127.185;
};
};

##include "/etc/named.rfc1912.zones";
##include "/etc/rndc.key";

controls {
inet 127.0.0.1 allow { 127.0.0.1; } keys { "rndckey"; };
};

zone "lacastellaza.co" {
type master;
notify yes;
file "/var/named//dynamics/lacastellaza.co.zone";
allow-update {key "rndckey";};
};
zone "160.127.168.192.in-addr.arpa" {
type master;
notify yes;
file "/var/named/dynamics/127.168.192.in-addr.arpa.zone";
allow-update {key "rndckey";};
};
zone "Forward" {
type forward;
forwarders {
4.2.2.3;
4.2.2.2;
};
};
zone "cache" {
type stub;
masters port 53 {
4.2.2.3;
4.2.2.2;
};
file "/var/named/slaves/cache.hosts";
};
zone "185.127.168.192.in-addr.arpa" {
type master;
file "/var/named/192.168.127.185.rev";
};