master and slave on the same server - problem

[Rajesh Bandar]

Kevin, thanks again for your reply. I have modified the
transfer-source and notify-source to master server IP address. It is
working fine now. Thanks a lor for your help.
I have another question? Is it possible to have 2 different rndc.conf
files for each named server. Since I am running master and slave on
the same server with 2 different IP addresses, how can I use rndc
reload to restart the named.

Thanks for your help once again.

Raj.

key "rndc-key" {

algorithm hmac-md5;

secret "hfSrOaQxuvUGTEMGOcdxFg==";

};

controls {

inet 127.0.0.1 port 953

allow { 127.0.0.1; } keys { "rndc-key"; };

};

acl "slaves" {

134.251.131.50;

127.0.0.1;

localhost;

};

options {

directory "/var/named"; // Working directory

listen-on {134.251.131.56; };

allow-transfer { "slaves"; };

transfer-source 134.251.131.56;

notify-source 134.251.131.56;

allow-query { any; }; // This is the default

recursion yes; // Do not provide recursive service

notify yes;

pid-file "/var/run/named.pid";

statistics-file "/var/run/named.stats";

dump-file "/var/run/named.db";

# hide the version number

version "[secured]";

};

# The root nameservers

zone "." {

type hint;

file "named.root";

};

zone "localhost" {

type master;

file "/var/named/zone/localhost.hosts";

};

zone "127.0.0.in-addr.arpa" {

type master;

file "/var/named/zone/0.0.127.rev";

};

zone "au.ap.domain.com" {

type master;

file "/var/named/zone/au.ap.domain.com.hosts";

allow-transfer { "slaves"; };

};

zone "131.251.134.in-addr.arpa" {

type master;

file "/var/named/zone/134.251.131.rev";

allow-transfer { "slaves"; };

};


> I assume you're incrementing the serial # and reloading the zone on the
 master, when you make a change, right (or using Dynamic Update, which
> does these things automatically)?
>
> If so, then I would point out that you have your notify-source set to
> the listen address of the slave instead of the master. By default,
> slaves only respect NOTIFYs that come from the master address. So the
> slave is probably ignoring the NOTIFYs and it could take up to 3 hours
> (your REFRESH setting) for any changes to propagate "naturally".
>
> Is there any particular reason why you set notify-source to the address
> of the slave instance? As for transfer-source, I don't know why you felt
> the need to set that explicitly (also to the slave instance's address),
> since you don't even slave any zones in that (master) instance...
>
> Note that you can use the -b option on later versions of dig to
> test/troubleshoot ordinary queries and zone transfers between nameserver
> instances on the same box.
>
>
>                                          - Kevin
>
>
>
>