LinuxQuestions.org
Visit the LQ Articles and Editorials 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 06-16-2005, 09:46 PM   #1
Garbledwords
LQ Newbie
 
Registered: May 2005
Posts: 4

Rep: Reputation: 0
Question dynamic updating reverse-dns problem


HI,

I have a small home network, with my server running dhcp3 (V3.0.1) and bind9 (9.2.4) on ubuntu (5.04). I have managed to set it up to dynamically update dns through dhcp for my XP clients. However, I am at a block on getting the reverse dns updating to work. The message that is get in the syslog is:

Jun 16 21:20:13 rover dhcpd: Added new forward map from Bowser.garbledwords.lan to 192.168.0.10
Jun 16 21:20:13 rover dhcpd: unable to add reverse map from 10.0.168.192.in-addr.arpa. to Bowser.garbledwords.lan: not a zone


The first message show that the forward dns update works and the second shows that the reverse dns update fails saying that the zone that I have set up is "not a zone". But it really seems to be as when I add a static entry to this zone, it works fine. It is the dynamic update part that does not work. Could it be something to do with XP?

(And yes, I know I have no security for this. I was waiting on getting it working first before complicating things.)

I would appreciate any assistance with this problem. Thanks in advance.

Now for the long part - the config files (minus the comments):

dhcpd.conf
----------
ddns-update-style interim;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;

subnet 192.168.0.0 netmask 255.255.255.0 {
update-optimization off;
one-lease-per-client on;
server-name "rover.garbledwords.lan";
range 192.168.0.2 192.168.0.11;
option routers 192.168.0.1;
option domain-name-servers 192.168.0.1;
option netbios-name-servers 192.168.0.1;
option netbios-node-type 8;
ignore client-updates;
option broadcast-address 192.168.0.255;
option domain-name "garbledwords.lan";
}

----------

named.conf
----------
include "/etc/bind/named.conf.options";

zone "." {
type hint;
file "/etc/bind/db.root";
};

zone "localhost" {
type master;
file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};

include "/etc/bind/named.conf.local";

----------

named.conf.options
----------
options {
directory "/var/cache/bind";
auth-nxdomain no; # conform to RFC1035
listen-on { 127.0.0.1; 192.168.0.1; } ;
allow-query { 127.0.0.1; 192.168.0.0/24; } ;
};

----------

named.conf.local
----------
acl garbledwords.lan {
127.0.0.1;
192.168.0.0/24;
};

zone "garbledwords.lan." IN {
type master;
file "/etc/bind/zone.garbledwords.lan";
allow-update { garbledwords.lan; } ;
};

zone "0.168.192.in-addr.arpa." IN {
type master;
file "/etc/bind/zone.0.168.192";
allow-update { garbledwords.lan; } ;
};

----------

zone.0.168.192
----------
$TTL 300
@ IN SOA rover.garbledwords.lan. roy.garbledwords.net. (
1 ; Serial no., based on date
21600 ; Refresh after 6 hours
3600 ; Retry after 1 hour
604800 ; Expire after 7 days
3600 ; Minimum TTL of 1 hour
)
1 IN PTR rover
@ IN NS rover
10 IN PTR bowser
-----------

(A reverse dns lookup on bowser works (nslookup 192.168.0.10)).

-----------

The syslog messages during starting named/
-----------
Jun 16 21:36:52 rover named[30179]: starting BIND 9.2.4 -u bind
Jun 16 21:36:52 rover named[30179]: using 1 CPU
Jun 16 21:36:52 rover named[30179]: loading configuration from '/etc/bind/named.conf'
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface lo, 127.0.0.1#53
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface bridge, 192.168.0.1#53
Jun 16 21:36:52 rover named[30179]: zone 'garbledwords.lan.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: zone '0.168.192.in-addr.arpa.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: command channel listening on 127.0.0.1#953
Jun 16 21:36:52 rover named[30179]: command channel listening on ::1#953
Jun 16 21:36:52 rover named[30179]: zone 0.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 127.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 255.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone garbledwords.lan/IN: loaded serial 7
Jun 16 21:36:52 rover named[30179]: zone localhost/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: running
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 1)
Jun 16 21:36:52 rover named[30179]: starting BIND 9.2.4 -u bind
Jun 16 21:36:52 rover named[30179]: using 1 CPU
Jun 16 21:36:52 rover named[30179]: loading configuration from '/etc/bind/named.conf'
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface lo, 127.0.0.1#53
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface bridge, 192.168.0.1#53
Jun 16 21:36:52 rover named[30179]: zone 'garbledwords.lan.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: zone '0.168.192.in-addr.arpa.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: command channel listening on 127.0.0.1#953
Jun 16 21:36:52 rover named[30179]: command channel listening on ::1#953
Jun 16 21:36:52 rover named[30179]: starting BIND 9.2.4 -u bind
Jun 16 21:36:52 rover named[30179]: using 1 CPU
Jun 16 21:36:52 rover named[30179]: loading configuration from '/etc/bind/named.conf'
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface lo, 127.0.0.1#53
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface bridge, 192.168.0.1#53
Jun 16 21:36:52 rover named[30179]: zone 'garbledwords.lan.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: zone '0.168.192.in-addr.arpa.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: command channel listening on 127.0.0.1#953
Jun 16 21:36:52 rover named[30179]: command channel listening on ::1#953
Jun 16 21:36:52 rover named[30179]: zone 0.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 127.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 255.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone garbledwords.lan/IN: loaded serial 7
Jun 16 21:36:52 rover named[30179]: zone localhost/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: running
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 1)
Jun 16 21:36:52 rover named[30179]: zone 0.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 127.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 255.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone garbledwords.lan/IN: loaded serial 7
Jun 16 21:36:52 rover named[30179]: zone localhost/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: running
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 1)
 
Old 06-18-2005, 10:14 AM   #2
scowles
Member
 
Registered: Sep 2004
Location: Texas, USA
Distribution: Fedora
Posts: 620

Rep: Reputation: 31
Have you tried adding the "zone" statment for the reverse zone to dhcpd.conf? I have one for each zone (in named.conf) that I want dynamically updated. See: man dhcpd.conf (search for zone)

Other than the missing zone statements in dhcpd.conf, I don't see anything else wrong.
 
Old 06-18-2005, 01:00 PM   #3
Garbledwords
LQ Newbie
 
Registered: May 2005
Posts: 4

Original Poster
Rep: Reputation: 0
Thank you very much. I thought it would be very simple. I had seen this previously, but when the lookup for the name worked, I must have ignored putting the zones in dhcpd.conf or just thought I had.

Garbledwords
 
Old 06-24-2005, 01:05 PM   #4
tikky
LQ Newbie
 
Registered: Jun 2005
Posts: 1

Rep: Reputation: 0
Question

Can any of you specify where you have to add the "zone" statement for the reverse zone in dhcpd.conf file. It wasn't very clear from the context.
 
Old 06-24-2005, 03:04 PM   #5
Garbledwords
LQ Newbie
 
Registered: May 2005
Posts: 4

Original Poster
Rep: Reputation: 0
You can put the zone statement anywhere in the "global" section (that is, not in a subnet or other specific section).
 
  


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
DNS Reverse lookup problem pazvant Linux - Networking 3 10-10-2005 07:36 AM
Reverse DNS problem guanyu Linux - Networking 6 12-21-2003 04:47 AM
Postfix/Reverse DNS Problem otisthegbs Linux - Software 0 12-15-2003 02:05 PM
Mozilla problem with Dynamic DNS techrolla Linux - Networking 2 11-30-2003 05:26 PM
Reverse Dns Problem Hein-ZA Linux - Networking 2 07-15-2003 08:01 AM


All times are GMT -5. The time now is 11:40 PM.

Main Menu
Advertisement
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