Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Dec 2003 21:37:14 -0500
From:      Benjo <benjo@brokenzero.com>
To:        freebsd-questions@freebsd.org
Subject:   nis, dhcp and dynamic dns updates
Message-ID:  <20031218213714.299b8a29.benjo@brokenzero.com>

next in thread | raw e-mail | index | archive | help
greetings all,
  this is kinda messy so please bear with me.  i have a fairly large LAN
set up on 10.60.37.0/24 class c.  there's a router at 10.60.37.1,
there's an nis/dhcp server on 10.60.37.59 that also holds my users'
homedirs which are mounted to the workstations over NFS.  let me note
here that i suspect the problem i'm having may be related to the nis/yp
service but i cannot disable it because that is how my users
authenticate...it is too big a network to use local logins on all the
machines.  and finally, there is a dns server (bind named 8.2.4) at
10.60.37.60 that also uses rsync to back up the homedirs from other
machines and runs a few daily maintenance crons.  the problem i'm having
is that i would like the dhcp server to update the dns server so i can
resolve internal hostnames.  and the really weird thing is that it works
for the couple windows machines on the network...but not for any of the
FreeBSD machines....

ok so here are the settings and whatnot that i'm using:
both the nis/dhcp machine and the dns machine are FreeBSD 4.4
most of the clients are FreeBSD 5.1 but there are a scattering of
anything from 4.7 up.

here is the dhcpd.conf on 10.60.37.59

option domain-name "internal.blah.com";
option domain-name-servers 10.60.37.60,207.69.188.187;
option subnet-mask 255.255.255.0;

default-lease-time 3600;
max-lease-time 86400;
ddns-update-style interim;

zone internal.blah.com. {
        primary 10.60.37.60;
}

zone 37.60.10.in-addr.arpa. {
        primary 10.60.37.60;
}

subnet 10.60.37.0 netmask 255.255.255.0 {
  range 10.60.37.129 10.60.37.254;
  option routers 10.60.37.1;
}

here is the named.conf on 10.60.37.60

options {
        directory "/etc/namedb";

        forwarders {
                207.69.188.186;
                207.69.188.187;
        };
};

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

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

zone
"0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT"
{        type master;
        file "localhost.rev";
};

zone "internal.blah.com" {
        type master;
        file "internal.blah.com";
        allow-update {
                localnets;
        };
};

zone "37.60.10.in-addr.arpa" {
        type master;
        file "37.60.10.in-addr.arpa";
        allow-update {
                localnets;  //i have tried 10.60.37.0/24 also
        };
};

from /var/log/messages on the dns machine:

Dec 18 20:08:06 nfs2 named[97796]: starting (/etc/namedb/named.conf). 
named 8.2.4-REL Tue Sep 18 09:51:38 PDT 2001    
murray@builder.FreeBSD.org:/usr/obj/usr/src/usr.sbin/named 
Dec 18 20:08:06 nfs2 named[97796]: limit files set to fdlimit (1024) 
Dec 18 20:08:06 nfs2 named[97796]: dynamic zone file
'37.60.10.in-addr.arpa' is writable 
Dec 18 20:08:06 nfs2 named[97797]: Ready to answer queries. 
Dec 18 20:08:06 nfs2 named[97797]: check_hints: A records for
J.ROOT-SERVERS.NET class 1 do not match hint records

meanwhile the dhcp machine is giving me this:

Dec 18 13:48:35 webhost dhcpd: unable to add reverse map from
253.37.60.10.in-addr.arpa. to hbg07-swtest.internal.blah.com: timed
out 
Dec 18 13:48:36 webhost ypserv[144]: res_mkquery failed
Dec 18 13:49:09 webhost last message repeated 14 times
Dec 18 13:51:10 webhost last message repeated 49 times
Dec 18 14:01:11 webhost last message repeated 240 times
Dec 18 14:11:12 webhost last message repeated 239 times
etc, etc, ad nauseum.

so, since i was not getting ypserv errors before attempting to have the
DHCP update the DNS and the DNS updates are not happening, i can only
assume that somehow ypserv is hosing the deal.  what i can't figure out
is why ypserv would even be involved in it and more importantly how to
fix it w/o disabling NIS.

i strongly suspect there's something dumb i missed but i've been staring
at it too long to see it.

any suggestions greatly appreciated!

ben w



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031218213714.299b8a29.benjo>