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]DNS records for the probes' internet address
- Previous message (by thread): [atlas]DNS records for the probes' internet address
- Next message (by thread): [atlas]DNS records for the probes' internet address
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Emile Aben
emile.aben at ripe.net
Thu Dec 2 11:56:21 CET 2010
On 02/12/2010 11:17, Tore Anderson wrote: > Hi list, > > I've got a probe connected to my home broadband connection, which might > change its WAN address whenever my ISP feels like it should. I just > thought it would be a nice feature if the probes had an A record in DNS > that were automatically updated to match the current external address. > Like probe-121.atlas.ripe.net or something. That way I would have a > hostname I would be sure that points to the WAN address of my CPE > whenever I want to log on to my home network from somewhere else. We can see if there is broader interest for this feature and make it an opt-in (checkbox in the GUI). One thing to be careful about here is that having all probes in easy to guess hostnames, will make it easy to DoS part of the infrastructure. Doing it as an opt-in, will make sure that only the people that want/need this feature will enable it, and if that is a sufficiently low fraction of total, it makes it unlikely as a DoS target. > I would think such a feature would be a small incentive for home > broadband users to become probe hosts. > > On an unrelated note, the graphs for the probe in question (#121) > doesn't work, they're all gray, even though the probe is up. As we speak, probes are upgrading to firmware version 3900, which solves this problem (see http://atlas.ripe.net/dynamic/stats/stats.probe_versions.png for overall status). In case people still see this problem by the end of the day with firmware version < 3900 and want to force firmware version 3900 onto their probes: You can force the upgrade by rebooting (unplugging and replugging) your probe. Emile
- Previous message (by thread): [atlas]DNS records for the probes' internet address
- Next message (by thread): [atlas]DNS records for the probes' internet address
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]