If this is a FAQ, please accept my apologies and point me to it.
Mike Schrauder
Specialty Blades, Inc.
If your zone serial number is 25,000 and you want to start numbering at
1 again, you can speed through the serial number space in two steps.
First, add the largest increment possible to your serial number (25,000
+ 2,147,483,647 =3D 2,147,508,647). If the number you come up with is
larger than 4,294,967,295 (the largest 32-bit value), you'll have wrap
around to the beginning of the number space by subtracting 4,294,967,296
from it. After changing the serial number, you must wait for all of your
secondaries to pick up a new copy of the zone. Second, change the zone
serial number to its target value (1), which is now larger than the
current serial number (2,147,508,647). After the secondaries pick up a
new copy of the zone, you're done!=20
Mike S
> -----Original Message-----
> From: Mike Schrauder=20
> Sent: Thursday, May 12, 2005 2:54 PM
> To: comp-protoc...@isc.org
> Subject: newb ? serial number out of sync
>=20
> I was playing around after upgrading to bind 9.2.4 from NT=20
> dns. NT had a serial number of 2812345678 (eg) and so the=20
> secondaries=3D20 had that stored. I made it 3005051101 to=20
> shake things loose.
> Now the secondaries have that stored and I would like to fix=20
> it (2005051201) but since the secondaries (which I have no control
> over) will not update to the 'lower' number. Any ideas?
>=20
> If this is a FAQ, please accept my apologies and point me to it.
>=20
>=20
> Mike Schrauder
> Specialty Blades, Inc.
>=20
>=20
>=20
>=20
I think you can update the serial #'s on your master(s) to whatever you=
=
want. Then delete the db files on the slaves and restart the slaves to =
re-pull the zone data.
<*BobL*>
| -----Original Message-----
| From: bind-use...@isc.org [mailto:bind-use...@isc.org]On
| Behalf Of Mike Schrauder
| Sent: Thursday, May 12, 2005 12:54 PM
| To: comp-protoc...@isc.org
| Subject: newb =3F serial number out of sync
| =20
| =20
| I was playing around after upgrading to bind 9.2.4 from NT dns. NT
| had a serial number of 2812345678 (eg) and so the secondaries=3D20
| had that stored. I made it 3005051101 to shake things loose.
| Now the secondaries have that stored and I would like to fix
| it (2005051201) but since the secondaries (which I have no control
| over) will not update to the 'lower' number. Any ideas=3F
| =20
| If this is a FAQ, please accept my apologies and point me to it.
| =20
| =20
| Mike Schrauder
| Specialty Blades, Inc.
| =20
| =20
| =20
| =20
------------------------------------------------------------------------------
This electronic mail transmission may contain confidential information and is=
=
intended only for the person(s) named. Any use, copying or disclosure by any=
=
other person is strictly prohibited. If you have received this transmission =
in error, please notify the sender via e-mail.
Notice regarding privacy and confidentiality
OppenheimerFunds may, at its discretion, monitor and review the content of al=
l=
email communications.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
The OP stated that he does *not* have control of the secondaries. He must
use serial number math to reset them.
Dave...
> re-pull the zone data.