Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

Establishing a Naming Convention for DNS CNAME Entries Per Application

$
0
0

We have a project to create a unique set of DNS CNAME records for each business application (both custom and COTS). This will allow increased portability and ease of migration for all tiers of an application, as well as provide flexibility for DR and application level backup and restore. These DNS records are used within our connect-strings for the apps, so that once set, they don't need to be changed as we migrate apps from one server to another, and we only need to update the back end DNS pointer to its new server alias. Our child domain for all of these records will be*.apps.multco.net.

We have two suggested naming conventions, and I'm seeking input on which path makes more sense:

App name = "sampleapp"

End user DNS (for browser-based app) =sampleapp.apps.multco.net

OPTION 1 (ADDITIONAL CHILD DOMAINS):

Web Server: PRD environment DNS:SAMPLEAPP-PRD.webiis.apps.multco.net

DB Server: PRD environment DNS:SAMPLEAPP-PRD.dbmssql.apps.multco.net

OPTION 2 (APP COMPONENT INCLUDED IN NAME):

Web Server: PRD environment DNS:SAMPLEAPP-WEBIIS-PRD.apps.multco.net

DB Server: PRD environment DNS:SAMPLEAPP-DBMSSQL-PRD.apps.multco.net



Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>