GoDaddy does not give the zone to Russia?

Question

Domain Name System

Hello.
Today, people have "fallen off" domains registered in GoDaddy. A small study showed that the GoDaddy name servers do not send information to Russia, they do not even ping, everything works great from Germany.
At least the server data is not accessible from Russia:

ns05.domaincontrol.com
ns06.domaincontrol.com
ns43.domaincontrol.com
ns44.domaincontrol.com

they do not respond and do not give information about the zone.
Can anyone else confirm issues accessing domains hosted by GoDaddy?
UPD
The following nameservers are not pinged

ns01.domaincontrol.com
...
ns58.domaincontrol.com

And the name server data is pinged

ns61.domaincontrol.com
...
ns82.domaincontrol.com

and most likely give the zone to Russia
For example 0-buy.com :

dig NS 0-buy.com @ns62.domaincontrol.com

; <<>> DiG 9.7.0-P1 <<>> NS 0-buy.com @ns62.domaincontrol.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2816
;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;0-buy.com.                     IN      NS

;; ANSWER SECTION:
0-buy.com.              3600    IN      NS      ns56.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns55.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns46.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns45.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns38.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns37.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns62.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns61.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns22.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns21.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns10.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns09.domaincontrol.com.
0-buy.com.              3600    IN      NS      ns58.domaincontrol.com.

;; Query time: 247 msec
;; SERVER: 208.109.255.32#53(208.109.255.32)
;; WHEN: Thu Apr 16 19:29:36 2015
;; MSG SIZE  rcvd: 288

and correspondingly:

dig NS 0-buy.com @ns09.domaincontrol.com

; <<>> DiG 9.7.0-P1 <<>> NS 0-buy.com @ns09.domaincontrol.com
;; global options: +cmd
;; connection timed out; no servers could be reached

Answer 1

are not visible. see Crimea with Russia beguiled). do you know how many of us? us army! =)

Answer 2

I confirm.
Had to migrate to cloudflare.com

Answer 3

I confirm the issue. Domain wofh.ru.
MNS01.DOMAINCONTROL.COM
MNS02.DOMAINCONTROL.COM

Answer 4

Likewise, the domain is dead. What is more "interesting" is that mail does not go on his behalf - mail.ru says "DNS problem" and does not accept letters for recipients @mail.ru
Or maybe it's not GoDaddy, maybe it's our RKN that entered something "wrong" in the registry ?

Answer 5

All sites (3 pieces), whose domains are located on GoDaddy - stopped opening from Russia.

Answer 6

Trace to DNS:

> tracert ns44.domaincontrol.com

Трассировка маршрута к ns44.domaincontrol.com [208.109.255.22]
с максимальным числом прыжков 30:

  1     1 ms     1 ms     1 ms  SERVER [192.168.0.100] 
  2     2 ms     1 ms     1 ms  XX.XX.XX.XX 
  3    30 ms    12 ms    12 ms  129-dlp.megaline.ru [85.91.100.129] 
  4     6 ms     5 ms     7 ms  v552-xe100-atlant-msk.m9.naukanet.ru [77.94.167.57] 
  5    49 ms    48 ms    48 ms  77.94.160.54 
  6    61 ms    60 ms    61 ms  ibrsa0203-01.edg.mgmt.ams1.gdg [80.81.193.165] 
  7     *        *        *     Превышен интервал ожидания для запроса.
  8     *        *        *     Превышен интервал ожидания для запроса.
  9     *        *        *     Превышен интервал ожидания для запроса.
 10     *        *        *     Превышен интервал ожидания для запроса.
 11     *        *        *     Превышен интервал ожидания для запроса.

So packages seem to be leaving Russia.
New trace:

> tracert ns44.domaincontrol.com

Трассировка маршрута к ns44.domaincontrol.com [208.109.255.22]
с максимальным числом прыжков 30:

  1     1 ms     1 ms     1 ms  SERVER [192.168.0.100] 
  2     1 ms     1 ms     1 ms  XX.XX.XX.XX 
  3    21 ms    29 ms    13 ms  129-dlp.megaline.ru [85.91.100.129] 
  4     4 ms     7 ms     4 ms  v552-xe100-atlant-msk.m9.naukanet.ru [77.94.167.57] 
  5    49 ms    48 ms    49 ms  77.94.160.54 
  6    61 ms    60 ms    60 ms  ibrsa0203-01.edg.mgmt.ams1.gdg [80.81.193.165] 
  7     *        *        *     Превышен интервал ожидания для запроса.
  8    72 ms    62 ms    61 ms  ip-188-121-33-106.ip.secureserver.net [188.121.33.106] 
  9    61 ms    61 ms    61 ms  ip-188-121-33-105.ip.secureserver.net [188.121.33.105] 
 10    62 ms    62 ms    61 ms  ip-188-121-33-114.ip.secureserver.net [188.121.33.114] 
 11    64 ms    64 ms    64 ms  ns44.domaincontrol.com [208.109.255.22] 

Трассировка завершена.

Some sort of routing problem halfway through I guess.