- This topic has 3 replies, 4 voices, and was last updated 16 years, 4 months ago by
.
-
Topic
-
What is the general consensus of using DNS names vs IP addresses. I have generally stayed away from using DNS names simply because it takes away some of the control by introducing another variable in the connectivity of the interfaces. When migraating from one server’s hardware to another, if you using the big bang approach to migrating it can make it as simple as changing the DNS entry to switch all DNS capable connections over. The concern is when you want to do a more controlled cutover, you still need to carefully change and monitor what is being cutover, especially on the inbounds to cloverleaf. Any thoughts or advice. I have some folks that beleive that DNS is where they want to go in the configurations. I want to make the best decision possible with your help. Thanks….
-
Replies
-
-
While it can be difficult for a large organization to make a switch over to DNS, it is well worth it in the long run. If you are starting out then it is, in my opinion, a no-brainer…DNS is the way to go. If you set up your name resolution to hit the host table prior to DNS then you can have all of the control that you want. This assumes that you have admin access to the host table which is not always the case. So, you can make hassles for yourself by using the IP address or you can become friendly with the Sysadmins or the networking folks.
Each solution has its drawbacks but I find that I get along better with sys admins than I do with networking folks…lol.
-
-
We run strictly with IP numbers, although if we had more hosts we would be using the host file.
We’ve never had a good experience with DNS: very rarely the addresses will
be incorrect, more frequently the server(s) will be down, still more frequently
the lag will be unbearable.
Internet DNS multiplies all that
andis insecure to boot. T’aint wuth it.
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
