On Sunday 29 May 2005 15:58 pm, Marko wrote:
So how do ya check TTL and is there a way to keep the record's cached for longer(maybe a week) and only update the cached ip's weekly or when i want(some command)?
The TTL is defined by the administrators of the originating domain - Google sets its TTL, The BBC set them for www.bbc.co.uk, my hosts set the TTL for my domain.... They choose times which are suitable for the domain in question.
Cause there is no point having records last less then a day
Yes, there is. As mentioned before it is a method of implementing crude load balancing for sites which a single user MAY use many times an hour (like google.) Since one use of google may actually span half an hour or more and every time you ask the browser to fech a new page it does a dns lookup a session of 15 minutes looking through results is going to be covered by the TTL of your local cache.
i generaly wont go to the same page every hour or even everyday but i might the next day and i dont want to query again cause i dont have a really fast(ISDN) connection. Currently im connected multilink 128k and the query time for suse.com is 1.6 second and nxsecure.org 3 seconds. Thats just 2 long.
You're right - it is. AND YOU NEED TO SOLVE THAT PROBLEM. I get suse.com in 18msec and nxsecure.org in 139msec. Clearly suse.com is cached, but nxsecure certainly isn't and you should be looking at 1 to 200 msec for a lookup. Your problem is NOT with the TTL of the cache, it is with your named setup. Dylan -- "I see your Schwartz is as big as mine" -Dark Helmet