Per mike, and others. If I understand. I can purchase a domain name "foo.com" I can then use that name to have sub domains, which can then be applied to the "boxes" within the internal network. I'm assuming that there's no additional charge to use the "sub domains" but that these domains can then be applied to the target instances/boxes of a digitialocean, mapped to the ip address of the actual instance as defined when the droplet/vm is created. So as an example I could buy foo.com name ip address foo.com 1.2.3.4 nfs.foo.com 1.2.3.5 mysql.foo.com 1.2.3.6 app1.foo.com 1.2.3.7 etc... (there would be a bunch more) with the name/mapping performed via dns of something like a cloudflare.. Is this getting close to being correct? Thanks guys.. ps. once I get this nailed down, the process will be to auto spin up a given instance, as well as to perform the dns updates, to create additional instances to perform the testing for the overall project. At that point, I'll look into chef/puppet/ansible/shell scripts/etc to ease the process.. On Sun, Jan 31, 2016 at 4:22 PM, Mike Wright <nobody@xxxxxxxxxxxxxxxxxxxx> wrote: > On 01/31/2016 09:57 AM, bruce wrote: >> >> Hi. >> >> Researching dns/naming. (sortof fed!!) >> >> Assume I have a server -rackspace/digitalocean/etc.. And I and I want >> to serve the DNS via something like cloudflare. >> >> The test server(s) aren't going to be webservers, they're going to be >> used to test apps.. >> >> As far as I can tell, most of the sites say you need to already have a >> "name" from a domain name provider. That can't be right, can it!! One >> can have a dns process internal to an org, providing dns names to >> machines all over the place. Granted, those machines/names might be >> internal/private. >> >> So, does one need an "actual" real name for an externally facing >> server in order to process the DNS so one can do a "ssh test@xxxxxxx" >> or can you use something like "ssh test@xxxxxxxxxxxxxxx" > > > yes > >> At the same time.. if you do need a real/actual "domain name" for the >> externally facing box, digitalocean provides for both public/private >> networks for the linux instances. If you run a private network, would >> you then be able to create your own name for the internal instances >> that would be available to the other instances on the private >> network?? > > > Pete and Shawn both give good advice. However, if you'd like a quick > solution using a fake domain name *internally* I'd recommend djbdns's > tinydns. tinydns allows you to declare yourself AUTHORITATIVE for zones > without having to connect to the root name servers. > > To test this I just created feefle.farfle. and paired it with > 53.53.10.in-addr.arpa. and it worked without a hitch. Combined with > dnscache, also part of djbdns, you would have a complete authority/recursive > name server setup for your private space. > > If this interests you let me know and I'll contact you off list. > > Mike Wright > > -- > users mailing list > users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
