You can use canonical names, like server1.domain.com, it should work, but beware. Make sure you are using a local cached dns server, or make the same machine also be its own DNS server, and it has a copy of that domain. This will make the host lookup much quicker, and not be much of an issue. If you DON'T do that, you will see a performance hit, and can even see things DIE if you are having any network issues to your dns.

Example: If these are windows servers, and lets say your domain is domain.com. you can easily turn on DNS server on your windows 2003 system and tell it to be a SLAVE or secondary server for that domain, and point to a master dns server. This is the best, because it will cache all of the host records for that domain on that machine, yet when a change to the domain occurs on the master, it will filter down to the slave. This will keep your performance GOOD.

I have dealt with this when using a file share for my files like this:

\\db1.domain.com\webfiles\site

And also using dns lookup on the datasource like:

ds1.domain.com

This allows me to point them to a different server if needed, and not change code or datasources and such, but you must nail down your DNS lookups to be extremely fast and ultra reliable.

Lastly, you may also edit and use the /etc/hosts file, which is even faster than dns.

--

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/

On May 29, 2008, at 1:39 PM, Wolf, Gene wrote:

I have what I believe is a simple question. We are moving our Intranet to a datacenter located in Dallas. At that location they are very conscious of adding new servers, moving machines around, changing IP addresses, etc. They seem to be able to want to mix and match machines at will. While I agree that hardcoding server names or IP addresses in code is very bad practice it seems to me that complete flexibility isn't possible either. For example, according to the documentation the client.ini file needs to have the IP addresses of the servers serving Witango specified. For example a snippet of our client.ini file looks like:

WITANGO_SERVER=Witango1,10.200.10.51,18150:Witango1a, 10.200.10.51,18151

Is it possible to replace the IP addresses with something else that will resolve to an IP address of must the IP address be specified? Yes, we can do a global search and replace if we ever need to move servers but the powers that be want this as flexible as possible. Thanks for the feedback and thoughts.



Gene Wolf
Supervisor, Business Systems
DRS Sensors & Targeting Systems-Optronics
2330 Commerce Park Drive NE
Palm Bay, Florida 32905
Phone: 321-309-0685
           321-309-0202 (fax)

Dictionary.com Word of the Day
http://dictionary.reference.com/wordoftheday/

This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior written approval from the U.S. Department of State."

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf


________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to