Hi guys.. IP Coordinator for Indiana...
Most of the assignments in our 44.48.x.x range are nolonger in operation... I know we were planning something to address this... what was that plan?
73 jerry
Jerry Kutche Electrical Supervisor
Lehigh Cement Company LLC 180 N. Meridian Road Mitchell, IN 47446 Phone: (812) 849-2191 ext. 251 Fax: (812) 849-5007 Cell: (812) 583-0445 jkutche@lehighcement.commailto:jkutche@lehighcement.com www.lehighcement.comfile:///C:\Documents%20and%20Settings\kmundy\Application%20Data\Microsoft\Signatures\www.lehighcement.com This e-mail may contain confidential and/or legally privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
On Fri, Sep 13, 2013 at 05:46:41AM -0500, Kutche, Jerry (Mitchell) USA wrote:
Most of the assignments in our 44.48.x.x range are nolonger in operation... I know we were planning something to address this... what was that plan?
The old DNS database contains some 46,000 entries. Probably fewer than 500 of these are still valid.
The goal is to have every DNS entry belong to someone who is registered with the portal, so that when that person becomes inactive (defined as no longer keeping their portal registration current despite annual reminders), the DNS entry will also become inactive, and after a year or so, be expunged. That way we can reclaim addresses and also prevent the DNS from being full of obsolete data.
What we have to work with is a database that has only the DNS information for the vast majority of its entries. For the past few years, it has also been recording the timestamp and author of the entry. So the plan in general (details are still to be worked out) is to convert entries which match registered portal users either in the hostname or in the author field. That will have the effect of leaving out most of the obsolete entries but should retain most relevant (active) ones.
Database matching is always a difficult task. This will be a painful process, but as far as I can see, the only alternative is to have everyone re-enter their DNS data from scratch, which would be even more painful and disruptive.
I'm open to suggestions as to better ways to do this. Thoughts? - Brian
Am 13.09.2013 um 13:59 schrieb Brian Kantor Brian@ucsd.edu:
(Please trim inclusions from previous messages) _______________________________________________ On Fri, Sep 13, 2013 at 05:46:41AM -0500, Kutche, Jerry (Mitchell) USA wrote:
Most of the assignments in our 44.48.x.x range are nolonger in operation... I know we were planning something to address this... what was that plan?
The old DNS database contains some 46,000 entries. Probably fewer than 500 of these are still valid.
Our HAMNET range in germany (which is quite new and really up to date) contains more than 3500 entries:
$ grep ^44.224 amprhosts|wc 778 2334 45315 $ grep ^44.225 amprhosts|wc 2868 8605 168263
Many of those are automatically generated by our tool http://hamnetdb.net/
The old packet-radio range in germany nearly has 4900 entries: $ grep ^44.130 amprhosts|wc 4894 14686 192806 Responsible for them are our regional coordinators. I guess, 60% of them are outdated.
We need the bot. We can't live with a web frontend. The only option would be to consequently have country-based subdomains (i.E. de.ampr.org) and either - delegate requests (or have zone transfers to ucsd). But then, it's wise to have a transfer for the reverse-Zones (imho, delegation of PTRs of 44.130/16 and 44.224/15 is not possible). - have small countries being able to be managed in a web frontend (and let generate it their subzonefiles for them)
vy 73, - Thomas dl9sau IP coordination DL
On Fri, Sep 13, 2013 at 02:28:08PM +0200, Thomas Osterried wrote:
We need the bot. We can't live with a web frontend.
Hmm. Well, that will delay the DNS conversion even further. I haven't had time to adapt the old bot to the new database. It's written in 'C'. Any 'C'/mysql wizards interested? - Brian
Brian,
My C is pretty rusty, but if you want to send me the code I will take a look and see if I can understand it.
Thanks. -Neil
On Fri, Sep 13, 2013 at 9:03 AM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Fri, Sep 13, 2013 at 02:28:08PM +0200, Thomas Osterried wrote:
We need the bot. We can't live with a web frontend.
Hmm. Well, that will delay the DNS conversion even further. I haven't had time to adapt the old bot to the new database. It's written in 'C'. Any 'C'/mysql wizards interested? - Brian _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
On Fri, 13 Sep 2013, Brian Kantor wrote:
Hmm. Well, that will delay the DNS conversion even further. I haven't had time to adapt the old bot to the new database. It's written in 'C'. Any 'C'/mysql wizards interested?
What needs to be done?
-
Antonio Querubin -
Brian Kantor -
Kutche, Jerry (Mitchell) USA -
Neil Johnson -
Thomas Osterried