On 05/05/2017 07:38 AM, Dave Jones wrote:
On 05/04/2017 11:20 PM, Kevin A. McGrail wrote:
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?
Looks good:
root@sa-vm1:/tmp# dns_compare -z spamassassin.org -f sa.org -s ns2.pccc.com
.......................................................................................................done
Results:
Matches: 103
Mis-matches: 0
Are you ready to me to add ns2.pccc.com as an NS record on the hidden
master? If so, I vote for ns2.pccc.com should replace ns.hyperreal.org.
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 ;-)
I don't think we should spend more time on this trying to get DJBDNS
slaving up properly. We need good slaving that supports NOTIFYs for
instant updates that we can see happening in our logs. The sonic.net
servers seem to have about a 5 to 10 minute lag even with the NOTIFY
working but this is acceptable.
What was his IP for xfer, again?
209.237.226.92 is his server, he was doing manual testing from .90.
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.
I shouldn't have any problem getting approval later today. ENA is a
small company and the CTO likes me. :) We have a few committers on the
ASF Cloudstack project, two of which are my manager and his manager that
report to the CTO. I think they will approve.
Kevin,
Everyone has approved of our ns2.ena.com helping with the DNS hosting of
spamassassin.org except the CTO. He is out of the office this week and
not able to be reached. His direct report has said OK but would like to
run this past the CTO before giving an official OK. We expect this will
be approved by the CTO but it could take a couple of weeks.
If you want to go ahead with the DNS change request to remove
ns.hyperreal.org and add ns2.pccc.com at the registrar, this will get
the DNS hosting healthy as we get closer to being ready to update DNS
records frequently. We don't need ns.hyperreal.org giving out stale
records.
Dave
