[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 ]
João Damas
joao at bondis.org
Thu Dec 2 15:20:54 CET 2010
On 2 Dec 2010, at 15:10, Wilfried Woeber, UniVie/ACOnet wrote: > Hi Tore, > > yes, manufacturing a DNS name for my/our probe/s was one of the first > actions during installation :-) > > 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. > > What would be your suggested mechanism to keep this in synch with the > DNS zone data? dynamic updates, I guess. If the probe can't handle that in its firmware then the receiving side, at the NCC, could update a local zone (what Tore was suggesting). This is a request for a service like what dyndns and others do, which has support in quite a few DSL routers these days, but without having to subscribe to these services. > >> 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, > > Cheers, > Wilfried >
- 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 ]