On 5/3/2017 7:19 AM, Dave Jones wrote:
Thought: Open up transfer from 69.171.29.37 and I'll test if I can
pull the zone.
Is there anything you can see wrong with that record? It's looking
like dealing with TCP v UDP and EDNS. DJB can be very pedantic about
RFCs and I'm worried we are going to have a compatibility issue. The
good news is that I think this is the SAME issue we were seeing
before the crash so it's likely not going to be PowerDNS (hopefully).
69.171.29.37 has been allowed to do zone transfers for your testing.
This should not be a PowerDNS issue since the sonic.net DNS servers
are working fine.
OK, I pulled the zone. Can you test ns2.pccc.com and tell me if it
looks good to you?
If so, I can ask Brian to pull from my server as a test but I think the
use of DJBDNS is just likely bringing some pedantic RFC hell to light
that I'm not interested in trying to fix ;-)
What was his IP for xfer, again?
If we need to find a replacement DNS server, I should be able to get
permission to use my ns2.ena.com from my day job. It will support
NOTIFY for instant updates and not have this problem. It's currently
slaving for about 200 zones to various flavors of DNS masters plus
it's a master for about 2,000 zones.
That sounds awesome. We can add ns2.pccc.com to diversify more. Let me
know when you have approval.
--
Kevin A. McGrail
Asst. Treasurer, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
