Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

rndc reload not reflecting the changes made in zone file.

1,100 views
Skip to first unread message

Gaurav Pruthi

unread,
Nov 1, 2008, 9:32:27 AM11/1/08
to
Hi All,
I have recently upgraded and migrated my DNS server. Version i am using now
is 9.3.5-P2. Problem i am facing is that whenever i make some changes in
zone file (either changing or adding a record), after running rndc reload
domain.com, it is not showing any error but when i run

dig domain.com (running the command of the name server
itself)

it is still showing the old records. There is no issue related to rndc-key
as all the file rndc.conf, rndc.key and named.conf are having the same key.

Permissions of the files are as follows. Named daemon is running as "named"
user.

-rwxrwxr-- 1 root named /usr/local/named/etc/named.conf
-rw-r----- 1 root named /usr/local/named/etc/rndc.conf
-rw-r----- 1 root named /usr/local/named/etc/rndc.key

When i run rndc -V reload domain.com, i gets this message
create memory context
create socket manager
create task manager
create task
create logging context
setting log tag
creating log channel
enabling log channel
create parser
get default key
get config key list
decode base64 secret
reload
post event
using server 127.0.0.1 (127.0.0.1#953)
create socket
connect
create message
render message
schedule recv
send message
parse message
create message
render message
schedule recv
send message
parse message
zone reload queued
[root@server ~]# /usr/local/named/sbin/rndc -V reload domain.com
create memory context
create socket manager
create task manager
create task
create logging context
setting log tag
creating log channel
enabling log channel
create parser
get default key
get config key list
decode base64 secret
reload
post event
using server 127.0.0.1 (127.0.0.1#953)
create socket
connect
create message
render message
schedule recv
send message
parse message
create message
render message
schedule recv
send message
parse message
zone reload up-to-date


The zone gets updated when i restarts the named daemon.

In /var/log/named message appear as:

general: zone domain.com/IN: loaded serial 3000000122


Kindly suggest what could be the issue.

Thanks,
Gaurav Pruthi

Alan Clegg

unread,
Nov 1, 2008, 10:24:30 AM11/1/08
to
Gaurav Pruthi wrote:
> I have recently upgraded and migrated my DNS server. Version i am using now
> is 9.3.5-P2. Problem i am facing is that whenever i make some changes in
> zone file (either changing or adding a record), after running rndc reload
> domain.com, it is not showing any error but when i run
>
> dig domain.com (running the command of the name server
> itself)
>
> it is still showing the old records. There is no issue related to rndc-key
> as all the file rndc.conf, rndc.key and named.conf are having the same key.

What does /etc/resolv.conf on that server contain?

AlanC

Gaurav Pruthi

unread,
Nov 3, 2008, 1:45:38 AM11/3/08
to
It contains the localhost address i.e.
nameserver 127.0.0.1


Gaurav Pruthi

Gaurav Pruthi

unread,
Nov 6, 2008, 8:00:36 AM11/6/08
to
Yes i always increment the serial number before updating zone file. This
problem was not persisting before. This only happened after i upgraded the
bind package.

Gaurav Pruthi

On Thu, Nov 6, 2008 at 6:18 PM, Jack Tavares <j.ta...@f5.com> wrote:

> Did you change the serial number?
> You have to bump the serial number
>
> --
>
> ________________________________________
> From: bind-use...@isc.org [bind-use...@isc.org] On Behalf Of
> Gaurav Pruthi [gkpr...@gmail.com]
> Sent: Saturday, November 01, 2008 3:32 PM
> To: bind-...@isc.org
> Subject: rndc reload not reflecting the changes made in zone file.
>
> Hi All,


> I have recently upgraded and migrated my DNS server. Version i am using now
> is 9.3.5-P2. Problem i am facing is that whenever i make some changes in
> zone file (either changing or adding a record), after running rndc reload
> domain.com, it is not showing any error but when i run
>
> dig domain.com (running the command of the name server
> itself)
>
> it is still showing the old records. There is no issue related to rndc-key
> as all the file rndc.conf, rndc.key and named.conf are having the same key.
>

0 new messages