> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of JD Runyan > Sent: Thursday, November 17, 2005 9:31 AM > To: Main Discussion List for KPLUG > Subject: Re: DNS=> CNAME always bad idea? (Use A records > instead always?) > > CNAME is useful for a lot of things in a world with dynamic > IP addresses. I use CNAME for pointing to hosts in other > domains that may > change IPs. Something like jason.bar.com => > jason.customer.bar.foo.com. I don't control anything but my > content at the latter, so IP and such may change without my > knowing. This allows me to give a short name for it.
A more concrete and real world example is the use of dyndns.com or similar service for name resolution of home machines behind a residential broadband connection. For me, I have a leased server that's hosting a number of my domains, including say mydomain.com. I also like to ssh into my home machine. Instead of trying to remember if it's homemachine.dyndns.org or homemachine.dyndns.com or homemachine.someotherservice.TLD, I have a CNAME of homemachine.mydomain.com pointing to my dyndns FQDN. Works great... -Jon -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
