July 6, 2020 at 7:05 pm
So, don't use DNS alias. This is the FQDN as a CNAME or A entry. You have one set for the current server, like
myserver.mydomain.com 192.168.0.111
Users use this to connect, assuming you have a listener for the 1433 port. This translates the myserver. to an IP.
Now, when you set up a new server, you would create a new entry, like
testserver.mydomain.com 192.168.0.121
which points to the new IP. Users can connect to that. Alternatively, someone can add an entry in their local hosts file that says:
myserver.mydomain.com 192.168.0.121
This overrides what their DNS server would use. When you have the new server ready, just alter the DNS entry.
July 8, 2020 at 10:00 pm
Sorry I am confused. The aliases is pointed to current prod server.So my understanding is the aliases cannot be pointed to new prod server until the go live. So the testing would be done with server name until then?
July 8, 2020 at 11:08 pm
Don't use alias, unless this is defined in the Native client (https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/create-or-delete-a-server-alias-for-use-by-a-client?view=sql-server-ver15)
A DNS entry is a particular type of lookup. Usually this is an A record, which is for a host. The maps the name (a.b.com) to an IP. There is a hierarchy in DNS, which allow you to override an entry in a DNS server with a local hosts entry. You can do this for testing, so clients can edit their hosts file in /drivers/etc/ and put in an entry there.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply