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 ]
David Precious
davidp at preshweb.co.uk
Wed Aug 6 13:51:31 CEST 2014
On Wed, 06 Aug 2014 12:24:45 +0200 Philip Homburg <philip.homburg at ripe.net> wrote: > On 2014/08/06 12:02 , David Precious wrote: > > I've just had my router log new outbound connections then > > power-cycled the probe again. I saw it successfully obtain an IP > > via DHCP (10:13:21), then 31 minutes later, connected to > > oneill.atlas.ripe.net (193.0.19.12) on port 443 (10:44:50) (UK > > times). > > Any chance there might be an issue with the DNS resolver that is used > by the probe? 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?
- 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 ]