Yahoo Mail servers can't find my domain hostname

[Stephane Bortzmeyer]

On Fri, Sep 07, 2007 at 12:54:41AM +0545,
 Tek Bahadur Limbu <teklimbu at wlink.com.np> wrote 
 a message of 54 lines which said:

> Let's not judge a book by it's cover and assume that everyone is the
> same just because of some stupid actions taken by a few group of
> people.

Point taken. Now, going back to the original subject, the issue with
com.np goes on. As of now, I see:

% check_soa com.np 
ns-np.ripe.net has serial number 2007090601
shikhar.mos.com.np has serial number 2007090702
ns-ext.vix.com has serial number 2007090601
There was no response from ns.ripe.net
np-ns.npix.net.np has serial number 2007090601
yarrina.connect.com.au has serial number 2007090601
sec1.apnic.net has serial number 2007090601
ns-ext.isc.org has serial number 2007090601
np-ns.anycast.pch.net has serial number 2007090401
sec3.apnic.net has serial number 2007090401

np-ns.anycast.pch.net is again late and so is sec3.apnic.net. 

Yesterday, I watched the version change to
2007090601. shikhar.mos.com.np was the first to change (it seems to be
the master) but the others took many hours to join it. 

It seems shikhar.mos.com.np does not send NOTIFY at all (or these
notifies are always filtered out). And the "refresh" time is awfully
large (one full day).

It is also possible that the NOTIFY are received but there are
connectivity issues which prevent the slaves to reach the master.

In anycase, com.np seem to have serious problems. There is no point in
having so many name servers if they cannot connect to the master !