1

BIND and DHCPD are configured but as far as I can tell DHCPD makes no attempt to even send Dynamic DNS update to BIND. I can manually add records using nsupdate with the same key I have configured DHCPD to use.

Server:

eth0: 10.0.0.1 static (BIND and DHCPD) eth1: DHCPd assigned (external, different subnet)

Client:

eth0: DHCP assigned, same subnet as Server eth0

DHCPD Config:

authoritative; option domain-name "ops.ss"; option domain-name-servers testvm1.ops.ss; ddns-updates on; ddns-update-style interim; default-lease-time 3600; max-lease-time 7200; log-facility local6; key DDNS_UPDATE { algorithm HMAC-MD5.SIG-ALG.REG.INT; secret "manysecrets"; } zone ops.ss. { primary 127.0.0.1; key DDNS_UPDATE; } zone 0.0.10.in-addr.arpa. { primary 127.0.0.1; key DDNS_UPDATE; } subnet 10.0.0.0 netmask 255.255.255.0 { range 10.0.0.50 10.0.0.99; option routers 10.0.0.1; } 

BIND Config:

include "/etc/named/ddns.key"; acl trusted { 10.0.0.0/24; 127.0.0.0/8; localnets; localhost; }; options { listen-on port 53 { trusted; }; 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-query { trusted; }; forwarders { 192.168.1.2; }; }; logging { channel default_debug { file "data/named.run"; severity dynamic; }; channel update_log { file "data/bind-updates.log"; severity debug; print-category yes; print-severity yes; print-time yes; }; category update { update_log; }; category update-security { update_log; }; }; zone "." IN { type hint; file "named.ca"; }; zone "ops.ss" IN { type master; file "dynamic/fwd_ops.ss"; allow-update { key DDNS_UPDATE; }; }; zone "0.0.10.in-addr.arpa." { type master; file "dynamic/rev_10.0.0.0_24"; allow-update { key DDNS_UPDATE; }; }; include "/etc/named.rfc1912.zones"; include "/etc/named.root.key"; 

Both systems are CentOS 6.4 with bind and dhcp from @updates

3 Answers 3

1

DHCPD is not pushing updates to BIND because it does not know what DNS name to update since no DDNS hostname is defined.

0

According to the man page ddns-hostname does not need to be set.

 The ddns-hostname statement ddns-hostname name; The name parameter should be the hostname that will be used in set- ting up the client's A and PTR records. If no ddns-hostname is spec- ified in scope, then the server will derive the hostname automati- cally, using an algorithm that varies for each of the different update methods. 
0

Make sure the dhcp client is actually sending the hostname. In Ubuntu, the following option in dhclient.conf does this:

send host-name = gethostname(); 

Your named config seems fine, at first sight.

This is my setup for the DHCP server. I use RNDC key's:

subnet 192.168.20.0 netmask 255.255.255.0 { range 192.168.20.100 192.168.20.200; option subnet-mask 255.255.255.0; option routers 192.168.20.1; option domain-name-servers 192.168.20.201; option domain-name "srv.internal.mycompany.be"; ddns-domainname "srv.internal.mycompany.be."; ddns-rev-domainname "in-addr.arpa."; } 

make sure the ddns-domainname is specified, so it knows which zone records to update. Don't forget the extra "dot" at the end.

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.