خرید بک لینک

I've set up dhcp + bind9 ddns with allow updates by key

I keep getting this 'update unsuccessful' messages on syslog because the name already exists (from the previous dhcp renew) and I would like to confirm that those are informative and perfectly normal and, therefore, can be ignored by logcheck.

If the dhcp changed the ip of the lease, would the record be correctly updated? If not, how can I allow the replacement a name in use? And from the point of view of security, should I?

Code:

Jun  1 11:21:10 tutusrv dhcpd: DHCPREQUEST for 192.168.30.130 from 00:08:9b:c2:0b:1a via p4p1
Jun  1 11:21:10 tutusrv dhcpd: DHCPACK on 192.168.30.130 to 00:08:9b:c2:0b:1a via p4p1
Jun  1 11:21:10 tutusrv named[4504]: client 192.168.30.240#3336/key dc-key: updating zone 'tutu/IN': update unsuccessful: hssrv-bak.tutu: 'name not in use' prerequisite not satisfied (YXDOMAIN)
Jun  1 11:21:10 tutusrv named[4504]: client 192.168.30.240#3336/key dc-key: signer "dc-key" approved
Jun  1 11:21:10 tutusrv named[4504]: client 192.168.30.240#3336/key dc-key: updating zone 'tutu/IN': deleting rrset at 'hssrv-bak.tutu' A
Jun  1 11:21:10 tutusrv named[4504]: client 192.168.30.240#3336/key dc-key: updating zone 'tutu/IN': adding an RR at 'hssrv-bak.tutu' A
Jun  1 11:21:10 tutusrv dhcpd: Added new forward map from hssrv-bak.tututo 192.168.30.130
Jun  1 11:21:10 tutusrv named[4504]: client 192.168.30.240#3336/key dc-key: signer "dc-key" approved
Jun  1 11:21:10 tutusrv named[4504]: client 192.168.30.240#3336/key dc-key: updating zone '30.168.192.in-addr.arpa/IN': deleting rrset at '130.30.168.192.in-addr.arpa' PTR
Jun  1 11:21:10 tutusrv named[4504]: client 192.168.30.240#3336/key dc-key: updating zone '30.168.192.in-addr.arpa/IN': adding an RR at '130.30.168.192.in-addr.arpa' PTR
Jun  1 11:21:10 tutusrv dhcpd: Added reverse map from 130.30.168.192.in-addr.arpa. to hssrv-bak.tutu
Cheers

برچسب: نویسنده: استخدام کار تاريخ: پنجشنبه 13 خرداد 1395 ساعت: 17:53

صفحه بندی