DHCP, Bind9 and DDNS setup
Hi All, [SuSE9.0 Bind-9.2.2-31 dhcp-server-3.0.1rc12-13] I'm trying to set up dhcpd and bind to provide dynamic dns here at home. DHCP is working fine wrt assigning IP addresses to a test box, and dns is likewise responding correctly to digs for the single defined entry. I have followed the DDNS instructions in /usr/share/doc/packages/dhcp-server as well as taking note or the chrood info in the dhcp and bind readmes. Files have the following ownership and permissions: /etc/dhcp.conf root:root rw-r--r-- /etc/named.conf root:named rw-r----- /etc/named.keys root:named rw-r--r-- /var/lib/named/dyn/[dylan.me.uk.zone | 0.168.192.in-addr.arpa] named:named rw-rw-r-- directory /var/lib/named/dyn had named:named drwxr-xr-x Both chroot jails have a copy of /etc/named.keys I have uploded dhcpd.conf, named.conf, dylan.me.uk.zone and 192.168.0.zone to www.dylan.me.uk Any assistance / suggestions would be most welcome. Thanks Dylan -- "I see your Schwartz is as big as mine" -Dark Helmet
On Wed, May 05, 2004 at 07:15:01PM +0100, Dylan wrote:
Hi All,
[SuSE9.0 Bind-9.2.2-31 dhcp-server-3.0.1rc12-13]
I'm trying to set up dhcpd and bind to provide dynamic dns here at home. DHCP is working fine wrt assigning IP addresses to a test box, and dns is likewise responding correctly to digs for the single defined entry.
[...]
/etc/named.conf root:named rw-r----- /etc/named.keys root:named rw-r--r--
That's wrong: named.keys is the one that must not be world readable, not named.conf!
named:named rw-rw-r--
directory /var/lib/named/dyn had named:named drwxr-xr-x
Both chroot jails have a copy of /etc/named.keys
I have uploded dhcpd.conf, named.conf, dylan.me.uk.zone and 192.168.0.zone to www.dylan.me.uk
I see only dhcpd.conf and named.conf, and can't access the latter. You should not add the key to dhcpd.conf itself -- instead include the file /etc/named.keys. Read the DDNS howto again. Peter
On Thursday 06 May 2004 15:05 pm, poeml@cmdline.net wrote:
On Wed, May 05, 2004 at 07:15:01PM +0100, Dylan wrote:
Hi All,
[SuSE9.0 Bind-9.2.2-31 dhcp-server-3.0.1rc12-13]
I'm trying to set up dhcpd and bind to provide dynamic dns here at home. DHCP is working fine wrt assigning IP addresses to a test box, and dns is likewise responding correctly to digs for the single defined entry.
[...]
/etc/named.conf root:named rw-r----- /etc/named.keys root:named rw-r--r--
That's wrong: named.keys is the one that must not be world readable, not named.conf!
If named.keys is not workd readable then dhcpd cannot read it since it is set by default to run as nobody:nogroup.
named:named rw-rw-r--
directory /var/lib/named/dyn had named:named drwxr-xr-x
Both chroot jails have a copy of /etc/named.keys
I have uploded dhcpd.conf, named.conf, dylan.me.uk.zone and 192.168.0.zone to www.dylan.me.uk
I see only dhcpd.conf and named.conf, and can't access the latter. You should not add the key to dhcpd.conf itself -- instead include the file /etc/named.keys.
That's because I have changed the uploaded files as a result of other lines of inquiry.
Read the DDNS howto again.
I have, several times. Dylan
Peter
-- "I see your Schwartz is as big as mine" -Dark Helmet
Here is a working copy of dhcpd.conf and named.conf
skyline:/var/lib # cat /etc/dhcpd.conf
ddns-updates on;
ddns-update-style interim;
ignore client-updates;
include "/etc/named.keys";
subnet 192.168.6.0 netmask 255.255.255.0 {
option routers 192.168.6.13;
option subnet-mask 255.255.255.0;
option domain-name "3111skyline.com";
option domain-name-servers 192.168.6.14;
option netbios-name-servers 192.168.6.14;
ddns-domainname "3111skyline.com";
ddns-rev-domainname "6.168.192.in-addr.arpa";
range dynamic-bootp 192.168.6.80 192.168.6.100;
default-lease-time 21600;
max-lease-time 172800;
# Adding zone information
zone 3111skyline.com. {primary 127.0.0.1; key DHCP_UPDATER; }
zone 6.168.192.in-addr.arpa. { primary 127.0.0.1; key
DHCP_UPDATER; }
skyline:/var/lib # cat /etc/named.conf
include "/etc/named.keys";
include "/etc/rndc.key";
controls {
inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
};
options {
directory "/var/lib/named";
forward first;
forwarders { 66.76.2.130; 208.180.1.69;};
// query-source address * port 53;
};
zone "." {
type hint;
file "root.hint";
};
zone "localhost" {
type master;
file "localhost";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "127.0.0";
};
zone "3111skyline.com" {
type master;
file "dyn/3111skyline.com";
allow-update{ key DHCP_UPDATER; };
};
zone "6.168.192.in-addr.arpa" {
type master;
file "dyn/192.168.6";
allow-update{ key DHCP_UPDATER; };
};
--
David C. Rankin, J.D., P.E.
RANKIN * BERTIN, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankin-bertin.com
--
----- Original Message -----
From: "Dylan"
On Wed, May 05, 2004 at 07:15:01PM +0100, Dylan wrote:
Hi All,
[SuSE9.0 Bind-9.2.2-31 dhcp-server-3.0.1rc12-13]
I'm trying to set up dhcpd and bind to provide dynamic dns here at home. DHCP is working fine wrt assigning IP addresses to a test box, and dns is likewise responding correctly to digs for the single defined entry.
[...]
/etc/named.conf root:named rw-r----- /etc/named.keys root:named rw-r--r--
That's wrong: named.keys is the one that must not be world readable, not named.conf!
If named.keys is not workd readable then dhcpd cannot read it since it is set by default to run as nobody:nogroup.
named:named rw-rw-r--
directory /var/lib/named/dyn had named:named drwxr-xr-x
Both chroot jails have a copy of /etc/named.keys
I have uploded dhcpd.conf, named.conf, dylan.me.uk.zone and 192.168.0.zone to www.dylan.me.uk
I see only dhcpd.conf and named.conf, and can't access the latter. You should not add the key to dhcpd.conf itself -- instead include the file /etc/named.keys.
That's because I have changed the uploaded files as a result of other lines of inquiry.
Read the DDNS howto again.
I have, several times. Dylan
Peter
-- "I see your Schwartz is as big as mine" -Dark Helmet -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thu, May 06, 2004 at 03:51:42PM +0100, Dylan wrote:
On Thursday 06 May 2004 15:05 pm, poeml@cmdline.net wrote:
On Wed, May 05, 2004 at 07:15:01PM +0100, Dylan wrote:
/etc/named.conf root:named rw-r----- /etc/named.keys root:named rw-r--r--
That's wrong: named.keys is the one that must not be world readable, not named.conf!
If named.keys is not workd readable then dhcpd cannot read it since it is set by default to run as nobody:nogroup.
Untrue. This is only your assumption. To explain that, it reads the configuration while still being root, i.e. before changing user id to nobody. It never needs to read the file again after that, because dhcpd does not support a "reload".
You should not add the key to dhcpd.conf itself -- instead include the file /etc/named.keys.
That's because I have changed the uploaded files as a result of other lines of inquiry.
Read the DDNS howto again.
I have, several times.
Well, if you'd follow it _exactly_, I would be interested to learn what doesn't work for you. :) Peter
participants (3)
-
David Rankin -
Dylan -
poeml＠cmdline.net