Christian Seberino wrote: > > > debian.example.net CNAME -> ftp.us.debian.org > > > > *CORRECT* When you don't control the destination, you have no control > > over what debian.org does. > > Hot Dog! You may have just found a sneaky way to overcome annoyances > of DHCP addresses! All the benefits of static IPs without the price! > > This is almost as cool as your bugmenot.com suggestion! :)
moo? A CNAME works well when there is a *static* hostname to point to. Say you are on a laptop, and that laptop travels from place to place. Say, home and work. At work, you get the address of 10.3.45.6. There is no hostname pointing to that, because the network admins are too lazy to do that. Let's also assume that the 10. network was a routable on the internet :) (I don't like using what could be legit ip's for sake of argument) In this case, all the CNAME's in the wold would not help: nothing resolves to 10.3.45.6. At home, you get 172.16.34.5. Let's also assume that this is also routable! It has a hostname of 5-34-16-176.customer.example.org. You own the example.com domain, so you point laptop.example.com as a CNAME to 5-34-16-176.customer.example.org. That works as long as your laptop attaches to the IP of 172.16.34.5. If you next attach to 172.16.34.33, then your hostname (following the same conventions) would be 33-34-16-176.customer.example.org, and your CNAME would no longer point to the right thing. CNAME's only help with the other person changes their A records. It does not help the roaming system, or a system on a DHCP dynamically allocated IP address at all. > > -john -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
