[44net] Re: RIP broadcasts

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(a)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(a)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(a)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