discuss AT lists.opennicproject.org
Subject: Discuss mailing list
List archive
- From: Peter Green <peter AT greenpete.co.uk>
- To: <discuss AT lists.opennicproject.org>
- Subject: Re: [opennic-discuss] Share your killer T2 config
- Date: Fri, 29 Jun 2012 17:18:26 +0100
- Mail-reply-to: <peter AT greenpete.co.uk>
So, if I understand you correctly, a T! op needs to configure any of their
T.L.D.s to expire (T.T.L.) in much shorter time, maybe 24hours, is there a
recommended time?
Peter
On 29.06.2012 15:30, Jeff Taylor wrote:
Actually it was the other way around... The original OZ zone had a very
large serial (probably based on epoch seconds), and it was changed to
using the YYYMMDDxx format, which gave the zone a *smaller* serial.
When something like this happens, dns services do not automatically grab
the new zone file. They only get the updates when the serial has been
incremented. In cases like this, you have to wait for the zone to expire
before the dns server forces the download of the new zone file. The
expire time on the oz zone is two weeks, so we would have seen failures
during that entire period. Fortunately the server operators who slave
that zone were able to manually reset the file within a couple days and
get everyone back in sync again.
On 06/28/2012 01:21 PM, Alex Hanselka wrote:
The way a zone operates is that with every edit, the serial number in
the SOA record gets incremented by one. Usually they are in the form of
something like YYYYMMDDXX where XX is the edit for that day. The slave
servers, in this case the other T1s and sometimes T2s will only update
if the serial number has incremented since the one they have. In this
case, the serial for OZ got incremented to a huge amount so the other
server never would have updated again causing some failures. Also, some
of the T1s had not even updated their config to resolve the OZ zone
which also caused intermittent failures depending on the T1 my server
queried.
On Jun 28, 2012, at 2:19 PM, Peter Green wrote:
Wow, fast reply! :-)
What do you mean when you say "serial issues"?
The reason I am interested is I am building a testing a T1.
Peter
On 28.06.2012 20:16, Alex Hanselka wrote:
Due to some T1 and serial issues, the OZ zone was not resolving
sometimes. This made me fail the test which made my "pass rate" onForgive
the
as been already been covered, but what were thes with .oz that dropped your up
On 28.06.2012 20:11, Alex Hanselka wrote:lockquote>
---
Alex Hanselka
alex AT opennicproject.org [1]
Links:
------
[1] mailto:alex AT opennicproject.org
- [opennic-discuss] Share your killer T2 config, Psilo, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Alex Hanselka, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Peter Green, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Alex Hanselka, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Peter Green, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Alex Hanselka, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Peter Green, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Jeff Taylor, 06/29/2012
- Re: [opennic-discuss] Share your killer T2 config, Peter Green, 06/29/2012
- Re: [opennic-discuss] Share your killer T2 config, Jeff Taylor, 06/29/2012
- Re: [opennic-discuss] Share your killer T2 config, Alex Hanselka, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Peter Green, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Alex Hanselka, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Peter Green, 06/28/2012
- Re: [opennic-discuss] Share your killer T2 config, Alex Hanselka, 06/28/2012
Archive powered by MHonArc 2.6.19.