SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Changing raw IP to FQDN in connection strings - any potential issues?


Changing raw IP to FQDN in connection strings - any potential issues?

Author
Message
torben 67322
torben 67322
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 5
Our setup
I have a small hosting setup consisting of an SQL Server (2008), a couple of webservers and an application server. They are not part of any domain - just a bunch of totally separate machines (but on the same switch).

The problem
We are currently using the server IP in the connection strings on the web and application servers. This is not optimal in case the server crashes needs to be rebuild with a different IP (or for some other reason needs to change IP).

Possible solution?
What I thought I'd do is use a FQDN instead (e.g. sqlserver.mydomain.com). This has some potential issues:
- One more thing that can break (the DNS resolution)
- There might be a slight performance hit due to the DNS resolution (though probably theoretical)
- There would be a delay when changing the DNS-record due to TTL.

To mitigate this I thought I'd add the FQDNs to the "hosts file" which should be the equivalent of a NETBIOS name (afaik - not my area of expertise).
That way I would have name resolution that did not depend on an external DNS-server and the ability to instantly change the DNS. The "real" DNS-record would simply be a fallback for machines that did not have the "hosts" entries or e.g. had forgotten to re-add them after a hardware replacement.

Are there any gotchas with this method? (issues with Windows or SQL Server). Or is there a better way to accomplish this for our kind of setup?
NJ-DBA
NJ-DBA
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1481 Visits: 1546
Sounds pretty solid to me.
torben 67322
torben 67322
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 5
Thanks NJ.
If anyone have tried this in a real-life production environment I would appreciate a short "yes - and it works" or "no - it ended in a major catastrophy" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search