Access Gateways --> "Edit" any exist cluster --> click the hyperlink for any existing Reverse Proxy --> click "New..." to create a new Proxy Service
Within the pop-up window, instead of being forcibly made to specify an Web Server IP Address you should instead be free to specify the Web Server DNS Name.
As I recall, the last time I brought this up several years ago it was when the LAG was still bound by the outdated DNS-related libraries of a SLES 9 base, and there were performance problems in this area that led Novell to steer people towards IP addresses instead.
But that never stopped anyone from just editing the Proxy Service definition after it was created and changing that IP address into a DNS Name.
Now the LAG / MAG architecture resides on SLES 11 SP1. I can't imagine there is still a strong enough argument to prevent people from choosing to use original webserver DNS names if they so desire.
And this must be a relatively simple UI change that you could immediately enact.
Thank you,
- Stefan
Within the pop-up window, instead of being forcibly made to specify an Web Server IP Address you should instead be free to specify the Web Server DNS Name.
As I recall, the last time I brought this up several years ago it was when the LAG was still bound by the outdated DNS-related libraries of a SLES 9 base, and there were performance problems in this area that led Novell to steer people towards IP addresses instead.
But that never stopped anyone from just editing the Proxy Service definition after it was created and changing that IP address into a DNS Name.
Now the LAG / MAG architecture resides on SLES 11 SP1. I can't imagine there is still a strong enough argument to prevent people from choosing to use original webserver DNS names if they so desire.
And this must be a relatively simple UI change that you could immediately enact.
Thank you,
- Stefan