Chris,
Are you the person I should be contacting to ensure that there is a Atlantic Division/MDC Section DNS for AMPRNet - or should I contact another Ham regarding the infrastructure DNS? I seem to have inquires regarding DNS that are unresolved (see CLI output below), namely:
- Verify ns.ardc.net is configured for new global zones for Reverse DNS after 44/8 was subdivided - Why certain AMPRNet IPs cannot AXFR (per your email - "but you can do zone transfers from ns.ardc.net if you’re source IP is within 44.0.0.0/9 or 44.128.0.0/10")
user@dns-mdc:~$ ls /var/lib/bind/44.rev -l-rw-r--r-- 1 bind bind 3221142 Feb 22 2023 /var/lib/bind/44.rev user@dns-mdc~$ dig -b 44.60.44.3 AXFR ampr.org @44.1.1.44;; Connection to 44.1.1.44#53(44.1.1.44) for ampr.org failed: timed out.
If you are still working on this - I offer my sincere apologies. One issue seems to be over a year old. If you don't understand the ramifications - anyone using my server are receiving 1-year old PTR records.
--- 73,
- LynwoodKB3VWG
On Sunday, April 21, 2024 at 07:38:18 PM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
A.) Please verify your new zones are:
- 0.44.in-addr.arpa - 68.44.in-addr.arpa - 128.44.in-addr.arpa
B.) Testing the command 'dig AXFR ampr.org @44.1.1.44'
- Works from SRC IP 44.60.44.128 - DOES NOT work from SRC IP 44.60.44.3 - hence I still have failing transfers on dns-mdc.ampr.org (dig -b 44.60.44.3 AXFR ampr.org @44.1.1.44)
user@dns-mdc:~$ ls /var/lib/bind/ampr.org.hosts -l -rw-r--r-- 1 bind bind 2580501 Apr 11 09:08 /var/lib/bind/ampr.org.hosts
C.) This was also odd: user@dns-mdc:~$ ping 44.1.1.44 -I 44.60.44.3PING 44.1.1.44 (44.1.1.44) from 44.60.44.3 : 56(84) bytes of data.From 44.1.1.44 icmp_seq=1 Destination Protocol Unreachable64 bytes from 44.1.1.44: icmp_seq=2 ttl=49 time=210 ms64 bytes from 44.1.1.44: icmp_seq=3 ttl=49 time=208 ms D.) I noticed the high ping, is this server at UCSD or elsewhere? E.) I've updated my NTP configuration as well.
--- - Lynwood
On Sunday, April 21, 2024 at 06:47:26 AM EDT, Chris chris@ardc.net wrote:
You should update to use ns.ardc.net as your time source. All functionality on the gateway server is being deprecated except it’s role as the IPIP gateway i.e. encap/de-encap and RIP44d 73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 21 Apr 2024, at 11:21, lleachii--- via 44net 44net@mailman.ampr.org wrote: I also wanted to note that 44.0.0.1 still appears to be a Stratum 2 NTP server as well. If this functionality is planned to switch, I also need to know to change my sanity check peers for 44.60.44.1. --- Lynwood
On Sunday, April 21, 2024 at 06:07:40 AM EDT, lleachii--- via 44net 44net@mailman.ampr.org wrote:
All,
- dns-mdc.ampr.org (44.60.44.3) has been reconfigured for ns.ardc.net (44.1.1.44) - dns-mdc.ampr.org is recursive for source IPs within 44.0.0.0/9 or 44.128.0.0/10 - AXFR for AMPR.ORG works - AXFR 44.in-addr.arpa does NOT work - AXFR for 68.44.in-addr.arpa works - I also have a Stratum 2 NTP server available at 44.60.44.1 (for source IPs within 44.0.0.0/9 or 44.128.0.0/10 or IPIP Tunnel Public IP addresses)
Chris,
- Should I also be adding 128.44.in-addr.arpa? - May I receive all the [verified] parameters on your part?
73,
LynwoodKB3VWG
On Saturday, April 20, 2024 at 04:11:07 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
In case it is of use to anyone you can also get NTP time from ns.ardc.net if you are on any 44Net IP. It is a stratum 2 server. 73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 20 Apr 2024, at 20:47, Charles J. Hargrove n2nov@n2nov.net wrote: Thank you, but it would have been useful to everyone to have this laid out way before the shutdown. I hat playing catch-up at work or in my hobby.
On 4/20/2024 2:40 PM, Chris - G1FEF wrote:
That makes sense, the gateway server at UCSD is no longer running a DNS server. We have four authoritative nameservers now: ns.ardc.net a.gw4.uk ns1.de.ardc.net ns2.us.ardc.net None of these permit recursive lookups, but you can do zone transfers from ns.ardc.net if you’re source IP is within 44.0.0.0/9 or 44.128.0.0/10 We are planning on setting up a recursive nameserver for 44.0.0.0/9 and 44.128.0.0/10 IPs at some point. 73, Chris
On 20 Apr 2024, at 18:11, Charles J. Hargrove n2nov@n2nov.net wrote:
The SMTP process in JNOS was piling up messages with 44.0.0.1 as a DNS server. Having seen that the issue was with 44.0.0.1, I changed to 8.8.8.8 (Google) and things cleared out quickly. My personal JNOS also does public SMTP messaging, so I already had 8.8.8.8 and a few others besides AMPR DNS. The various state HamGates only had AMPR DNS, so they were backing up. I can only go by what I was seeing vs what had been working for two years.
On 4/20/2024 12:59 PM, Chris - G1FEF wrote: The gateway server is still online and working, it’s not been moved, some of it’s functions have been deprecated, but I am able to SSH into it ok, so could you expand a bit on “unresponsive” please? Thanks Chris
On 20 Apr 2024, at 15:21, Charles J. Hargrove n2nov@n2nov.net wrote:
AMPR DNS at 44.0.0.1 has been unresponsive since April 11th. Either something is wrong with it or it has been moved without us being notified.
On 4/19/2024 2:30 PM, Chris wrote:
On 19 Apr 2024, at 18:42, Charles J. Hargrove via 44net 44net@mailman.ampr.org wrote:
Has anyone noticed anything strange with encap routing and DNS entries since 4/10?
Can you be a little more specific Charles? There have been some major changes with encap and DNS in moving to the new portal, so if you are seeing any issues please let me know so they can be investigated/fixed