21 Dec
2022
21 Dec
'22
2:52 p.m.
The new portal sounds good. I know any DNS entries in my 44.136/24
allocation are out of date, and carry over from the previous holder of
that allocation. Having control of my DNS would allow me to make
appropriate updates.
On 22/12/22 6:34 am, Chris Smith via 44net wrote:
Hi David,
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
Hey Chris,
It is most certainly the case that there are many entries in DNS that
do not have corresponding entries in the portal. However, the whole
point of the portal was to have a way to manage the assignments. One
of Brian Kantor’s main problems was not knowing when someone no longer
required an assignment - if they lose interest, they tend not to
bother letting anyone know and if the worst happens and they go SK
then they clearly can’t let us know.
Brian’s decision was to have a cut off date of a year after the portal
came online - if the end user hadn’t got in touch to claim their entry
by then, the entry was considered not required. This 12 month period
has long since expired (by over 8 years!) so if there is anyone that
hasn’t claimed their assignment after over 8 years it is highly
unlikely they will do so now, and if they do then they can always have
it re-assigned.
Incidentally this is the reason behind the portal removing accounts
(and assignments) after 12 months of not seeing the user logging in.
For anyone that is interested - the portal did originally have DNS
management built in (actually it still does, it’s just disabled).
Unfortunately there was no easy way of matching up DNS entries with
accounts on the portal. Brian was still working on the best way to
import and match the data when he left us.
The new portal will have DNS management live from the start (end users
will be able to manage their own entries), building on Brian’s work
we’ve figured out how to match up the majority of the wanted DNS
entries, but when the new portal does eventually go live, there will
be a window of opportunity (probably 12 months) during which folk will
be able to claim their entries, after which they will be disabled
(removed from the zonefile), at that point if anyone complains things
have stopped working their entries can be re-enabled and assigned to
their account. After a further period (probably another 12 months) the
disabled entries will be removed.
We have literally thousands of DNS entries, my best guess is over 60%
of them are redundant, it really does need cleaning up!
So I re-iterate my request to get in touch if anyone knows of any ARDC
address space that is being used that is not registered on the portal.
I am more than happy to work with anyone that needs to import
assignments into the portal without having to go through the formal
request/approve process.
73,
Chris - G1FEF
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org I would urge you to get in touch and work with me
to correct this.
The bottom line is - if it’s not in the portal database, it’s free
for assignment elsewhere.
This is not the case. I also have examples in my 44.4.0.0/16 subnet
of active user allocations that existed before the portal was
created. I have been reaching out to those users who have DNS
entries but don't have portal entries to clarify the situation and
try to get them to request to make a portal request for their
previous allocation. This can be very difficult at time as people
don't have email addresses in qrz.com <http://qrz.com/> or finding an
email address via the Internet.
Putting it another way, I consider an IP/subnet to be either "in use"
or "under review" if there is a DNS entry but nothing in the AMPR
portal.