http://cr.yp.to/djbdns/run-server-bind.html
mai ales partea urmatoare:
*Automatic serial numbers.* With BIND-style administration, you have to
increase the serial number in your Z line, 10455 in the above example,
every time you change another line. (You don't have to worry about this
if you aren't transferring zones to third-party servers; server
replication through rsync to dns2.panic.mil doesn't rely on serial
numbers.)
You can instead replace :10455: by :: and let tinydns-data generate a
serial number from the modification time of the data file. *WARNING:* If
your serial number is around 2000000000, you'll have to set it to
4000000000, and wait for your secondary servers to get the new zone,
before you switch to the tinydns-data serial number. See RFC 2182,
section 7, for further discussion of this silly procedure. (You don't
have to worry about this if your secondary servers are using axfr-get
for zone transfers.)
Daca totusi vrei sa schimbi serial numberul trebuie sa incluzi la
fiecare zona ceva de genul linie:
Z/fqdn/:/mname/:/rname/:/ser/:/ref/:/ret/:/exp/:/min/:/ttl/:/timestamp/:/lo/
SOA record for /fqdn/ showing /mname/ as the primary name server,
/rname/ (with the first . converted to @) as the contact address, /ser/
as the serial number, /ref/ as the refresh time, /ret/ as the retry
time, /exp/ as the expire time, and /min/ as the minimum time. /ser/,
/ref/, /ret/, /exp/, and /min/ may be omitted; they default to,
respectively, the modification time of the data file, 16384 seconds,
2048 seconds, 1048576 seconds, and 2560 seconds.
Bafta,
Radu
Cristi Banciu wrote:
>Salut,
>
>De unde se modifica serialul la tinydns ?
>
>Merci
>
>
>---
>Detalii despre listele noastre de mail: http://www.lug.ro/
>
>
>
>
---
Detalii despre listele noastre de mail: http://www.lug.ro/
