[44net] Re: DNS AXFR

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 On Wednesday, April 24, 2024 at 12:49:35 PM EDT, Fredric Moses via 44net <44net(a)mailman.ampr.org> wrote: Make the request to the root server like any other resolver does.  We don’t have to allow you anything you are not ARDC nor was anything about allowing XFRS in any of the documents that was signed for when we got our allocation or when we then had to submit for approval of reverse delegation of our allocations.  Some people or groups might not want to give you special treatment is all. Welcome to the network. Nothing is hidden, make a PTR request to your resolver and you will get a response through the proper way things work. --Fredric Moses - W8FSM - WRPA678 On Apr 24, 2024, at 12:34, lleachii(a)aol.com wrote: Frederic, How does someone "make a request like normal" if their client DNS server is set to 44.1.1.44, but your 7 authoritative servers are not (nor ns2.ardc.net, UK, DE etc. - but others)? - What is that "normal request" in your paradigm? - Please explain - maybe I'm missing something? - What if this user doesn't use IPIP for Internet, but needs to accesses hamwan or your subnet? This is why it's better to simply follow RFC - or maybe your network is not being used for AMPRNet according the AUP? What's being hidden? 73, - LynwoodKB3VWG _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org