dynamic zones not working in ddns config on ubuntu server

Dear Experts:

configured ddns on ubuntu server using dhcp and bind packages , static amd dynamic zones are placed under /var/cache/bind (static zones) and /var/cache/bind/(dynamic zones) both dhcp and bind services started resolve is happening for the hosts confiigured for the static zones but dynamic zones are not working , var/log/syslog is attached for your reference , please help me to reslove this. Thanks
dynamic-zones.txt
D_wathiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PapertripCommented:
Hey D,

Let's see your dhcpd.conf please, you know the drill :)
0
PapertripCommented:
Oct  7 09:29:23 lampsrv dhcpd: Unable to add forward map from reception.shriramdb.com dyn.shriramdb.com to 192.168.1.153: timed out

Open in new window


The problem here is option domain-name

Only put 1 domain there.  Technically having more than 1 domain in the search list for resolv.conf is fine... however, it is not fine in dhcpd.conf -- that was my bad I misunderstood the limitations of that option.

option domain-name text;
This option specifies the domain name that client should use when resolving hostnames via the Domain Name System.
0
PapertripCommented:
This is the correct option for what I was thinking of from one of your previous questions -- sorry!  You don't need to set this for now, just get the basics working first :)

option domain-search domain-list;
The domain-search option specifies a 'search list' of Domain Names to be used by the client to locate not-fully-qualified domain names. The difference between this option and historic use of the domain-name option for the same ends is that this option is encoded in RFC1035 compressed labels on the wire. For example:

option domain-search "example.com", "sales.example.com",
                     "eng.example.com";

0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

D_wathiAuthor Commented:
Sir, thanks for the reply. chaged to dyn.shriramdb.com . is this correct or should i put shriramdb.com, still the same logs are getting generated
--------------dhcpd.conf-----------------------------------------
ddns-update-style interim;
include "/etc/bind/ddns.key";
#include "/etc/bind/rndc.key";

zone dyn.shriramdb.com. {
primary 192.168.1.244;
key "ddns-key";
}

zone 2.168.192.in-addr.arpa. {
primary 192.168.1.244;
key "ddns-key";
}

# option definitions common to all supported networks...
option domain-name "dyn.shriramdb.com";            
option domain-name-servers 192.168.1.244;
option routers 192.168.1.244;
option broadcast-address 192.168.1.255;
option ntp-servers 192.168.1.244;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.150 192.168.1.200;
}
---------------------------------------------------------------------------------
var/log/syslogOct  7 10:11:30 lampsrv dhcpd: Unable to add forward map from james.dyn.shriramdb.com to 192.168.1.154: timed out
Oct  7 10:11:30 lampsrv dhcpd: DHCPREQUEST for 192.168.1.154 from 00:19:d1:1e:dd:83 (james) via eth0
Oct  7 10:11:30 lampsrv dhcpd: DHCPACK on 192.168.1.154 to 00:19:d1:1e:dd:83 (james) via eth0
Oct  7 10:11:37 lampsrv dhcpd: Unable to add forward map from sudha.dyn.shriramdb.com to 192.168.1.167: timed out
Oct  7 10:11:37 lampsrv dhcpd: DHCPREQUEST for 192.168.1.167 from 00:19:d1:61:84:a2 (sudha) via eth0
Oct  7 10:11:37 lampsrv dhcpd: DHCPACK on 192.168.1.167 to 00:19:d1:61:84:a2 (sudha) via eth0
Oct  7 10:11:54 lampsrv dhcpd: Unable to add forward map from geetha.dyn.shriramdb.com to 192.168.1.160: timed out
Oct  7 10:11:54 lampsrv dhcpd: DHCPREQUEST for 192.168.1.160 from 00:0f:ea:42:b4:76 (geetha) via eth0
Oct  7 10:11:54 lampsrv dhcpd: DHCPACK on 192.168.1.160 to 00:0f:ea:42:b4:76 (geetha) via eth0
Oct  7 10:12:06 lampsrv dhcpd: DHCPREQUEST for 192.168.1.201 from 00:19:d1:61:60:02 via eth0: unknown lease 192.168.1.201.
-------------------------
Please help

                                                                     

0
PapertripCommented:
The domain to put for 'option domain-name' should match the dynamic zone in named.conf that is configured to accept A record updates from dhcpd.  
0
PapertripCommented:
Hah my last reply was written same time as your last reply.  I have not read your recent comment yet, I will now.
0
PapertripCommented:
OK I see two problems.

First one is 'timed out' -- are you sure named is running on 192.168.1.244 ?  Can you telnet to 192.168.1.244:53 and get a connection?

Second is that your zone statement for the arpa zone does not match the zone that you are assigning IP's to.

zone 2.168.192.in-addr.arpa. {
primary 192.168.1.244;
key "ddns-key";
}
subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.150 192.168.1.200;
}
0
D_wathiAuthor Commented:
SIr, thanks for the reply changed the range from 192.168.1.0 192.168.1.245

also changed stopped dhcpd service and restarted bind, with this log shows as below:
 sudo tail -f /var/log/syslog
Oct  7 10:52:24 lampsrv named[4227]: zone 0.in-addr.arpa/IN: loaded serial 1
Oct  7 10:52:24 lampsrv named[4227]: zone 127.in-addr.arpa/IN: loaded serial 1
Oct  7 10:52:24 lampsrv named[4227]: zone 1.168.192.in-addr.arpa/IN: loaded serial 4
Oct  7 10:52:24 lampsrv named[4227]: zone 2.168.192.in-addr.arpa/IN: loaded serial 11
Oct  7 10:52:24 lampsrv named[4227]: zone 255.in-addr.arpa/IN: loaded serial 1
Oct  7 10:52:24 lampsrv named[4227]: zone shriramdb.com/IN: loaded serial 4
Oct  7 10:52:24 lampsrv named[4227]: zone dyn.shriramdb.com/IN: journal rollforward failed: journal out of sync with zone
Oct  7 10:52:24 lampsrv named[4227]: zone dyn.shriramdb.com/IN: not loaded due to errors.
Oct  7 10:52:24 lampsrv named[4227]: zone localhost/IN: loaded serial 2
Oct  7 10:52:24 lampsrv named[4227]: running
------------------------------------------------------------------------------------------------------------------------------------
also posted below dynamic zones

cat db.dyn.shriramdb.com
$ORIGIN .
$TTL 604800     ; 1 week
dyn.shriramdb.com       IN SOA  lampsrv.shriramdb.com. root.shriramdb.com. (
                                11          ; serial
                                604800     ; refresh (1 week)
                                86400      ; retry (1 day)
                                2419200    ; expire (4 weeks)
                                604800     ; minimum (1 week)
                                )
                        NS      lampsrv.shriramdb.com.
                IN      A       192.168.1.244
---------------------------------------------------------------------------
cat db.2.168.192.in-addr.arpa
;
; BIND reverse data file for local loopback interface
;
$TTL    604800
@       IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. (
                             11         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
        IN      NS      lampsrv.shriramdb.com.
244     IN      PTR     lampsrv.shriramdb.com.
;1.0.0  IN      PTR     localhost.
-------------------------------------------------------------------------------------------------------------------------
Please help
0
PapertripCommented:
Oct  7 10:52:24 lampsrv named[4227]: zone dyn.shriramdb.com/IN: journal rollforward failed: journal out of sync with zone

Open in new window


This can be caused by several things, but my guess is that you manually updated the serial without first freezing the zones.  Each entry in the journal file has a new serial.  So let's say the most recent serial in the journal file is 15, but you manually updated it from 10 to 11 -- that will cause this error.

Let's see what is in your journal file.
named-journalprint dyn.shriramdb.com

Open in new window

0
D_wathiAuthor Commented:
Sir, thanks.
evey time when i do changes manually i used to update the serial key in the zones.

also i found one line missing A record in the dynamic forward zone which i had actually created but once the journal got created this line was missing hence added the same, like the below:
cat db.dyn.shriramdb.com
$ORIGIN .
$TTL 604800     ; 1 week
dyn.shriramdb.com       IN SOA  lampsrv.shriramdb.com. root.shriramdb.com. (
                                11          ; serial
                                604800     ; refresh (1 week)
                                86400      ; retry (1 day)
                                2419200    ; expire (4 weeks)
                                604800     ; minimum (1 week)
                                )
                        NS      lampsrv.shriramdb.com.
                IN      A       192.168.1.244
--------------------------------------------------------------------
also  please find the below jounal file details

named-journalprint db.dyn.shriramdb.com.jnl
del dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 2 604800 86400 2419200 604800
add dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 3 604800 86400 2419200 604800
add pavitra.dyn.shriramdb.com. 300      IN      A       192.168.1.78
add pavitra.dyn.shriramdb.com. 300      IN      TXT     "31b9a2ac8eebddb90fc236ebe2439756aa"
del dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 3 604800 86400 2419200 604800
del pavitra.dyn.shriramdb.com. 300      IN      A       192.168.1.78
add dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 4 604800 86400 2419200 604800
add pavitra.dyn.shriramdb.com. 300      IN      A       192.168.1.11
del dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 4 604800 86400 2419200 604800
del pavitra.dyn.shriramdb.com. 300      IN      A       192.168.1.11
add dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 5 604800 86400 2419200 604800
del dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 5 604800 86400 2419200 604800
del pavitra.dyn.shriramdb.com. 300      IN      TXT     "31b9a2ac8eebddb90fc236ebe2439756aa"
add dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 6 604800 86400 2419200 604800
del dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 6 604800 86400 2419200 604800
add dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 7 604800 86400 2419200 604800
add SENTHILVEL.dyn.shriramdb.com. 300 IN        A       192.168.1.12
add SENTHILVEL.dyn.shriramdb.com. 300 IN        TXT     "319595c99ef27a9fc2a1f77e72b84f02a8"
del dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 7 604800 86400 2419200 604800
del SENTHILVEL.dyn.shriramdb.com. 300 IN        A       192.168.1.12
add dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 8 604800 86400 2419200 604800
del dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 8 604800 86400 2419200 604800
del SENTHILVEL.dyn.shriramdb.com. 300 IN        TXT     "319595c99ef27a9fc2a1f77e72b84f02a8"
add dyn.shriramdb.com.  604800  IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. 9 604800 86400 2419200 604800
-------------------------------------
Please help






0
PapertripCommented:
You can't manually update dynamic zones without freezing it first to commit the journal changes to the zone file, or you will run into this exact problem.  You should be using nsupdate to add/delete records in dynamic zones.

IF, however, you MUST edit it manually (you almost never should need to), then you must freeze, edit, thaw.  I must stress -- use nsupdate for external zones!!!  One of the main reasons for using nsupdate on dynamic zones is to help counter human error while editing -- I explained all of this in a previous question of yours.
rndc freeze domain.com
vi domain.com
rndc thaw domain.com

Open in new window


To fix this:
edit the zone file without freezing it first
change serial to 1 and save
rndc freeze dyn.shriramdb.com
rndc thaw dyn.shriramdb.com
named-checkzone dyn.shriramdb.com dyn.shriramdb.com

Open in new window


Again --- use nsupdate, do not edit manually unless absolutely necessary.  nsupdate is very, very easy to use.  I actually just added a record to one of my own zones:

[root@broken ~]# nsupdate -l
> update add www.domain.com 300 in a 201.25.69.114
> send
> quit

Open in new window


Yes, it's that easy.

http://consultancy.edvoncken.net/index.php/HOWTO_Manage_Dynamic_DNS_with_nsupdate -- note that since you are using update-policy local, you will use the '-l' option instead of '-k' so that it uses the local TSIG session key.  

http://www.bind9.net/manual/bind/9.3.1/Bv9ARM.ch04.html#dynamic_update
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
D_wathiAuthor Commented:
Sir, did revert the serial key in the dyanamic zones and restarted bind , now the entries of the dynamic forward zones are getting addedo but problem with the reverse dynamic zones, for your reference posted below the logs
-------------/var/log/syslog----------------------

Oct  7 11:39:03 lampsrv dhcpd: Added new forward map from shubha.dyn.shriramdb.com to 192.168.1.175
Oct  7 11:39:03 lampsrv named[5129]: client 192.168.1.244#46230: update '1.168.192.in-addr.arpa/IN' denied
Oct  7 11:39:03 lampsrv dhcpd: unable to add reverse map from 175.1.168.192.in-addr.arpa. to shubha.dyn.shriramdb.com: timed out
Oct  7 11:39:03 lampsrv dhcpd: DHCPREQUEST for 192.168.1.175 (192.168.1.244) from 00:0f:ea:96:e0:de (shubha) via eth0
Oct  7 11:39:03 lampsrv dhcpd: DHCPACK on 192.168.1.175 to 00:0f:ea:96:e0:de (shubha) via eth0
Oct  7 11:39:04 lampsrv dhcpd: DHCPDISCOVER from 00:0f:ea:42:b4:80 via eth0
Oct  7 11:39:05 lampsrv dhcpd: DHCPOFFER on 192.168.1.176 to 00:0f:ea:42:b4:80 (rajeshwarist) via eth0
Oct  7 11:39:05 lampsrv named[5129]: client 192.168.1.244#58266: signer "ddns-key" approved
Oct  7 11:39:05 lampsrv named[5129]: client 192.168.1.244#58266: updating zone 'dyn.shriramdb.com/IN': adding an RR at 'rajeshwarist.dyn.shriramdb.com' A
Oct  7 11:39:05 lampsrv named[5129]: client 192.168.1.244#58266: updating zone 'dyn.shriramdb.com/IN': adding an RR at 'rajeshwarist.dyn.shriramdb.com' TXT
Oct  7 11:39:05 lampsrv dhcpd: Added new forward map from rajeshwarist.dyn.shriramdb.com to 192.168.1.176
Oct  7 11:39:05 lampsrv named[5129]: client 192.168.1.244#34787: update '1.168.192.in-addr.arpa/IN' denied
Oct  7 11:39:05 lampsrv dhcpd: unable to add reverse map from 176.1.168.192.in-addr.arpa. to rajeshwarist.dyn.shriramdb.com: timed out
Oct  7 11:39:05 lampsrv dhcpd: DHCPREQUEST for 192.168.1.176 (192.168.1.244) from 00:0f:ea:42:b4:80 (rajeshwarist) via eth0
Oct  7 11:39:05 lampsrv dhcpd: DHCPACK on 192.168.1.176 to 00:0f:ea:42:b4:80 (rajeshwarist) via eth0
Oct  7 11:39:06 lampsrv dhcpd: DHCPDISCOVER from 00:1a:4b:75:69:1c via eth0
Oct  7 11:39:07 lampsrv dhcpd: DHCPOFFER on 192.168.1.177 to 00:1a:4b:75:69:1c (uday) via eth0
Oct  7 11:39:07 lampsrv named[5129]: client 192.168.1.244#56847: signer "ddns-key" approved
Oct  7 11:39:07 lampsrv named[5129]: client 192.168.1.244#56847: updating zone 'dyn.shriramdb.com/IN': adding an RR at 'uday.dyn.shriramdb.com' A
Oct  7 11:39:07 lampsrv named[5129]: client 192.168.1.244#56847: updating zone 'dyn.shriramdb.com/IN': adding an RR at 'uday.dyn.shriramdb.com' TXT
Oct  7 11:39:07 lampsrv dhcpd: Added new forward map from uday.dyn.shriramdb.com to 192.168.1.177
Oct  7 11:39:07 lampsrv named[5129]: client 192.168.1.244#57064: update '1.168.192.in-addr.arpa/IN' denied
Oct  7 11:39:07 lampsrv dhcpd: unable to add reverse map from 177.1.168.192.in-addr.arpa. to uday.dyn.shriramdb.com: timed out
Oct  7 11:39:07 lampsrv dhcpd: DHCPREQUEST for 192.168.1.177 (192.168.1.244) from 00:1a:4b:75:69:1c (uday) via eth0
Oct  7 11:39:07 lampsrv dhcpd: DHCPACK on 192.168.1.177 to 00:1a:4b:75:69:1c (uday) via eth0
Oct  7 11:39:37 lampsrv dhcpd: DHCPDISCOVER from 00:07:95:50:9a:b2 via eth0
Oct  7 11:39:38 lampsrv dhcpd: DHCPOFFER on 192.168.1.162 to 00:07:95:50:9a:b2 (sneha) via eth0
Oct  7 11:39:38 lampsrv named[5129]: client 192.168.1.244#59364: signer "ddns-key" approved
Oct  7 11:39:38 lampsrv named[5129]: client 192.168.1.244#59364: updating zone 'dyn.shriramdb.com/IN': adding an RR at 'sneha.dyn.shriramdb.com' A
Oct  7 11:39:38 lampsrv named[5129]: client 192.168.1.244#59364: updating zone 'dyn.shriramdb.com/IN': adding an RR at 'sneha.dyn.shriramdb.com' TXT
Oct  7 11:39:38 lampsrv dhcpd: Added new forward map from sneha.dyn.shriramdb.com to 192.168.1.162
Oct  7 11:39:38 lampsrv named[5129]: client 192.168.1.244#53825: update '1.168.192.in-addr.arpa/IN' denied
Oct  7 11:39:38 lampsrv dhcpd: unable to add reverse map from 162.1.168.192.in-addr.arpa. to sneha.dyn.shriramdb.com: timed out
Oct  7 11:39:38 lampsrv dhcpd: DHCPREQUEST for 192.168.1.162 (192.168.1.244) from 00:07:95:50:9a:b2 (sneha) via eth0
Oct  7 11:39:38 lampsrv dhcpd: DHCPACK on 192.168.1.162 to 00:07:95:50:9a:b2 (sneha) via eth0
Oct  7 11:40:07 lampsrv named[5129]: client 192.168.1.244#49113: signer "ddns-key" approved
Oct  7 11:40:07 lampsrv named[5129]: client 192.168.1.244#49113: updating zone 'dyn.shriramdb.com/IN': adding an RR at 'SENTHILVEL.dyn.shriramdb.com' A
Oct  7 11:40:07 lampsrv named[5129]: client 192.168.1.244#49113: updating zone 'dyn.shriramdb.com/IN': adding an RR at 'SENTHILVEL.dyn.shriramdb.com' TXT
Oct  7 11:40:07 lampsrv dhcpd: Added new forward map from SENTHILVEL.dyn.shriramdb.com to 192.168.1.212
Oct  7 11:40:07 lampsrv named[5129]: client 192.168.1.244#43740: update '1.168.192.in-addr.arpa/IN' denied
Oct  7 11:40:07 lampsrv dhcpd: unable to add reverse map from 212.1.168.192.in-addr.arpa. to SENTHILVEL.dyn.shriramdb.com: timed out
Oct  7 11:40:07 lampsrv dhcpd: DHCPREQUEST for 192.168.1.212 from 00:19:d1:1e:cb:85 via eth0
Oct  7 11:40:07 lampsrv dhcpd: DHCPACK on 192.168.1.212 to 00:19:d1:1e:cb:85 (SENTHILVEL) via eth0
----------------------
unable to add reverse map please help to resolve this. Thanks
0
PapertripCommented:
I'm guessing that zone 1.168.192.in-addr.arpa is not dynamic.  You probably still have named.conf setup to update 2.168.192.in-addr.arpa.
0
D_wathiAuthor Commented:
Sir, Thanks for the reply, i some how feel my dynamic zones declaration statments are having some problems , posted below the dynamic zones request you to please check and help to resolve.
/var/cache/bind/dynamic$ pwd
/var/cache/bind/dynamic
indar@lampsrv:/var/cache/bind/dynamic$ dir
db.2.168.192.in-addr.arpa  db.dyn.shriramdb.com  db.dyn.shriramdb.com.jnl  db.dyn.shriramdb.com.jnlorg
indar@lampsrv:/var/cache/bind/dynamic$ cat db.2.168.192.in-addr.arpa
;
; BIND reverse data file for local loopback interface
;
$TTL    604800
@       IN      SOA     lampsrv.shriramdb.com. root.shriramdb.com. (
                             2          ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
        IN      NS      lampsrv.shriramdb.com.
244     IN      PTR     lampsrv.shriramdb.com.
;1.0.0  IN      PTR     localhost.
indar@lampsrv:/var/cache/bind/dynamic$ cat db.dyn.shriramdb.com
$ORIGIN .
$TTL 604800     ; 1 week
dyn.shriramdb.com       IN SOA  lampsrv.shriramdb.com. root.shriramdb.com. (
                                19         ; serial
                                604800     ; refresh (1 week)
                                86400      ; retry (1 day)
                                2419200    ; expire (4 weeks)
                                604800     ; minimum (1 week)
                                )
                        NS      lampsrv.shriramdb.com.
                        A       192.168.1.244
$ORIGIN dyn.shriramdb.com.
$TTL 300        ; 5 minutes
arun                    A       192.168.1.201
                        TXT     "31462addc88fdef088f7fe5d5bc0096b41"
csecy                   A       192.168.1.171
                        TXT     "31d9359adabf36ba1c67491c50f276b81a"
prajwala                A       192.168.1.168
                        TXT     "31db0c11a377a25891c8cd89b52f5fae42"
rajeshwarist            A       192.168.1.176
                        TXT     "3126fc247efa8bd3ea329344fa01d89ea6"
reception               A       192.168.1.153
                        TXT     "312f90d6c85cfcf4cf0ab454fcbbdff62a"
SENTHILVEL              A       192.168.1.212
                        TXT     "319595c99ef27a9fc2a1f77e72b84f02a8"
shubha                  A       192.168.1.175
                        TXT     "317a3ac1aa220147c11351d49d1e6c89f3"
sneha                   A       192.168.1.162
                        TXT     "311ea895a41a596e39517b0f46050f4857"
Suresh                  A       192.168.1.202
                        TXT     "313c2aace78089b2375e5657724fd271ea"
uday                    A       192.168.1.177
                        TXT     "31c8f51c1b00e260953cb08d9b84853955"
indar@lampsrv:/var/cache/bind/dynamic$
0
PapertripCommented:
As I said in my last reply, this problem is probably in your named.conf zone block for 1.168.192.in-addr.arpa and that it is not setup to be dynamic and allow updates from dhcpd.

Also, why are you are looking at 2.168.192.in-addr.arpa -- that is not involved in your dynamic DNS setup.
indar@lampsrv:/var/cache/bind/dynamic$ cat db.2.168.192.in-addr.arpa

Open in new window

0
D_wathiAuthor Commented:
Sir, Iam sorry to bother you, my named.conf.local is posted below:

include "/etc/bind/rndc.key";
//include "/etc/bind/ddns.key";

controls {
        inet 127.0.0.1 port 953
                allow {127.0.0.1; } keys { "rndc-key"; };
};


zone "shriramdb.com" {
        type master;
        file "/var/cache/bind/db.shriramdb.com";
};
zone "1.168.192.in-addr.arpa" {
        type master;
        notify no;
        file "/var/cache/bind/db.1.168.192.in-addr.arpa";
};

//## dynamic zones (updated by DDNS) ##

zone "dyn.shriramdb.com" {
        type master;
file "/var/cache/bind/dynamic/db.dyn.shriramdb.com";
allow-update { key "ddns-key"; };
};

zone "2.168.192.in-addr.arpa" {
        type master;
        notify no;
        file "/var/cache/bind/dynamic/db.2.168.192.in-addr.arpa";
        allow-update { key "ddns-key"; };
};
--------------------------------------------------------------------------------------------------------------
dhcp.conf.local
------------
ddns-update-style interim;
include "/etc/bind/ddns.key";
#include "/etc/bind/rndc.key";

zone dyn.shriramdb.com. {
primary 192.168.1.244;
key "ddns-key";
}

zone 2.168.192.in-addr.arpa. {
primary 192.168.1.244;
key "ddns-key";
}

# option definitions common to all supported networks...
option domain-name "dyn.shriramdb.com";
option domain-name-servers 192.168.1.244;
option routers 192.168.1.244;
option broadcast-address 192.168.1.255;
option ntp-servers 192.168.1.244;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.0  192.168.1.245;
}
------------------------------------------------------
sir please suggest me where i am going wrong and what be done to resolve this. Thanks
                                                                         
0
PapertripCommented:
I've already told you what the problem and solution was twice.  I'm trying to not get frustrated, because I know you are smarter than this -- you must be feeling overwhelmed -- don't, this is simple stuff you are probably just over-complicating it in your head.

You changed the subnet range in dhcpd.conf to 192.168.1.x.  You did not update your named.conf to reflect that change.  Look at your zone blocks in named.conf.

zone "1.168.192.in-addr.arpa" {
        type master;
        notify no;
        file "/var/cache/bind/db.1.168.192.in-addr.arpa";
};
zone "2.168.192.in-addr.arpa" {
        type master;
        notify no;
        file "/var/cache/bind/dynamic/db.2.168.192.in-addr.arpa";
        allow-update { key "ddns-key"; };
};

Open in new window

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.0  192.168.1.245;
}

Open in new window

0
D_wathiAuthor Commented:
Sir, I am extremely sorry. will completely go through the config and update you.
0
D_wathiAuthor Commented:
great support.
0
PapertripCommented:
Happy to help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.