No-Sync-at-Slave

[Mohammed Ejaz]

Thank you so much for your immediate answer, I wanted know how did you check
as 212.93.192.4 configured only on UDP? 

-----Original Message-----
From: Mark Andrews [mailto:marka at isc.org] 
Sent: Thursday, May 8, 2014 10:33 AM
To: Mohammed Ejaz
Cc: bind-users at isc.org
Subject: Re: No-Sync-at-Slave


In message <003c01cf6a8d$3a0a72d0$ae1f5870$@cyberia.net.sa>, "Mohammed Ejaz"
wr
ites:
>  
> 
> I have a primary and secondary name server which host a number of domains.
> Recently, the secondary has started failing to sync one of the 
> domains, and comes up with the following

Assuming the IP addresses is correct something is filtering the TCP
connections.  DNS uses *both* TCP and UDP.  It is a myth that TCP is only
used for zone transfers.  Properly configured nameservers answer on both TCP
and UDP.  212.93.192.4 only answers on UDP.

> May  7 22:51:12 ns2 named[1381]: [ID 873579 daemon.error] transfer of 
> 'domain.com/IN' from 212.93.192.4#53: failed to connect: timed out
> 
> May  7 21:35:06 ns2 named[1381]: [ID 873579 daemon.error] transfer of 
> 'domain.com/IN' from 212.93.192.4#53: failed to connect: timed out
> 
> May  7 21:43:31 ns2 named[1381]: [ID 873579 daemon.error] transfer of 
> 'domain.com/IN' from 212.93.192.4#53: failed to connect: timed out
> 
>  
> 
>  
> 
> Any one's  help would be highly appreciated thanks in advance. 
> 
>  
> 
> Regards
> 
> Ejaz
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org

--