19 Jan
2016
19 Jan
'16
1:14 p.m.
I don't know how practical it would be to to try and monitor the dns
server queries to help id which entries are used vs unused. But it
might be something to consider sooner than later as you'd want to let
this run for quite some time to build some statistics.
Just throwing the idea out there.
As for figuring out what is unused or not, there
isn't any good way of
determining that.
19 Jan
19 Jan
2:09 p.m.
New subject: AMPRNet DNS cleanup
I think people are making this way more complex than necessary:
Two conditions exist:
1 - A DNS entry is essentially dead, nobody will notice if it's deleted.
(probably > 95%)
2 - A DNS entry is in use. If it disappears, the affected party will
notice and it can be corrected.
In general, it's time to flush old entries.
On Tue, Jan 19, 2016 at 10:14 AM, Steve L <kb9mwr(a)gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
I don't know how practical it would be to to try and monitor the dns
server queries to help id which entries are used vs unused. But it
might be something to consider sooner than later as you'd want to let
this run for quite some time to build some statistics.
Just throwing the idea out there.
--
------------------------------
John D. Hays
K7VE
PO Box 1223, Edmonds, WA 98020-1223
<http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
<http://www.facebook.com/john.d.hays>
As for figuring out what is unused or not, there
isn't any good way of
determining that.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
20 Jan
20 Jan
3:42 a.m.
New subject: AMPRNet DNS cleanup
On 19.1.2016. 20:09, K7VE - John wrote:
I think people are making this way more complex than
necessary:
Two conditions exist:
1 - A DNS entry is essentially dead, nobody will notice if it's deleted.
(probably > 95%)
2 - A DNS entry is in use. If it disappears, the affected party will
notice and it can be corrected.
Agree.
In general, it's time to flush old entries.
I do not know how whole process works, but on other service I use
inactive accounts (and thus IP and DNS records) are not deleted, just
disabled.
That leaves time for users, if they actually use them, to notice that
something is wrong, react and reactivate by logging to the service at
least once. In process user may be asked to update contact data.
If account stays disabled for some time, then it is deleted with all
it's records.
Email notifications are fired a month before action is taken. If user's
email is obsolete, he will not get notices but he will later notice that
his account is disabled. If he does not even notice that, then it is
sure sign that account and data are obsolete too.
I guess similar can be applied here. It would take some time to clean
database but at least it would not cause damage for active users.
Pedja
YT9TP
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
19 Jan
19 Jan
2:29 p.m.
New subject: AMPRNet DNS cleanup
On Tue, Jan 19, 2016 at 12:14:02PM -0600, Steve L wrote:
I don't know how practical it would be to to try
and monitor the dns
server queries to help id which entries are used vs unused.
Considering how much spoofed traffic falsely from net-44 there is that
generates lookups anyway, the DNS queries are not a reliable way to
determine what's in use.
- Brian
3038
days inactive
3039
days old
3 comments
4 participants
participants (4)
-
Brian Kantor -
K7VE - John -
Pedja YT9TP -
Steve L