problem updating slave zones

Lucien GENTIS lucien.gentis at lorraine.iufm.fr
Mon Feb 12 14:42:48 UTC 2007


Mark Andrews a écrit :
>> Sounds like you are looking for functionality provided by NOTIFY:
>>
>> notify yes;
>>     
>
> 	Which is the default.
>  
>   
>> You can add this globally in the options{} section of named.conf or turn
>> it on for selected zones by adding to the zone config. Both servers need
>> this in their config. 
>>
>> You will need to restart named on each, but from that point on, you
>> should be able to change the zone on the master and rndc reload <zone>
>> and have the slave pull the new info.
>>     
>
> 	The usual problems are:
> 	1. failure to update the serial number.
> 	2. Notify messages being sourced from the wrong address.
> 	   The address the message is sent from needs to match the
> 	   address in the masters clause.  See notify-source and
> 	   allow-notify.
> 	3. A NAT box not reflecting internal traffic.
> 	   See also-notify.
> 	4. NS to address conversion is failing.  Check that the
> 	   master can resolve the addresses of the nameservers.
> 	5. The wrong nameserver is listed in the SOA record.
> 	   Named does not send NOTIFY messages to the nameserver
> 	   listed in the SOA record.
>  
>   
>> On Mon, 2007-02-05 at 09:38, Lucien GENTIS wrote:
>>     
>>> Hi to all,
>>>
>>> I wanted to update my old DNS servers running Bind 9.2.1 under Redhat 8
>>> and for that, I installed Bind 9.2.4 under Debian Sarge Stable
>>>
>>> So Master zones are still under Bind 9.2.2 - Redhat 8
>>>
>>> When I started my new server, zone files were correctly transfered from 
>>> the Master;
>>> but yet, when I update Master zones, slave zones are not updated, even 
>>> if I restart Bind on the slave server.
>>>
>>> There are only 2 manners updating slave zones:
>>> --- deleting zone files on the slave server and restart the slave server
>>> --- launching command "rndc reload zone"
>>>
>>> How could I configure Bind for slave Zones being automatically updated ?
>>>
>>> Thanks
>>>
>>> Lucien
>>>       
>> #############################################################################
>> ########
>>
>> This email has been scanned by MailMarshal, an email content filter. 
>>
>> #############################################################################
>> ########
>>
>>
>>     
Hi to all and thanks for yours answers

Effectively, "Notify yes;" is the default, and adding it didn't solve 
the problem.

In fact, I had to add 2 things:
--- a "NS record" for my new name server in the master zone file
--- an option "allow-notify" on the slave, but with IP address of the 
gateway of the DMZ
       where the master is, instead of its real IP address

Yet, every time I modify the master zone file and restart the master 
server, it notify the slave
and the new zone file is transfered.

So, I can say this problem is solved.

But I have a last problem: here are the results of a "nslookup" command:

FIRST QUERY:
*************************************
 > www.google.fr
Serveur :  [10.50.200.21]                    
Address:  10.50.200.21

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Le délai de la requête sur [10.50.200.21] est dépassé
**************************************

SECOND QUERY:
**************************************
 > www.google.fr
Serveur :  [10.50.200.21]
Address:  10.50.200.21

Réponse ne faisant pas autorité :
Nom :    www.l.google.com
Addresses:  209.85.135.99, 209.85.135.103, 209.85.135.104, 209.85.135.147
Aliases:  www.google.fr, www.google.com
**************************************

So, every time I query www.google.fr (or another name not known by my 
name server), I get a timeout;
if I repeat the query immediately, I get the correct response.
If I configure a workstation, with this name server for DNS, and try to 
browse, for example with Firefox,
browsing is slower because it take 2 to 4 second for each web site to 
resolve its name.

Could this have to do with forwarding ?

I have this in my named.conf:

// prime the server with knowledge of the root servers
zone "." {
    type hint;
    file "/etc/bind/db.root";
};

and db.root contains all root servers

Thanks for help

Lucien

-- 
Lucien GENTIS
IUFM de Lorraine
Centre de Ressources Informatiques
5, Rue Paul Richard
C.O. 3 - MAXEVILLE
54528 LAXOU-CEDEX

Tél. 03 83 17 68 41
Email : lucien.gentis at lorraine.iufm.fr



More information about the bind-users mailing list