Cached CNAMEs

[Danny Mayer]

At 04:03 AM 9/13/02, DJ wrote:
>On a cache server I have a user looking up noddy.com which is a CNAME for
>fred.co.uk

If noddy.com is a domain name, then it's illegal for it to have a CNAME. That's
a "CNAME and other data"error.

>so the cache server looks up noddy.com and receives the response that it is
>a CNAME for fred.co.uk.
>The cache then looks up fred.co.uk and receives the response with the A
>record 10.20.30.40
>
>Now does the cache
>
>a. Cache (i) noddy.com is a CNAME for fred.co.uk AND (ii) fred.co.uk A
>record is 10.20.30.40
>
>OR
>
>b. Cache that noddy.com 'translates' to 10.20.30.40
>
>
>The second question is that I want to change noddy.com to be and A record
>and fred.co.uk to be a CNAME for noddy.com
>My question is that if I do is is there ANYdanger on a cache that it will
>have cached as in (a) above BUT the TTL of fred.co.uk has timed-out so it
>now holds fred.co.uk as a CNAME for noddy.com (which it still holds itself
>as a CNAME as its TTL has not expired) i.e. a CNAME loop on a cache.
>
>OR will the above never happen ???

If fred.co.uk is a domain name then the same applies: It's illegal to have a
CNAME for the node.

Danny