LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 05-13-2005, 11:19 AM   #1
gkurts
LQ Newbie
 
Registered: Jan 2004
Posts: 3

Rep: Reputation: 0
Angry DHCP / DNS Trouble


I'm having trouble getting dhcp & dynamic dns working on a new server that I set up. Dhcp is assigning addresses properly and dns works, but dynamic dns isn't updating. Any help would be appreciated - config files and errors are below.... Thanks!

========================================
/etc/dhcpd.conf:
subnet 10.40.0.0 netmask 255.255.0.0 {
ddns-domainname "DELTA";
option nis-domain "DELTA";
ddns-rev-domainname "DELTA";
option time-servers 10.10.10.168;
max-lease-time 604800;
default-lease-time 604800;
option netbios-name-servers 10.10.10.168;
option domain-name-servers 10.40.34.254;
allow unknown-clients;
option domain-name "DELTA";
option subnet-mask 255.255.0.0;
ddns-updates on;
ddns-update-style ad-hoc;
range 10.40.34.1 10.40.34.253;
authoritative;
}

=======================
/etc/named.conf:
options {
directory "/var/lib/named";
forward first;
include "/etc/named.d/forwarders.conf";
};

zone "DELTA" {
type master;
file "DELTA.zone";
allow-query { any; localhost; localnets; };
allow-transfer { any; localhost; localnets; };
allow-update { any; localhost; localnets; };
};

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

zone "10.40.in-addr.arpa" {
type master;
file "10.40.in-addr.arpa.zone";
allow-query {any;};
allow-transfer {any;};
allow-update {any;};
};

zone "0.0.127.in-addr.arpa" {
type master;
file "127.0.0.zone";
};

============================
/var/lib/named/DELTA.zone:
$TTL 86400
$ORIGIN .
DELTA IN SOA DELTA. root.DELTA. (
2005051301 ; serial
28800 ; refresh
7200 ; retry
604800 ; expiry
86400 ) ; minimum

DELTA. IN NS 10.40.34.254.
$ORIGIN delta.
waltrip A 10.40.34.254
gk A 10.40.32.69
insight A 10.10.10.168
s1031534 A 10.40.33.5
isdir A 10.10.196.228

=========================
one of many of the same errors from /var/log/messages:
May 13 11:08:17 WALTRIP dhcpd: if Busoffice04.DELTA IN A rrset doesn't exist add Busoffice04.DELTA 302400 IN A 10.40.34.36: not a zone.
May 13 11:08:17 WALTRIP dhcpd: DHCPREQUEST for 10.40.34.36 from 00:02:e3:50:bf:7b (Busoffice04) via eth0
May 13 11:08:17 WALTRIP dhcpd: DHCPACK on 10.40.34.36 to 00:02:e3:50:bf:7b (Busoffice04) via eth0


I don't understand what it means by 'not a zone'. I've got DELTA set as a zone in named.conf and it's set authoritative in dhcpd.conf... Any ideas? I appreciate any help!!
 
Old 05-14-2005, 04:30 AM   #2
musicman_ace
Senior Member
 
Registered: May 2001
Location: Indiana
Distribution: Gentoo, Debian, RHEL, Slack
Posts: 1,555

Rep: Reputation: 46
ddns-update-style ad-hoc;

I've always seen this specified at the top of the config, not in the subnet declaration. maybe that has nothing to do with your problem, but my observation.
 
Old 05-14-2005, 05:41 AM   #3
scowles
Member
 
Registered: Sep 2004
Location: Texas, USA
Distribution: Fedora
Posts: 620

Rep: Reputation: 31
You have so many problems with your DNS zones there are just to many to list. See some of my other posts regarding DNS for some template examples.

A good starting point is your reverse zone definition:
Code:
zone "10.40.in-addr.arpa" {
type master;
This should be reversed (as the name implies):
Code:
zone "40.10.in-addr.arpa" {
type master;
Another starting point - you are specifing an IP address for the NS record for zone DELTA when this should be a FQDN that has a glue record (an address record) that points to the IP address.

As for the dhcpd.conf

1) The ddns-rev-domainname "DELTA"; needs to match the zone name as specifed in named.conf. i.e. 40.10.in-addr.arpa

2) Which zones are to be dynamically updated in dhcpd.conf?? Ex:
Code:
zone delta. {
       primary 127.0.0.1;
       key dhcp_updater;
}
 
zone 8.168.192.in-addr.arpa. {
         primary 127.0.0.1;
         key dhcp_updater;
       }
etc...

The command "dig" is your friend. Use this command to test your zone files. Make sure it returns the proper answer first before you move on to getting DDNS working. Ex:

dig delta soa
dig delta ns
dig waltrip.delta a
dig -x 10.40.34.254
 
Old 06-29-2009, 04:37 AM   #4
cam34
Member
 
Registered: Aug 2003
Distribution: OpenSuse 11.1, SLES10, Fedora 11 & XP 4 Gaming *sniffs
Posts: 101

Rep: Reputation: 16
Basically i had the same problem in my lab enviroment.
I had incorrect SOA's and incorrect :
IN NS records both forward and reverse and it then worked. (Dont forget to change the serials and reload :-p )
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCP and DNS Likosin Linux - Networking 1 11-13-2004 11:27 PM
forward dns from dhcp to dhcp Fark Linux - Networking 3 03-31-2004 10:40 AM
DHCP / DNS Help!! muzicman82 Linux - Wireless Networking 4 02-25-2004 04:59 PM
Dns / Dhcp TheRealDeal Linux - Networking 9 09-19-2003 04:57 AM
Dns +dhcp james.farrow Linux - Networking 1 07-04-2003 09:17 AM


All times are GMT -5. The time now is 09:33 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration