7 Feb
2016
7 Feb
'16
11:30 a.m.
On 2/7/16 12:18 PM, Brian Kantor wrote:
This brings up the question of who is to be the owner
of a DNS entry.
Should it be the individual or group who asked for it to be added to
the DNS or should it be the coordinator who entered it? The former
would mean that hundreds of people would have to register with the
portal and take ownership of each of their entries. The latter would
mean that it would be up to the coordinators to keep track of who is
still active (or still alive!) and delete entries for people who are
no longer around. Neither is a satisfactory solution.
In my mind the only logical way to do it is to have the person that requests
the DNS entry own it. Yes, they have to have an account and login once a year
or whatever to say "yes I still need this".
It's not a bad solution, and once we have it setup it works well moving
forward. It does mean the incumbent users need to do just a bit of effort to
register, but really we're making this out to be much harder than it is.
Making the coordinator responsible for checking the validity of the data is
not a scalable solution, as this is really easy to automate. I look at the
coordinator as more a local help desk that can fix things when they break and
issue IP allocations. They should not need to devote time to check out what's
still good and not.
IP allocations are rather easy to validate (especially with the amount of
users most regions have!), DNS not so much.
The goal is to have a tidy DNS database, with only
entries that are
valid as is possible. I am open to suggestions.
We need to have a three options, valid data, no data, and maybe it's good.
The coordinator or who ever could then tag an entry as "maybe" and the system
would send out an email to the admin for that item and they would have to
validate it within 60 days or it's scheduled for deletion.
Thoughts?
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net