Charles, Ludovic,
please read the reply again.

The issue is that the allocation 44.18.0.0/16 managed by Geoff can not be added to the portal because they are older than the portal and thus are invisible to you.
That does not mean that the allocation is nonexistent, nor that the DNS entries are not used and should be deleted.

Marius, YO2LOJ

On 21/12/2022 06:57, Charles Hargrove via 44net wrote:

You could submit delete entries to the Gateways robot to clean up the DNS.

On 12/20/2022 11:10 PM, Geoff Joy via 44net wrote:

Charles,
I am coordinating the 44.18.0.0/16 area.
There are no assignments evident in that area because they pre-date the AMPR portal and the database. There is no way to insert them into the database in the present implementation. It takes another complete cycle of request and reassignment to make that happen.


Regards,
Geoff Joy -ke6qh-

On Dec 20, 2022, at 19:48, Charles Hargrove via 44net <44net@mailman.ampr.org> wrote:

To the AMPRnet database chief admins, is there a way to clean out the
DNS database of entries if the allocation no longer exists?

There is no allocation for 44.18.48.0/24 yet there are DNS records.
I am sure there are many others if the database is scrubbed.

44.18.48.0    needles.ampr.org needles
44.18.48.1    ke6bbs.ampr.org ke6bbs
44.18.48.64    kd6hpk.ampr.org kd6hpk
44.18.48.65 budge.kd6hpk.ampr.org budge.kd6hpk
44.18.48.66 xerox.kd6hpk.ampr.org xerox.kd6hpk
44.18.48.67 ralph.kd6hpk.ampr.org ralph.kd6hpk
44.18.48.68 jean.kd6hpk.ampr.org jean.kd6hpk
44.18.48.69 ibmxt.kd6hpk.ampr.org ibmxt.kd6hpk
44.18.48.70    pc6.kd6hpk.ampr.org pc6.kd6hpk
44.18.48.71    pc7.kd6hpk.ampr.org pc7.kd6hpk
44.18.48.72    pc8.kd6hpk.ampr.org pc8.kd6hpk
44.18.48.73    k6krz.ampr.org k6krz
44.18.48.80    n6nxz.ampr.org n6nxz
44.18.48.82    ke6amt.ampr.org ke6amt
44.18.48.84    n6vbm.ampr.org n6vbm
44.18.48.255 bc.needles.ampr.org bc.needles

-- 
73 de N2NOV
n2nov@n2nov.ampr.org
n2nov@n2nov.#rich.ny.usa.noam