Re: broken ISP in china

2013-02-19 Thread G.W. Haywood
Hi there, On Mon, 18 Feb 2013, Vernon Schryver wrote: ... Recently I moved this domain(lcrcomputer.net) to a registrar that suports DNSSEC and inserted the DS record for this domain. I checked DNSSEC via http://dnsviz.net and http://dnssec-debugger.verisignlabs.com. Both show DNSSEC is

Re: broken ISP in china

2013-02-19 Thread Dave Warren
On 2/18/2013 23:20, Matus UHLAR - fantomas wrote: On 19.02.13 10:25, Noel Butler wrote: One thing I need to point out, your SOA timings seem extreme... refresh 86400 drop that to 3h retry 3600, drop to 900 I don't see the reason for doing these, unless NOTIFY does not work, but in such

Re: broken ISP in china

2013-02-19 Thread Sten Carlsen
Just be sure that WHEN your master dies, the slaves will stay authoritative for long enough that you can get the master up without working night shift. On 19/02/13 21:17, Dave Warren wrote: On 2/18/2013 23:20, Matus UHLAR - fantomas wrote: On 19.02.13 10:25, Noel Butler wrote: One thing I need

broken ISP in china

2013-02-18 Thread Lyle Giese
I am cross posting this as it might be a dns issue, but it effects email directly. And I am quite aware of the 'Great Chinese Firewall' and realized that may be a large part of the issue. LCR's mail filter and mail servers are all in the lcrcomputer.net domain. Recently I moved this

Re: broken ISP in china

2013-02-18 Thread Chuck Swiger
Hi-- On Feb 18, 2013, at 2:07 PM, Lyle Giese wrote: Recently I moved this domain(lcrcomputer.net) to a registrar that suports DNSSEC and inserted the DS record for this domain. I checked DNSSEC via http://dnsviz.net and http://dnssec-debugger.verisignlabs.com. Both show DNSSEC is

Re: broken ISP in china

2013-02-18 Thread Noel Butler
On Mon, 2013-02-18 at 16:07 -0600, Lyle Giese wrote: Recently I moved this domain(lcrcomputer.net) to a registrar that suports DNSSEC and inserted the DS record for this domain. I checked DNSSEC via http://dnsviz.net and http://dnssec-debugger.verisignlabs.com. Both show DNSSEC is

Re: broken ISP in china

2013-02-18 Thread David Forrest
On Mon, 18 Feb 2013, Lyle Giese wrote: I am cross posting this as it might be a dns issue, but it effects email directly. And I am quite aware of the 'Great Chinese Firewall' and realized that may be a large part of the issue. LCR's mail filter and mail servers are all in the

Re: broken ISP in china

2013-02-18 Thread Tony Finch
Lyle Giese l...@lcrcomputer.net wrote: Recently I moved this domain(lcrcomputer.net) to a registrar that suports DNSSEC and inserted the DS record for this domain. Was it signed before this point? I am wondering if this is a DNS response size problem - was the cause the addition of the DS

Re: [mailop] broken ISP in china

2013-02-18 Thread Lyle Giese
On 02/18/13 19:02, Tony Finch wrote: Lyle Giese l...@lcrcomputer.net wrote: Recently I moved this domain(lcrcomputer.net) to a registrar that suports DNSSEC and inserted the DS record for this domain. Was it signed before this point? I am wondering if this is a DNS response size problem - was

Re: broken ISP in china

2013-02-18 Thread Vernon Schryver
I see no problem with your SPF IP records though so long as you dont try use ns1. Ignoring most of Vernons anti SPF rhetoric, which BTW this list is NOT the place for (go cry a river on mailop list), he is correct that you shouldn't really be using PTR, or A for that mater, just have your

OFF TOPIC Re: broken ISP in china

2013-02-18 Thread Noel Butler
apparently you have no comprehension of OFF TOPIC I stopped reading at about the half dozen words because you once again went off on your OFF TOPIC rants. But each to our own, you hate it, many stand by it, its only fools like you who cant accept that, thats your problem not mine. Given that

Re: broken ISP in china

2013-02-18 Thread Matus UHLAR - fantomas
On 19.02.13 10:25, Noel Butler wrote: One thing I need to point out, your SOA timings seem extreme... refresh 86400 drop that to 3h retry 3600, drop to 900 I don't see the reason for doing these, unless NOTIFY does not work, but in such case it's the NOTIFY that should be fixed... expire