On 5/2/2017 9:08 PM, Dave Jones wrote:
Maybe those were test AXFRs but they seemed to work based the logs.
They were tests.
His server is failing to transfer one of the records and it's the one
that was a problem before too I believe.
OK, dig works, I'm able to get a full response that looks like a full
zone. But I did get one part of that response that looks like it may be
why axfr-get is choking:
P response exceeding the 512 bytes limit, requiring a " "resolver to use
a TCP query or EDNS support at both ends, and " "no broken or
misconfigured firewall inbetween\; p="
"MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2eISVGRr1njbT7LVYOp6"
"LxNGlry1t65IVpFfvgIdGeF3hW3f3CXHsmVWGtb3nLFpelsTeXIVwHUE81xAHN6V"
"eMiCoRcQffES5Z5/k68N+UxsLuLq3uiZNXcKLew6SDB06oRSvBbvskjNes1z4Tpg"
"QnUFWCzb5STMUZxG65a4Mkk7mX9X3sRrvm97EZ8U/LeLOz4IUmv7HbHph5CSyuf4"
"fQrUN0GFr2HydC4/DbPqWdCmx4bq+7slE609dUL19ZMv9LYI7E6cpVeX7RmciRTn"
"H7jOVQ6RvIav2REzY5KksgL7eAeV/QYLqSAaFZqYKJjYiZj+6p47ef5u+Cd8GrCj"
"WQIDAQAB"
Here's the docs for axfr-get:
https://cr.yp.to/djbdns/axfr-get.html
--
Kevin A. McGrail
Asst. Treasurer, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
