Named/BIND TTL Question, pretty simple??
; foo.com.
$TTL 14400
@ IN SOA
someplace.foo.com. admin.foo.com. (
1 ; this file's version -- change
43200 ; refresh twice a day
1800 ; retry refresh every 15 minutes
604800 ; expire after 1000 hours (over week)
259200 ) ; minimum TTL of 3 day
$TTL 14400
@ IN SOA
someplace.foo.com. admin.foo.com. (
1 ; this file's version -- change
43200 ; refresh twice a day
1800 ; retry refresh every 15 minutes
604800 ; expire after 1000 hours (over week)
259200 ) ; minimum TTL of 3 day
What I THINK I want to do:
; foo.com.
$TTL 3600
@ IN SOA
someplace.foo.com. admin.foo.com. (
1 ; this file's version -- change
3600 ; refresh twice a day
1800 ; retry refresh every 15 minutes
604800 ; expire after 1000 hours (over week)
3600 ) ; minimum TTL of 3 day
$TTL 3600
@ IN SOA
someplace.foo.com. admin.foo.com. (
1 ; this file's version -- change
3600 ; refresh twice a day
1800 ; retry refresh every 15 minutes
604800 ; expire after 1000 hours (over week)
3600 ) ; minimum TTL of 3 day
Ok, what did I just do with what I THINK I want to do?
I have two servers, I would like to use one for DNS server and the other to house the website.
one the dns server is bind, and on the housing server is apache (actually both have both, but disregard that, I already fixed anything with that).
I want, if the HOUSING server goes down, that I can change dns on my DNS server foo.com.db file and within ONE hour, EVERYONE will see the NEW place I uploaded my site (incase old server crashes, I have a redundent server). I hate the 24-48 hour wait that godaddy has each time you change your nameservers, so I am trying to find a faster way. Will this work like I want it to???
ALSO, very important, IF by a bad stroke of luck, it's the DNS server that crashes and the housing server that is still online, I want the housing server to still be online and people viewing. THIS REASON is why I set the EXPIRE time REALLY high, over a week, so DOES that mean, that if my dns server goes down, that the housing server will still be accessable for one week right? Regardless if the dns server is online ( I plan that I can get a server back on its' feet minutes to hours after I find out it crashes
but maybe I'm busy and don't have time to check and it goes two days before I see the dns server has crashed, and I was working on the housing servre all that time.
Are my settings good for what I need, or does the "Expire" not mean what I think it does. here is what I READ this file as:
$TTL 3600 = no clue, just set to 3600 (1 hour anyways)
1 ; this file's version -- change (serial number, i add 1 number every time)
3600 ; refresh twice a day ( refreshes ISP cache of dns every hour so if housing server crashes, I can change housing servers and ip's and be back online within an hour)
1800 ; retry refresh every 15 minutes ( retry for dns info incase the first time it could not be accessed ???????? I think that's what it means, please inform me)
604800 ; expire after 1000 hours (if dns server is out for a day or two up to a week, the visitors will still resolve to the housing server until dns server is up again, and once dns server is up again I can change dns info in ONE hour because of the refresh right? )
259200 ) ; minimum TTL of 3 day ( ABSOLUTELY NO FREAKING CLUE, just set to 3600 ( 1 hour).
Please inform me if I am WAY off base or how I can make it do what I need to do. This is a CONTIGNECY pre planning I am doing, so please no flames or bashing or "WHAT IN THE WORLD WOULD YOU WANT TO THIS FOR".
Thanks in advance.
