0

secondary 45.90.30.0 (ipv4/v6) failure

Hi,

Since the 25/10/2024 at 15h45 (from France), the secondary DNS (ipv4/v6) encounter issues.

No issue for the primary DNS (45.90.28.0).

Here is a screenshot and the posted diag :

https://nextdns.io/diag/0b85ddc0-947d-11ef-bf29-3f1960b24e4b

Thanks

2 replies

null
    • Christophe_Yayon
    • 2 wk ago
    • Reported - view

    Here is a ping test that show the issue :

     

    PING 45.90.30.0 (45.90.30.0) 56(84) bytes of data.
    64 bytes from 45.90.30.0: icmp_seq=1 ttl=49 time=18.2 ms
    64 bytes from 45.90.30.0: icmp_seq=2 ttl=49 time=16.7 ms
    64 bytes from 45.90.30.0: icmp_seq=3 ttl=49 time=14.5 ms
    64 bytes from 45.90.30.0: icmp_seq=4 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=5 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=6 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=7 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=8 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=9 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=10 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=11 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=12 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=13 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=14 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=15 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=16 ttl=49 time=13.5 ms
    64 bytes from 45.90.30.0: icmp_seq=17 ttl=49 time=13.5 ms
    64 bytes from 45.90.30.0: icmp_seq=18 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=19 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=20 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=21 ttl=49 time=13.7 ms
    64 bytes from 45.90.30.0: icmp_seq=22 ttl=49 time=13.2 ms
    64 bytes from 45.90.30.0: icmp_seq=23 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=24 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=25 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=26 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=27 ttl=49 time=13.7 ms
    64 bytes from 45.90.30.0: icmp_seq=28 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=29 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=30 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=31 ttl=49 time=13.4 ms
    64 bytes from 45.90.30.0: icmp_seq=32 ttl=49 time=69.4 ms
    64 bytes from 45.90.30.0: icmp_seq=33 ttl=49 time=70.6 ms
    64 bytes from 45.90.30.0: icmp_seq=34 ttl=49 time=12.7 ms
    64 bytes from 45.90.30.0: icmp_seq=35 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=36 ttl=49 time=13.8 ms
    64 bytes from 45.90.30.0: icmp_seq=37 ttl=49 time=13.8 ms
    64 bytes from 45.90.30.0: icmp_seq=38 ttl=49 time=59.5 ms
    64 bytes from 45.90.30.0: icmp_seq=39 ttl=49 time=57.9 ms
    64 bytes from 45.90.30.0: icmp_seq=40 ttl=49 time=56.0 ms
    64 bytes from 45.90.30.0: icmp_seq=41 ttl=49 time=54.9 ms
    64 bytes from 45.90.30.0: icmp_seq=42 ttl=49 time=57.4 ms
    64 bytes from 45.90.30.0: icmp_seq=43 ttl=49 time=51.6 ms
    64 bytes from 45.90.30.0: icmp_seq=44 ttl=49 time=50.3 ms
    64 bytes from 45.90.30.0: icmp_seq=45 ttl=49 time=48.6 ms
    64 bytes from 45.90.30.0: icmp_seq=46 ttl=49 time=58.0 ms
    64 bytes from 45.90.30.0: icmp_seq=47 ttl=49 time=45.7 ms
    64 bytes from 45.90.30.0: icmp_seq=48 ttl=49 time=43.9 ms
    64 bytes from 45.90.30.0: icmp_seq=49 ttl=49 time=42.5 ms
    64 bytes from 45.90.30.0: icmp_seq=50 ttl=49 time=41.7 ms
    64 bytes from 45.90.30.0: icmp_seq=51 ttl=49 time=40.0 ms
    64 bytes from 45.90.30.0: icmp_seq=52 ttl=49 time=38.2 ms
    64 bytes from 45.90.30.0: icmp_seq=53 ttl=49 time=36.7 ms
    64 bytes from 45.90.30.0: icmp_seq=54 ttl=49 time=13.3 ms
    64 bytes from 45.90.30.0: icmp_seq=55 ttl=49 time=33.6 ms
    ^C
    --- 45.90.30.0 ping statistics ---
    55 packets transmitted, 55 received, 0% packet loss, time 54084ms
    rtt min/avg/max/mdev = 12.721/26.317/70.550/18.474 ms
    
    • Christophe_Yayon
    • 2 wk ago
    • Reported - view

    Hi,

     

    Seems to be resolved since this morning at 07h00 (France)

Content aside

  • 2 wk agoLast active
  • 2Replies
  • 32Views
  • 1 Following