|
Hi, Sorry about the long-winded question I've never dealt with DNS before. I just opened a Pro account as I have about 30 domains which I intend to point to cloud hosting servers. I'm trailing cloud hosts so may need to switch the IP's the domains point to if I switch cloud hosts. I can control the nameservers with my registrar. This was my understanding:
Is this correct? I tried to set this up with one domain, I'm unsure whether I need to transfer the domains and if I need Custom DNS or Secondary DNS. What is the best way for me to do this? Thanks! Simon |
|
If this is just for testing and playing, then DynDNS Pro and CNAMEs at your current DNS hosting service is just fine. If you're looking for a more professional solution then look for the following: Great, this is just for playing in the short term but I will need a more solid solution once I've decided where my sites will live. To clarify they are many different domains, some are miss-spellings eg(example.com, http://exmple.com, http://exampe.com) some are differnt top levels(example.com, http://example.co.uk) and some are just plain different(example.com, http://foo.com, http://bar.com, http://domain.com). Can you explain the steps I need to take? do I use secondary DNS? if so what is the "master DNS server IP address"?, where do I point my CNAME's? Thanks! Simon
Jul 28 at 11:48 PM
simon
|
|
Do not reply with a comment. This has no reliable notification. Either edit your original question, or add an answer. Secondary DNS is just a backup/fall-back for another functional primary DNS, so you really would not need it yet. You want to point your CNAMEs (or webhop redirections) to your DynDNS hostnames. Depending on what server applications you're running, you may also need to configure them to accept both, your domain names and your DynDNS hostnames. Some applications are just too sensitive about this. |