[atlas]DNS records for the probes' internet address

talking as an individual.

Isn't it the same as probe ID? just another namespace. 
I wonder how forward dns would scale for large sensor networks. 

I have my doubts on usability and  maintaining operational constancy of forward dns records when  probes change ip addresses. For example, German DSL networks might change probe's public IP-address every day. May be as  Jo?o  suggested dyndns could work in theory. Once there are 1000s of probes what good are forward names. Then we will need hierarchies. 
one hierarchuy based on geography, one based network prefixes, asns .. 

Currently these probes just send out measurements and don't respond to anything but ping.  
 
On the other hand if the probes become more static say something like an  
rpsl-reachable-test [1] there is definitely value for forward dns. Then you actually want a name to IP address mapping.

regards,
-antony

[1] http://tools.ietf.org/html/draft-haberman-rpsl-reachable-test-04





On Thu, Dec 02, 2010 at 11:17:13AM +0100, 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.
> 
> 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.
> 
> Best regards,
> -- 
> Tore Anderson
> Redpill Linpro AS - http://www.redpill-linpro.com
> Tel: +47 21 54 41 27
> 
>