On Fri, Apr 11, 2014 at 2:19 AM, David Guntner <da...@guntner.com> wrote: > what you want to do is > create a CNAME record for the domain - set a CNAME of mydomain.org that > points to myhostname.someddns.com. > > Presto! Now when you try to access your home machine, you can simply > refer to mydomain.org and it will point you to the correct place. You > can also set up CNAME records for subdomains (whatever.mydomain.org) to > point to your DDNS hostname as well.
List newbie chiming in here, hope I'm not out of line! CNAMEs are immensely helpful, but they do have their limitations, so be careful. You can't, for instance, have a CNAME on mydomain.org and then also have an MX record on mydomain.org - so you'll have trouble receiving mail (unless DDNS lets you set an MX on myhostname.someddns.com, which I'm not sure about). You also can't have an SOA record, or any other type of record, on something that's CNAMEd elsewhere. Also, pointing a CNAME at another CNAME, while technically legal (I think), is potentially problematic - you may start seeing glitchiness with some clients, timeouts, etc. But as long as your needs are simple, that method will work very nicely. Among other benefits, you're free to move where your actual DDNS is hosted without anything changing - if you lose myhostname.someddns.com and replace it with myhostname.someotherddns.com, the only change you need to make is to your CNAME - everything that accesses mydomain.org will still work fine. I strongly recommend the practice. But do make sure you understand what you're doing. ChrisA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/captjjmpe2yc2od3gdrdufokmzjxoatomjhd9xmhdx2azysn...@mail.gmail.com
