Can someone give some insight to 4 fully qualified hostnames I can use for our new server setup. Assume the name of the website is helloworld.com We have the following:

  • A Webserver
  • A Failover Server
  • A Storage Server
  • A Database Server
link|improve this question
feedback

2 Answers

up vote 1 down vote accepted

What is your expansion plan for the future?

A generic set up that allows for scalability (more machines in the future) would look like this:

web1.helloworld.com
standby1.helloworld.com
files1.helloworld.com
db1.helloworld.com

If the failover is for the web server, you may want to try: web2.helloworld.com or backup2.helloworld.com or something like that.

(You may start things with 1 or 0.)

link|improve this answer
This is smarter, starting at 1 for everything :-) – Kyle Brandt Nov 17 '09 at 15:34
You may not need it right away, but I'd pad those numbers with one or more leading zeros. – Dennis Williamson Nov 17 '09 at 18:37
Dennis, you're so right. I often forget to do that with other stuff and then have to write a script to fix it. Thanks. :-). – briealeida Nov 17 '09 at 21:08
feedback
  • webserver: www.helloworld.com perhaprs?
  • failover: Failover for what, www? Then maybe www2.helloworld.com
  • Storage: storage.helloworld.com
  • database: db.helloworld.com
link|improve this answer
Do I need the www for a hostname? – Jonathan Kushner Nov 17 '09 at 15:27
1  
Are you talking about names in DNS for the external network, or internal host names? You can add lots of "names" in DNS to refer to a server but have one name for the actual machine... – Bart Silverstrim Nov 17 '09 at 15:31
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.