I am trying to get dhcpd to add a forward to named for local computers. Dhcpd is timing out when it is trying to add the forward map.
I have set the zone files to bind and edited /etc/mtree/BIND.chroot.dist to this. Before this i got the working directory is not writable error.
I have been trying to fix this for a few weeks now and trying other settings but still having the same problems.
here is my config files
dhcpd.conf
named.conf
Code:
dhcpd: Unable to add forward map from web.system.lan to 10.0.0.2: timed outI have set the zone files to bind and edited /etc/mtree/BIND.chroot.dist to this. Before this i got the working directory is not writable error.
Code:
# $FreeBSD: src/etc/mtree/BIND.chroot.dist,v 1.6.20.1 2009/04/15 03:14:26 kensmith Exp $
#
# Please see the file src/etc/mtree/README before making changes to this file.
#
#/set type=dir uname=root gname=wheel mode=0755
/set type=dir uname=bind gname=wheel mode=0755
.
dev mode=0555
..
etc
namedb
dynamic uname=bind
..
master
..
slave uname=bind
..
..
..
/set type=dir uname=bind gname=wheel mode=0755
var uname=root
dump
..
log
..
run
named
..
..
stats
..
..
..here is my config files
dhcpd.conf
Code:
ddns-domainname "system.lan";
option domain-name-servers 10.0.0.1;
option routers 10.0.0.1;
option broadcast-address 10.0.0.255;
ddns-update-style interim;
update-static-leases on;
key dhcpupdate {
algorithm hmac-md5;
secret key-string;
}
authoritative;
zone system.lan. {
primary 127.0.0.1;
key dhcpupdate;
}
zone 0.0.10.in-addr.arpa. {
primary 10.0.0.1;
key dhcpupdate;
}
subnet 10.0.0.0 netmask 255.255.255.0 {
range 10.0.0.100 10.0.0.150;
option subnet-mask 255.255.255.0;
option routers 10.0.0.1;
option domain-name-servers 10.0.0.1;
allow unknown-clients;
}
host web.system.lan {
hardware ethernet 00:02:03:04:05:06;
fixed-address 10.0.0.2;
ddns-hostname "web";
ddns-domainname "system.lan";
option host-name "web";
option domain-name "system.lan";
}named.conf
Code:
// $FreeBSD: src/etc/namedb/named.conf,v 1.26.2.2.4.1 2009/04/15 03:14:26 kensmith Exp $
//
// Refer to the named.conf(5) and named(8) man pages, and the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.
options {
// Relative to the chroot directory, if any
directory "/etc/namedb";
pid-file "/var/run/named/pid";
dump-file "/var/dump/named_dump.db";
statistics-file "/var/stats/named.stats";
// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
listen-on { 127.0.0.1; 10.0.0.1; };
};
// The traditional root hints mechanism. Use this, OR the slave zones below.
zone "." { type hint; file "named.root"; };
key dhcpupdate {
algorithm hmac-md5;
secret "key-string";
};
zone "system.lan." {
type master;
//file "master/db-system.lan";
file "/etc/namedb/system.lan.db";
allow-update { key dhcpupdate; };
};
zone "0.0.10.in-addr.arpa." {
type master;
file "/etc/namedb/system.lan.rev.db";
allow-update { key dhcpupdate; };
};