Re: CNAME and TTL

2013-12-09 Thread Matus UHLAR - fantomas
On 09.12.13 16:37, sumsum 2000 wrote: What i meant was that, when a DNS query is made to emp.bbci.co.uk, the record for it is present in the cache with TTL of 436. and since it is present, there should not be any query to the DNS server,the same goes for emp-live.bbc.net.uk and emp.bbci.co.uk.edg

Re: CNAME and TTL

2013-12-09 Thread sumsum 2000
On Fri, Dec 6, 2013 at 6:12 PM, Matus UHLAR - fantomas wrote: > On 06.12.13 15:52, sumsum 2000 wrote: > >> I am having only a forward only option in bind configuration. >> When i dig on some host which has CNAME, the cache contains a longer TTL >> for the CNAME than the TTL for the final resolut

Re: CNAME and TTL

2013-12-06 Thread Matus UHLAR - fantomas
On 06.12.13 15:52, sumsum 2000 wrote: I am having only a forward only option in bind configuration. When i dig on some host which has CNAME, the cache contains a longer TTL for the CNAME than the TTL for the final resolution of the IP. Yes, every record has its own TTL, including every record

CNAME and TTL

2013-12-06 Thread sumsum 2000
Hi, I am having only a forward only option in bind configuration. When i dig on some host which has CNAME, the cache contains a longer TTL for the CNAME than the TTL for the final resolution of the IP. However, in the example below, the CNAME is queried again when the TTL for a336.g.akamai.net