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/[email protected]/
[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 ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Thu Dec 2 21:30:41 CET 2010
João Damas wrote: > Antony, > the "good" is for the users. It would provide them with a stable name > to address the variable external IP they get from the ISP, enabling access > to home machines from the outside using the name, independently of what > IP the DSL modem/cable modem happens to have at any given time Actually, I can see the beauty of name-to-dynamic-IP-tracking, but I doubt that it is a reasonable investment to teach the small things to do dynamic DNS *centrally*. To be able to get a grip on that one, I think we'd need to better understand when and how the probe detects an change of address? My feeling is that tracking of IP to name mapping is a local issue. Wilfried > Joao > > On 2 Dec 2010, at 17:27, Antony Antony wrote: > > >>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 >>> >>> >> > >
- 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 ]