Hi Frank,
Dag Maarten,
> stuid question, but isn't 2004010101 (today) > 1076370400 (9 Feb 2004)?
This doesn't apply here. It is perfectly possible to decrease the value
of your serial number without any consequences for the DNS slave/master
zone transfers, if you adhere to the procedures put forward in RFC 1912
(section 3.1). The fact that the newly introduced serial is lower will
thus not have any consequences from this perspective.
Yes, but we all know there are quite some non-compliant dns-servers out
there. Do they want to break the largest zone for a few days for all
non-compliant servers?
Oh, wait, right, they don't care if they break stuff...
Kind Regards,
Frank Louwers
> > stuid question, but isn't 2004010101 (today) > 1076370400 (9 Feb 2004)?
>
> This doesn't apply here. It is perfectly possible to decrease the value
> of your serial number without any consequences for the DNS slave/master
> zone transfers, if you adhere to the procedures put forward in RFC 1912
> (section 3.1). The fact that the newly introduced serial is lower will
> thus not have any consequences from this perspective.
Yes, but we all know there are quite some non-compliant dns-servers out
there. Do they want to break the largest zone for a few days for all
non-compliant servers?
Oh, wait, right, they don't care if they break stuff...
And all this matters because.. ?
The serial number is used by the slaves, everyone else (ISPs) are only
interested in the expiry which is 1 week. Verisign can force all the slaves to
reload the zone and hence eliminate the old format instantly.
Afaik all subdomains of the gtlds have their own SOAs so it wont affect any
of those and if you're running a stealth slave well this is your notification!
Steve
Frank Louwers wrote:
> Hi Frank,
Dag Maarten,
> > stuid question, but isn't 2004010101 (today) > 1076370400 (9 Feb 2004)?
>
> This doesn't apply here. It is perfectly possible to decrease the value
> of your serial number without any consequences for the DNS slave/master
> zone transfers, if you adhere to the procedures put forward in RFC 1912
> (section 3.1). The fact that the newly introduced serial is lower will
> thus not have any consequences from this perspective.
Yes, but we all know there are quite some non-compliant dns-servers out
there. Do they want to break the largest zone for a few days for all
non-compliant servers?
Oh, wait, right, they don't care if they break stuff...
Since I am currently unemployed I guess it is only as they say of
academic interest to me, but I don't see why it doesn't break it, and
for functionally all of time.
If they do this change, theyll break a tremendows number of systems around.
Alexei Roudnev writes on 1/8/2004 2:00 AM:
If they do this change, theyll break a tremendows number of systems around.
Like, for example?
I think, I should agree with Vixie - while all .com and .net servers are
controlled by Verisign, and no other servers xfer this zones,
the only thing which can break is some script which use SOA to determine, if
'com' was changed (which is unlikely case - I can not image any use for such
script).