DHCPD DDNS

Keith Bottner kbottner at barkinglizards.com
Tue Jun 27 14:23:35 UTC 2006


I am trying to have DHCPD update my DNS, however I keep receiving the
following error:
 
Unable to add forward map from Stile.mydomain.com to 192.168.1.14: timed out
 
I have read all of the documentation for both DHCPD and DNS, I have read
everything I could find through Google and no matter what I try I cannot
seem to achieve success. One difference that I notice, from quite a few of
the DDNS examples I see, is that my DNS server is not the same as my DHCPD
server. I realize this should not make a difference but.... Versions I am
running are:

ISC-DHCPD version 3.0.3
BIND version 9.3.1
FreeBSD 6.0

I would appreciate any help that anyone can offer. Thanks in advance.


 
My dhcpd.conf configuration is:
 
option domain-name "mydomain.com";
option domain-name-servers 192.168.1.215;

default-lease-time 86400;
max-lease-time 259200;

authoritative;

ddns-updates on;
ddns-domainname "mydomain.com.";
ddns-rev-domainname "in-addr.arpa.";
ddns-update-style interim;
allow client-updates;

key DHCP-UPDATE-KEY {
  algorithm hmac-md5;
  secret "secret-goes-here";
}

zone mydomain.com. {
  primary 192.168.1.215;
  key DHCP-UPDATE-KEY;
}

zone 1.168.192.in-addr.arpa. {
  primary 192.168.1.215;
  key DHCP-UPDATE-KEY;
}

log-facility syslog;

# DMZ network subnet declaration, no service will be given on this subnet,
# but declaring it helps the DHCP server to understand the network topology.
subnet 10.11.13.0 netmask 255.255.255.0 {
}

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.10 192.168.1.100;
  option domain-name-servers 192.168.1.215;
  option domain-name "mydomain.com";
  option routers 192.168.1.1;
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.1.255;
  default-lease-time 86400;
  max-lease-time 259200;
  use-host-decl-names on;
}

}

My DNS (bind) configuration is:

options {
	directory	"/etc/namedb";
	pid-file	"/var/run/named/pid";
	dump-file	"/var/dump/named_dump.db";
	statistics-file	"/var/stats/named.stats";

	listen-on	{ 192.168.1.215; };
};

logging {
	channel syslog_errors { syslog daemon; severity info; };

	channel mydomain_log {
	  file "/var/log/mydomain.log" versions 3 size 1m;
	  print-time yes;
          print-severity yes;
	  print-category yes;
	  severity dynamic;
	};

	category network { mydomain_log; };
	category notify { mydomain_log; };
	category resolver { mydomain_log; };
	category security { mydomain_log; };
	category update { mydomain_log; };
	category update-security { mydomain_log; };
};

key DHCP-UPDATE-KEY {
  algorithm hmac-md5;
  secret "secret-goes-here";
};

controls {
   inet 127.0.0.1
   allow { 127.0.0.1; 192.168.1.1; } keys { "DHCP-UPDATE-KEY"; };
};

view "INT" {
	match-clients { 192.168.1.0/24; 10.11.13.0/24; };
	recursion yes;

	zone "." {
	  type hint;
	  file "named.root";
	};

	zone "0.0.127.IN-ADDR.ARPA" in {
	  type master;
	  file "master/localhost.rev";
	};

	zone "1.168.192.IN-ADDR.ARPA" in {
	  type master;
	  file "/etc/namedb/dynamic/192.168.1.rev.internal";
	  notify yes;
	  allow-update { key DHCP-UPDATE-KEY; };
	};

	zone "mydomain.com" {
	  type master;
	  file "/etc/namedb/dynamic/master.mydomain.com.internal";
	  notify yes;
	  allow-update { key DHCP-UPDATE-KEY; };
	};

	zone "localhost" in {
	  type master;
	  file "master.localhost";
	};

};





More information about the dhcp-users mailing list