No Refresh Interval?

Discussion in 'DNS Server' started by djc, Mar 15, 2006.

  1. djc

    djc Guest

    could someone give me the details of this? does it actually prevent clients
    and dhcp servers from updating the records during the interval or does it
    allow the update but just not include it in any zone transfer or ad
    replication (depending on zone type) that may occur during the interval?

    any input is appreciated. thanks.
    djc, Mar 15, 2006
    1. Advertisements

  2. djc

    Herb Martin Guest

    As I understand it (but it has never seemed important enough
    to research beyond the basics):

    NoRefresh in optimization instruction to the client to
    prevent (unaccepted) early refresh.

    This plus Refresh (the SUM) is the time a record will
    be considered still viable.

    Clients are NOT to re-registered (except for changes) until
    no-refresh expires and then must re-registerd before the
    refresh expires or risk scavening (which takes place after
    the expiration of the sum of these two -- the scavenger runs
    independently of any record and so might happen after
    expiration at ANY time between 0-Scanvenging Period.)
    Herb Martin, Mar 15, 2006
    1. Advertisements

  3. djc

    djc Guest

    thank you.

    djc, Mar 15, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.