Hi Viktor,

Thank you for the prompt answer.

I will create a ticket.

Regards

Stanish

From: Viktor Naumov [mailto:vnaumov@ripe.net]
Sent: Friday, January 12, 2018 11:28 AM
To: Stanish Stanishev <Stanish.Stanishev@vivacom.bg>; ripe-atlas@ripe.net
Subject: Re: [atlas] #6262 Disconnectted

Hi Stanish,

The "DNS Problem Suspected" tag is set when the Atlas back-end doesn't see SOS messages. Probe/anchor sends SOS messages by means of DNS when it is about to connects to the registration server.

The last SOS message from your anchor was received 2017‑09‑12T09:47:18.115Z while it reconnected 2 times since then. That suggests the diag system that your anchor has some DNS issues.

If you needs further assistance bringing your anchor online I would suggest you to create a ticket.

Best regards
/vty

On 1/12/18 9:23 AM, Stanish Stanishev wrote:

Hello,
Yesterday i got a notification that one of the our Anchors  - #6262 has disconnected from Atlas. According to its Current Status info  - DNS Problem Suspected. I see the anchor is configured to use the following DNS Resolvers  - 8.8.8.8 and 2620:74:1b::1:1.
 
The anchor responds to pings and is reachable from the world. Also the resolvers 8.8.8.8 are 2620:74:1b::1:1 reachable from the anchor's uplink router.
 
So apart from checking the anchor's connectivity and DNS resolvers I don't have much left to do in order to get the anchor connected again.
 
Has anyone faced this situation before ?
 
Thanks
Stanish
 
 
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum