8 Feb
2016
8 Feb
'16
4:26 a.m.
Hello,
Why not to convert the DNS to LDAP database with few more attribute like
owner, last date of activity ,state ( active/suspend) and more as you need.
there are script that convert LDAP attribute to DNS file and only record
that have active state will reflect in the dns.
other script will check one a month\year if the address is in use, if not
he will set date in the lastactive record and after 6 month will set it to
in suspend.
on the next dns update the reccord will be delete from the dns but still be
in the portal, after few month if the owner will not claim it the address
will set free.
also it's will give the option to import to the LDAP all record that are in
the DNS with a suspend state and when someone will claim they will
automatically sync to the DNS.
Just an idea.
Regards,
Tal, 4z7tal
On Mon, Feb 8, 2016 at 11:12 AM, Rob Janssen <pe1chl(a)amsat.org> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Why does an hostname of an isolated system need
to be resolved in a world
wide DNS?
It has no connection to the internet via the gw or to the tunnelling
system,
so that DNS resolution will allways lead to an unreachable host.
Because there really is no relation between IP allocation and routing.
For example, back in the days when we ran a lowspeed IP packet network
here and in surrounding
countries (1987-2003 or thereabouts), it was strictly forbidden in the
regulations to have
a connection between a radio station and a public communication line.
We had thousands of stations active but none reachable from internet.
hostfiles were used instead of DNS, but the information in the hostsfiles
was always
replicated to the public DNS, to indicate what addresses are allocated to
whom.
Also, it would have been possible (had the software on the typical station
supported it) to
download a zonefile and use it offline.
Now that we have linking over- and to internet, we are in fact still doing
that.
Our gateway downloads the zonefile from hamradio.ucsd.edu daily, and
loads it in a local DNS
server on 44-net, only reachable from the radio side.
So even when we lose our internet connection, we can still resolve .
ampr.org addresses as
they were valid just before the breakdown.
I don't think that "reachable from the internet" or "reachable from
net-44
systems that tunnel
over internet" should be a criterion for being in the .ampr.org DNS.
(this does not even consider that there may be firewalls that make it
impossible to detect for
outsiders that a system is connected, while the system itself can
perfectly make outgoing connections)
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net