Bind Domain Expiration Problem

[Mohsin Raza]

One thing I would like to make clear is I'm not authoritative for 
pipelink.com.pk but I've just having problem in resolving this 
particular domain. I've also checked tcp tarffic between both servers 
and its working fine.

Dawn Connelly wrote:

> Make sure that TCP and UDP 53 is open from the Slave server to the 
> master server. Probably what is happening is that traffic is allowed 
> one direction but not the other. There is something about the notify 
> packets that isn't working for you. Typically what happens is that the 
> slave server sends a packet to the master server at the refresh 
> interval asking "Hey, is this serial number still good?" Then the 
> master server replies with either a yes or a no. If the answer is no, 
> a zone transfer takes place. That traffic happens over TCP. I would 
> definitely check the network path first.  A simple test would be 
> "telnet <master_server_IP> 53" from the slave server and try the 
> inverse from the master. If you can't connect both directions, you 
> found your problem.
>
> On 4/17/07, *Mohsin Raza* <mohsin at max.com.pk 
> <mailto:mohsin at max.com.pk>> wrote:
>
>     I'm administering two name servers which are working fine but I'm
>     facing
>     a problem with a domain pipelink.com.pk <http://pipelink.com.pk>,
>     the record expires after about
>     24 hours when I reload rndc and restart the service of bind, the
>     domain
>     starts to resolve again.
>
>     I've searched a lot but I can't figure out what's the problem and
>     how to
>     resolve it. So kindly provide any useful information in this regard, I
>     shall be thankful.
>
>     --
>     Thanks & regards,
>
>     Mohsin Raza
>
>     Maskatiya Communications (pvt) Ltd.
>
>


-- 
Thanks & regards,
 
Mohsin Raza