0 TTL Problem

[Michael Kjorling]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What version is BIND 824? I suppose you mean 8.2.4.

Is the slave supposed to SOA query the master every 0 seconds? With a
0 second delay if the master is unreachable? And expire the zone after
0 seconds of not being able to reach the master? And do you really
mean to have a TTL of 0? Baaaaaad.

I tend to use (serial 1H 30M 2W 1H) in the SOA and a TTL of 1 day (1
hour in the case of zones that change a lot, or when I otherwise need
to get changes out as soon as possible), which seems to work fine. And
I would certainly not be surprised if that's where your problem is.

By the way, "test" isn't an alias but rather an address record. The
closest I have come to aliases in DNS terms is a CNAME.


Michael Kjörling


On Jun 14 2001 20:23 -0700, November wrote:

> Hello,
>
> I'm currently in the process of testing around with v824 under Win2K.  I'm
> pretty much a newbie to DNS hosting in general (with BIND, at least), and
> I'm experiencing something that doesn't make sense to me.
>
> I have a test domain set up on my system (test.com).  The contents of the
> host file (correct term?) is as such (between quotes):
>
> "$TTL 0
> @ SOA ns1.test.com. domain-admin.test.com. (
>  2001060101 ; zone serial number in ccyymmddxx format
>  0  ; slave polls master for SOA/serial number
>  0  ; slave re-polls unreachable master
>  0  ; slave expires zone after master unreachable
>  0  ; TTL for negative answers
> )
>
> ; nameservers
> @  NS ns1.test.com.
> @  NS ns2.test.com.
>
> test    A    127.0.0.1"
>
> The fact that I've got all zeros as the SOA record values implies to me that
> any change should be taken into effect immediately... at least, at the next
> service restart (I am using all zeros right now for my testing... I
> obviously wouldn't in production).  I'm probably wrong, but...
>
> I find this to be true if I just change the value of an alias... such as, if
> I change it's IP to 10.0.0.2 instead of 127.0.0.1.  When I restart the
> service, test.test.com points to 10.0.0.2.
>
> Or, if I remove the "test" alias and restart the service, and I try to ping
> test.test.com, it's not there.  That's good.
>
> But the problem is, when I put it back and restart the service, it takes a
> "very long time" (quote unquote) before test.test.com is pingable again...
> anywhere between a minute, up to maybe more than 5 minutes.
>
> I'm sure this isn't a problem with the DNS server itself, but just me not
> understanding something with the configuration (or perhaps the OS?).  If
> someone could help me out, that would be really great.
>
> Thanks,
> November

- -- 
Michael Kjörling - michael at kjorling.com - PGP: 8A70E33E
"We must be the change we wish to see" (Mahatma Gandhi)

^..^     Support the wolves in Norway -- go to     ^..^
 \/   http://home.no.net/ulvelist/protest_int.htm   \/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7KdfIKqN7/Ypw4z4RAjPvAKDjIkjQ1KKBRUmWyDMQjYySLF/D+gCgkjtr
0TeRcWk9ufyCQlOweKSdM6o=
=Jv2O
-----END PGP SIGNATURE-----