[dns-operations] .MW inconsistent zone updates?

[Gunter Grodotzki]

Hello,

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.            21599    IN    NS    rip.psg.com.

$ dig +nocomments ns cheki.mw @rip.psg.com

; <<>> DiG 9.9.5-9-Debian <<>> +nocomments ns cheki.mw @rip.psg.com
;; global options: +cmd
;cheki.mw.            IN    NS
cheki.mw.        86400    IN    NS ns-1722.awsdns-23.co.uk.
cheki.mw.        86400    IN    NS ns-1022.awsdns-63.net.
cheki.mw.        86400    IN    NS ns-1137.awsdns-14.org.
cheki.mw.        86400    IN    NS    ns-279.awsdns-34.com.
;; Query time: 356 msec
;; SERVER: 147.28.0.39#53(147.28.0.39)
;; WHEN: Thu Jun 25 10:21:58 SAST 2015
;; MSG SIZE  rcvd: 178



Others, like the following, show the correct entry:
mw.            21599    IN    NS    chambo.sdnp.org.mw.
$ dig +nocomments ns cheki.mw @chambo.sdnp.org.mw

; <<>> DiG 9.9.5-9-Debian <<>> +nocomments ns cheki.mw @chambo.sdnp.org.mw
;; global options: +cmd
;cheki.mw.            IN    NS
cheki.mw.        86400    IN    NS athena.ns.cloudflare.com.
cheki.mw.        86400    IN    NS arch.ns.cloudflare.com.
;; Query time: 231 msec
;; SERVER: 196.45.188.5#53(196.45.188.5)
;; WHEN: Thu Jun 25 10:22:29 SAST 2015
;; MSG SIZE  rcvd: 94


Regards,
Gunter Grodotzki