On 5/8/2017 10:32 AM, Dave Jones wrote:
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.
Yes, go ahead and add it as an NS record and add a test record,
increment the serial and test. I've setup 62.210
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 deali
On 5/3/2017 6:18 PM, Dave Jones wrote:
I have setup my ns2.ena.com as a slave to the hidden master for testing.
Slaving is working perfectly. It's not published in the
spamassassin.org NS records yet on the hidden master. If we want to
add it to the DNS hosting, I will work on getting proper
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
On 05/03/2017 06:19 AM, Dave Jones wrote:
On 05/02/2017 09:22 PM, Kevin A. McGrail wrote:
On 5/2/2017 10:04 PM, Kevin A. McGrail wrote:
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.
Thought: Open up transfer
On 05/02/2017 09:22 PM, Kevin A. McGrail wrote:
On 5/2/2017 10:04 PM, Kevin A. McGrail wrote:
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.
Thought: Open up transfer from 69.171.29.37 and I'll test if I can pull
On 5/2/2017 10:04 PM, Kevin A. McGrail wrote:
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.
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 w
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 l
About an hour and a half ago, I see good AXFRs in the logs:
May 02 16:27:31 sa-vm1 pdns_server[14404]: May 02 16:27:31 AXFR of
domain 'spamassassin.org' initiated by 209.237.226.92
May 02 16:27:31 sa-vm1 pdns_server[14404]: May 02 16:27:31 AXFR of
domain 'spamassassin.org' allowed: client IP 20
On 05/02/2017 03:00 PM, Kevin A. McGrail wrote:
On 5/2/2017 3:27 PM, Dave Jones wrote:
I had .92 in the PowerDNS allowed-axfr list so it must be coming from
.90. I have added .90 to the list so please try it again when you get
a chance.
Will do!
P.S. You can easily check the outbound (init
On 5/2/2017 3:27 PM, Dave Jones wrote:
I had .92 in the PowerDNS allowed-axfr list so it must be coming from
.90. I have added .90 to the list so please try it again when you get
a chance.
Will do!
P.S. You can easily check the outbound (initiated traffic) IP with
'curl curlmyip.net'.
I thi
On 05/02/2017 11:27 AM, Kevin A. McGrail wrote:
Dave, thoughts re: Hyperreal below?
Hrm, I seem to be getting a block. My usual tool for this is djbdns, and
I pull down secondaries using tcpclient, as so:
[root@taz4 /etc/tinydns/root/secondaries]# /usr/local/bin/tcpclient
62.210.60.231 53
Dave, thoughts re: Hyperreal below?
Hrm, I seem to be getting a block. My usual tool for this is djbdns, and
I pull down secondaries using tcpclient, as so:
[root@taz4 /etc/tinydns/root/secondaries]# /usr/local/bin/tcpclient
62.210.60.231 53 /usr/local/bin/axfr-get spamassassin.org spamassass
13 matches
Mail list logo
