Our use case does assume “Radio Only” networks and not just BGP.  It’s why we have an IPIP gateway setup at one of our datacenters that handles the IPIP mesh for those AMPR users who are not BGP speaking.  Even though BGP is our primary external connection for other non IPIP networks.   

You seem pretty enraged about this “thing” you are providing and have provided for years now that nobody here on our networks are even using.  We provide our own dns-cache servers for our users to use as how it should be.   Having XFR of our zone file which is over 5MB mind you does not effect in any way your or other users ability on the IPIP mesh to connect to any IP address’s in our 44.15/16 allocation. 

I would also for future note if you are asking an out of the ordinary question of other admins that telling them if they do not do what you ask that they are some how violating ARDC’s terms of service for allocations and are hiding things.  You come hostile like that don’t be surprised when you get told no even if your “project” might do some good. As you have soiled the relationship.

Chris and others have told you it’s not needed and why what you are requesting isn’t a good idea so no need to pile that on.  But if for some reason you can’t reach any 44.15/16 IP via the IPIP mesh please provide traceroutes.

BTW - Please show me on the DNS server where the lack of XFR’s hurt you...

--
Fredric Moses - W8FSM - WRPA678

On Apr 24, 2024, at 13:18, lleachii@aol.com wrote:

Frederic,


Thanks. I assume your use case does not assume some radio only, etc. networks - and other anomalies, and that's OK - as you know how "your" network is connected to the Internet and others.

Since your use case seems to omit the circumstance a user may not have such connection, yet access to 44.60.44.3 assumes connection - as I noted normal PTR records are OK if one happens to make such a lookup.

Again, thank you for your consideration.



- KB3VWG