Soa record for quick changes - TCP-IP

This is a discussion on Soa record for quick changes - TCP-IP ; Hi there. We are going to implement some changes, that require su to change all dns-records in a matter of few minutes (a quarter of an hour is acceptable). We have currently lowered the TTL to 10 minutes, but are ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Soa record for quick changes

  1. Soa record for quick changes

    Hi there.

    We are going to implement some changes, that require su to change all
    dns-records in a matter of few minutes (a quarter of an hour is
    acceptable).

    We have currently lowered the TTL to 10 minutes, but are there other
    (SOA) settings, that needs to be changed in advance to make sure the
    zone can be changed in a blink with the eyes ?

    Tia

    Svenne


  2. Re: Soa record for quick changes

    In article ,
    Svenne Krap wrote:
    >Hi there.
    >
    >We are going to implement some changes, that require su to change all
    >dns-records in a matter of few minutes (a quarter of an hour is
    >acceptable).
    >
    >We have currently lowered the TTL to 10 minutes, but are there other
    >(SOA) settings, that needs to be changed in advance to make sure the
    >zone can be changed in a blink with the eyes ?


    If the servers all support the NOTIFY protocol, and you list all the slave
    servers in NS records in the zone or the also-notify statement in the
    named.conf file, then lowering the TTL should be sufficient.

    If there are some servers that won't receive the NOTIFY request or can't
    process it (e.g. they're running BIND 4) then you should also lower the
    Refresh time.

    --
    Barry Margolin, barry.margolin@level3.com
    Level(3), Woburn, MA
    *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
    Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.

+ Reply to Thread