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 ]
Tore Anderson
tore.anderson at redpill-linpro.com
Fri Dec 3 09:15:08 CET 2010
Good morning, * Wilfried Woeber, UniVie/ACOnet > 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*. Clearly it would be a waste of the probe's constrained resources to make it do such DNS updates itself. I didn't mean to suggest that the probe should change in any way. The central Atlas system, *already* knows all the necessary information. If you check your probe details on the web page, you will see a field called «Internet Address», which will differ from «Local Address» if the probe is behind the NAT. So my idea was simply to set up a DNS server with a custom zone backend that looked up this information directly from the central database it's stored in. 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 ]