Re: [dns-operations] .MW inconsistent zone updates?

2015-06-28 Thread Randy Bush
the occasional packet can get through rip.psg.com:/root# ping 196.45.188.5 PING 196.45.188.5 (196.45.188.5): 56 data bytes 64 bytes from 196.45.188.5: icmp_seq=2 ttl=44 time=360.147 ms 64 bytes from 196.45.188.5: icmp_seq=55 ttl=44 time=377.265 ms 64 bytes from 196.45.188.5: icmp_seq=78 ttl=43

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Phil Regnauld
Stephane Bortzmeyer (bortzmeyer) writes: It has always been our policy (and, I believe, the one of the majority of DNS operators), that responsability and monitoring belongs to the _master_. If a secondary of .fr lags behind, it is _our_ role and responsability to detect it and to solve it

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Randy Bush
all true. but mw is a tough case, hard circumstances. and a sat link does not help. so frank from tz helps watch and debug. warren also watches, but he is up at layers nine and ten this week. life goes on. randy ___ dns-operations mailing list

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Stephane Bortzmeyer
On Thu, Jun 25, 2015 at 11:12:40AM +0200, Gunter Grodotzki gun...@grodotzki.co.za wrote a message of 78 lines which said: But shouldn't that raise a big red flag - even if it is not your fault? DNS operator hat _on_. At $DAYJOB, we both have secondaries for other domains, and domains for

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Anand Buddhdev
On 25/06/15 10:30, Randy Bush wrote: rip.psg.com:/root# dig +short @196.45.188.5 mw. soa ;; connection timed out; no servers could be reached rip.psg.com:/root# dig +short @41.221.99.135 mw. soa ;; connection timed out; no servers could be reached having fun over there? We also operate

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Gunter Grodotzki
Hi Randy, Thank you for your quick response! So in other words master is blocking you from fetching updates? But shouldn't that raise a big red flag - even if it is not your fault? Currently your slave is the only one not receiving any updates thus poisoning dns-caches with wrong/outdated

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Stephane Bortzmeyer
On Thu, Jun 25, 2015 at 10:23:46AM +0200, Gunter Grodotzki gun...@grodotzki.co.za wrote a message of 47 lines which said: I did a domain update last week on cheki.mw, but it seems like some OPs are either sleeping or their syncing is not really working ;) Inconsistencies are always fun to

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Gunter Grodotzki
Ah ok my mistake, sorry for that! I made the wrong assumption, did not know it was a overall problem with the masters. The Zone-OPS according to iana.org are in cc'ed and should hopefully have enough debug data to see the problem and solve it? Thanks again Randy for your feedback, I'm glad

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Randy Bush
The Zone-OPS according to iana.org are in cc'ed and should hopefully have enough debug data to see the problem and solve it? frank has been working with them for a while and debugging. just did not see the need to start screaming fire in a crowded theater. randy

Re: [dns-operations] .MW inconsistent zone updates?

2015-06-25 Thread Randy Bush
I did a domain update last week on cheki.mw, but it seems like some OPs are either sleeping or their syncing is not really working ;) The following auth-ns is still delivering a old record: mw.21599INNSrip.psg.com. $ dig +nocomments ns cheki.mw @rip.psg.com ;