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] Probe 2092 shown as offline for a month
- Previous message (by thread): [atlas] Probe 2092 shown as offline for a month
- Next message (by thread): [atlas] Probe 2092 shown as offline for a month
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Aug 6 14:20:34 CEST 2014
On 2014/08/06 13:51 , David Precious wrote: > The DHCP server gives out the IP of my internal gateway/router (a Linux > box) as the DNS server to use; that's the box all other devices on my > network use, too, so if it had problems I'd certainly have noticed! > > Presumably the probe attemptign to connect that one observed time means > it resolved that hostname, no? I changed something in the probe setting to make it connect even if DNS resolving doesn't work. When that takes effect it will be possible to figure out what is going on exactly. Philip
- Previous message (by thread): [atlas] Probe 2092 shown as offline for a month
- Next message (by thread): [atlas] Probe 2092 shown as offline for a month
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]