Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 11-22-2017 04:43 AM
Hi there,
I have setup a cluster in a private network with internal DNS, how am I able to create external subdomain and point to the servers and access it through internet without any problem? I have created the subdomain but whenever I clicked on the Namenode UI, it will only point to inrternal hostname, not internet hostname.
thanks.
Created 11-22-2017 07:44 AM
Hello,
Based on your description, it appears the complaint is that when you click on the Cloudera Manager link for the NameNode UI, it uses the "internal" hostname. This cannot be influenced unless you changed the name of the internal host to match the hostname your browser is using. Cloudera Manager generates the URL based on the hostname and domain of the hosts on which the roles are running.
I would recommend either adding the internal hostname as an alias (maybe in hosts file) so the external clients know how to resolve to the correct IP.
There are other ways to work around this... for example, I think using a reverse proxy with URL rewrite rules may work, for instance depending on your host naming scheme would be something that is possible.
A low-tech solution would be to build a list of URLs that use the public host/IP and put them in web page rather than using the URLs generated by CM.
Ben
Created 11-22-2017 07:44 AM
Hello,
Based on your description, it appears the complaint is that when you click on the Cloudera Manager link for the NameNode UI, it uses the "internal" hostname. This cannot be influenced unless you changed the name of the internal host to match the hostname your browser is using. Cloudera Manager generates the URL based on the hostname and domain of the hosts on which the roles are running.
I would recommend either adding the internal hostname as an alias (maybe in hosts file) so the external clients know how to resolve to the correct IP.
There are other ways to work around this... for example, I think using a reverse proxy with URL rewrite rules may work, for instance depending on your host naming scheme would be something that is possible.
A low-tech solution would be to build a list of URLs that use the public host/IP and put them in web page rather than using the URLs generated by CM.
Ben
Created 11-22-2017 07:32 PM
Thank you for your reply, let me have a look on the suggested solutions.
ronnie10
Created 09-27-2018 12:37 AM