Dhcp3 not updating bind9

Rated 3.88/5 based on 980 customer reviews

to 172.16.2.105: connection refused Aug 18 cortex dhcpd: DHCPREQUEST for 172.16.2.105 from :4a::e9 (i Phone) via eth0 Aug 18 cortex dhcpd: DHCPACK on 172.16.2.105 to :4a::e9 (i Phone) via eth0 Aug 18 cortex dhcpd: DHCPREQUEST for 172.16.2.111 from :62:f4:f4 via eth0 Aug 18 cortex dhcpd: DHCPACK on 172.16.2.111 to :62:f4:f4 via eth0 Aug 18 cortex dhcpd: DHCPREQUEST for 172.16.2.111 from :62:f4:f4 via eth0 Aug 18 cortex dhcpd: DHCPACK on 172.16.2.111 to :62:f4:f4 via eth0 Aug 18 cortex dhcpd: DHCPREQUEST for 172.16.2.111 from :62:f4:f4 via eth0 I would prefer to keep DHCP and BIND on different machines.it seems odd to me that they would have to be on the same machines. You just published the keys to your DNS server on the internet....to 172.16.2.105: connection refused Aug 18 cortex dhcpd: DHCPREQUEST for 172.16.2.105 from :4a::e9 (i Phone) via eth0 Aug 18 cortex dhcpd: DHCPACK on 172.16.2.105 to :4a::e9 (i Phone) via eth0 Aug 18 cortex dhcpd: Unable to add forward map from i Phone.to 172.16.2.105: connection refused Aug 18 cortex dhcpd: DHCPREQUEST for 172.16.2.105 from :4a::e9 (i Phone) via eth0 Aug 18 cortex dhcpd: DHCPACK on 172.16.2.105 to :4a::e9 (i Phone) via eth0 Aug 18 cortex dhcpd: DHCPREQUEST for 172.16.2.111 from :62:f4:f4 via eth0 Aug 18 cortex dhcpd: DHCPACK on 172.16.2.111 to :62:f4:f4 via eth0 Aug 18 cortex dhcpd: Wrote 11 leases to leases file.

key DHCP_UPDATER ; // // Do any local configuration here // // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; # Our domain zone zone "homelinux.com" ; # For reverse DNS zone "2.16.172.in-addr.arpa" ; [email protected]:/etc/bind$ cat options options ; [email protected]:/etc/bind$ cortex.DHCP [email protected]:/etc/dhcp3$ cat # # Sample configuration file for ISC dhcpd for Debian # # Attention: If /etc/ltsp/exists, that will be used as # configuration file instead of this file.#host fantasia # You can declare a class of clients and then do address allocation # based on that.The example below shows a case where all clients # in a certain class get addresses on the /24 subnet, and all # other clients get addresses on the 10.0.29/24 subnet.# Hosts for which fixed IP addresses have been specified can boot using # BOOTP or DHCP.Hosts for which no fixed address is specified can only # be booted with DHCP, unless there is an address range on the subnet # to which a BOOTP client is connected which has the dynamic-bootp flag # set.

Leave a Reply