This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] IPv4/DNS entry not updated
- Previous message (by thread): [atlas] IPv4/DNS entry not updated
- Next message (by thread): [atlas] single measurement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Tue Dec 4 09:55:38 CET 2012
Hello, A code change deployed yesterday in the infrastructure prevents the probes from reconnecting to the network. It only affects probes that have disconnected since yesterday afternoon (about 15% of all probes). We've identified the root cause for this and will deploy a fix shortly. In the meantime your probe keeps on measuring, it just cannot report the results. Regards, Robert Kisteleki On 2012.12.04. 9:09, Daniel Gomez wrote: > > Good Morning everyone, > > After a DSL restart from my ISP at 2:00, atlas.ripe.net > <http://atlas.ripe.net> has not updated the IPv4 and with it the DNS. The > proble is online but it is listed as down. > > "dig A p4065.probes.atlas.ripe.net <http://p4065.probes.atlas.ripe.net>" is > showing my IP from yesterday. > > There is any way to push an "update", in order for the probe to register the > right IP ? > > Greetings, > > Daniel Gomez
- Previous message (by thread): [atlas] IPv4/DNS entry not updated
- Next message (by thread): [atlas] single measurement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]