Hi all,
I am about to rollout Win2k on our network and having some problem with DNS issue. Let me try to explain the problem below:
1. We'd like to do a DNS mapping for our database server.
2. Our production database server is called sql01 and our backup database server is called sql02
3. We'd like to do a DNS mapping so that our applications call upon 'database' instead of 'sql01' or 'sql02'. This is done to avoid maximum downtime on the database server. DNS alias "database.corp.mydomain.com" would point to sql01.corp.mydomain.com most of the time. If sql01 fails, we can quickly make a DNS change in our Win2K DNS server to point it to sql02.corp.mydomain.com, restore the database quickly and we are back in business again.
4. The above works fine in our current NT4 production environment.
5. The above doesn't work fine on our test Win2K environment.
To explain more on our current situation:
1. We can ping database.corp.mydomain.com and it would resolve to sql01 IP address fine.
2. When we point our application to sql01.corp.mydomain.com, it works like a champ.
3. When we point our application to database.corp.mydomain.com, it broke.
4. sql01 is a virtual server sitting on Win2K cluster.
Our questions are:
1. Can we still map DNS alias like that in Win2K environment?
2. If yes, what do we need to change? Network wise, it seems that DNS alias is working fine.
3. If no, where can I find some whitepaper clearly explaining the situation ?
Our applications are in-house applications that points to the SQL server. The server name is hard-coded in the application.
Thank you for staying through this long and boring message.
email me at err@errsolutions.com if you got any clue 🙂
eRr
I am about to rollout Win2k on our network and having some problem with DNS issue. Let me try to explain the problem below:
1. We'd like to do a DNS mapping for our database server.
2. Our production database server is called sql01 and our backup database server is called sql02
3. We'd like to do a DNS mapping so that our applications call upon 'database' instead of 'sql01' or 'sql02'. This is done to avoid maximum downtime on the database server. DNS alias "database.corp.mydomain.com" would point to sql01.corp.mydomain.com most of the time. If sql01 fails, we can quickly make a DNS change in our Win2K DNS server to point it to sql02.corp.mydomain.com, restore the database quickly and we are back in business again.
4. The above works fine in our current NT4 production environment.
5. The above doesn't work fine on our test Win2K environment.
To explain more on our current situation:
1. We can ping database.corp.mydomain.com and it would resolve to sql01 IP address fine.
2. When we point our application to sql01.corp.mydomain.com, it works like a champ.
3. When we point our application to database.corp.mydomain.com, it broke.
4. sql01 is a virtual server sitting on Win2K cluster.
Our questions are:
1. Can we still map DNS alias like that in Win2K environment?
2. If yes, what do we need to change? Network wise, it seems that DNS alias is working fine.
3. If no, where can I find some whitepaper clearly explaining the situation ?
Our applications are in-house applications that points to the SQL server. The server name is hard-coded in the application.
Thank you for staying through this long and boring message.
email me at err@errsolutions.com if you got any clue 🙂
eRr
