Ok, the second line has to be deleted. But still I have some doubts.
digging about bind:
The master DNS for each zone is defined in the 'masters' statement of the zone
clause and allows slaves to refresh their zone record when the 'expiry'
parameter of the SOA Record is reached. If a slave cannot reach the master DNS
when the 'expiry' time has been reached it will stop responding to requests for
the zone. It will NOT use time-expired data.
in my zone file on the slave server I see the expire time is 1800. This means
the slave stop resolving after 30 minutes.
Could be this the problem?
mysipdomain.it IN SOA ns1.mysipdomain.it. root.mysipdomain.it. (
2010042303 ; serial
1800 ; refresh (30 minutes)
1800 ; retry (30 minutes)
1800 ; expire (30 minutes)
1800 ; minimum (30 minutes)
)
Thank you,
Heros
Ing. Heros Deidda
Pre-sales VoIP Engineer
----- Messaggio originale -----
Da: "Dale R Worley (Dale)" <[email protected]>
A: "Heros Deidda" <[email protected]>, [email protected]
Inviato: Martedì, 27 aprile 2010 20:34:23 GMT +01:00
Amsterdam/Berlino/Berna/Roma/Stoccolma/Vienna
Oggetto: RE: [sipx-users] HA DNS server failure on slave when master is down
________________________________________
From: [email protected]
[[email protected]] On Behalf Of Heros Deidda
[[email protected]]
on the slave my /etc/resolv.conf is
search mysipdomain.it
nameserver 127.0.0.1
nameserver 172.16.5.1
________________________________________
You should never need to put a second "nameserver" line in /etc/resolv.conf --
if the caching nameserver on the secondary is not functioning, the secondary
itself is not functioning.
Of course, you need more than one authoritative DNS server for your SIP domain.
Dale
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
