25 Apr
2024
25 Apr
'24
12:20 a.m.
Hi Lynwood,
Nobody is saying that a recursive nameserver inside the IPIP Tunnel Mesh is a bad idea,
and thank you for providing this service, I am sure some folks will find it useful. As you
rightly point out, it saves DNS queries going out and back in the UCSD gateway server.
What I personally don't get is why you need access to AXFR / zone transfers? It simply
isn’t required, in fact it’s a bad idea if you are relying on these to answer queries as
they could easily be out of synch with the authoritative nameservers. It is also
generating a lot of unnecessary traffic between your server and the authoritative servers,
especially if you’re pulling them on a regular basis - so counter productive to your
original intent ;-)
73,
Chris - G1FEF
—
ARDC Administrator
Web: https://www.ardc.net
On 24 Apr 2024, at 18:06, lleachii(a)aol.com wrote:
Ruben,
You just asked (or suggest) I be the only available recursive nameserver for AMPRNet. You
must have missed I've begun that for 10+ years ago. Yet to the contrary - you seem to
miss the issue of its need and others existence for years?
In cases where one does not add a gateway to use AMPRNet for Internet, how did users
easily configure clients to use DNS for all of the domains/IP available over the AMPRNet
(44.0/9-44.128.0/10 today) network/space/domain?
The DNS servers prevented the disjointed issued that caused failures prior to
dns-mdc's existence - now, you're just asking me to use my internet for those
clients, yet this solution was to prevent usages of AMPRGW for Internet. So be it. The
late B. Kantor, SK and my Late Regional Coordinator Applauded this - my late coordinator
even setup DNS too, understanding the issue.
As of the passing of N1URO, to my knowledge, I provided the first and not only client DNS
server. So yes - I will just do it, but I humbly asked 44.15/16 spare me Internet when
users connect to them - which might me useful in a emergency. They refused and that's
OK.
I appreciate the response from Federick. Normal PTR requests are fine. Thank you for
understanding the issue preventing better usage of the network - on the network.
73,
Lynwood
KB3VWG
On Wednesday, April 24, 2024 at 12:44:40 PM EDT, Ruben ON3RVH via 44net
<44net(a)mailman.ampr.org> wrote:
Lynwood,
A request like normal is just a standard dns request.
If you want to be a open dns server for everyone on the AMPR network just do it. If
someone asks for a ptr which your server does not own or have in it’s cache it’ll just
look it up using the root servers like any normal dns server.
I don’t get why you **need** to have all reverses in your zones. Master or slave.
73,
Ruben - ON3RVH
On 24 Apr 2024, at 18:35, lleachii--- via 44net
<44net(a)mailman.ampr.org> 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,
- Lynwood
KB3VWG
On Wednesday, April 24, 2024 at 12:26:36 PM EDT, Fredric Moses <fred(a)moses.bz>
wrote:
As the admin for W8CMN and 44.15/16 our PTR records are hosted on seven different
authoritative name servers in diverse areas and networks. BGP and IPIP included, if
somebody wants a PTR record make a request like normal, but we will not be allowing
transfers of zone files to any server not under our control. You are welcome to make PTR
queries like anybody else but no special zone transfers will be allowed.
--
Fredric Moses - W8FSM - WRPA678
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
<mailto:44net-leave@mailman.ampr.org>