How to setup wildcard DNS subdomain

[#1]

How to setup wildcard DNS subdomain in order to open http://cdsw.<company>.com ?

It would be really useful if anybody would be able to provide with a detailed step to configure this on a RHEL box.

Thanks.

[#2]

Did you manage to do this? I am still stuck on this part. 

[#3]

You can install dns on a windows server easily.

Just google how to create dns server ON WINDOWS. Add the wildcard entries there in forward dns.

In control panel--> network--> local area network--> right click and edit ipv4 properties and set default dns server as the one on which you set.

In linux box --> vi /etc/resolv file and add nameserver <ip address> on topmost. 

do cdsw reset 

and cdsw init.

HOPEFULLY THIS WILL SOLVE YOUR ISSUE.

[#4]

Thanks Neha. 

So i did that step.In the resolv file i added the private ip as below: 

nameserver 172.31.37.124

and in the conf file i added the following:

domain = "cdsw.datacloudera.com"

master ip = "172.31.37.124"

However it is still not working. I guess i am missing something else.

I have a EC2 AWS instance running. i installed CDSW on this server. I have a public ip 35.160.249.85 and private IP as 172.31.37.124

where do i add the following as stated in the installtion manual 

 
cdsw.<company>.com. IN A 172.46.47.48
*.cdsw.<company>.com. IN A 172.46.47.48
 

[#5]

Hey,

When you hit cdsw.<companyname>.com in the url tab, the url goes to the mentioned DNS server.

Since this is set up using AWS, you can setup a DNS on AWS using maybe Rote53. Not very sure of that though.

You can go through the Routee 53 documentation for further help.

And in /etc/resolv dns server entry has to be fed the one that you set up.

[#6]

ok. I had tried Route 53. But did not work. I guess my concepts on networking need bit of refresh. 

[#7]

I give up. Unable to resolve this. 

[#8]

quick question. Are you able to open the url from open internet? 

[#9]

No, was trying to figure that out.

[#10 · Accepted solution]

Sorry for the delay providing additional details.

The wildcard DNS needs to work on both the CDSW nodes and on your computer.  For a production installation, you should configure a proper wildcard DNS entry using a domain you control.  You need to control a domain, e.g. company.com, and have proper nameservers (e.g. your internal corporate DNS or something like Route53, GoDaddy, etc).  For instance, if you control the domain company.com and the nameservers point to AWS Route 53, then you should configure the wildcard DNS entries as described in the documention within Route 53.  This will resolve the wildcard entries to your master CDSW node both within AWS and on your computer.

If you're in a corporate environment, typically these types of tasks would be done by a network administrator.

If you are only testing CDSW and do not control a domain, the easiest way is to use a service like xip.io which provides a wildcard DNS automatically pointing to an IP.  However this setup should not be used in production since it is unreliable and delegates your DNS configuration to a third party.

I hope this is helpful.

Best,

Tristan

[#11]

Hi 

Thank you so much for your information. 

So i am currently testing it. But I have hosted my cloudera single node environment on AWS EC2 instance. 

I also own a domain on godaddy www.datacloudera.com. I have changed the nameserver to the one in AWS DNS Zone. Should the hosted zone be public ? or private in a vpc?

ns-0.awsdns-00.com

ns-1024.awsdns-00.org

ns-512.awsdns-00.net

ns-1536.awsdns-00.co.uk

But i am not sure how to proceed next. What are the steps which i should take post this one ? 

[#12]

This depends on your corporate network configuration.  Private zones are only resolvable within your AWS VPC, so unless you have your corporate network connected to your VPC and DNS peering properly configured, it is often easier to configure DNS in your public zone.  You will want to set both cdsw.datacloudera.com and *.cdsw.datacloudera.com A name records to your master node.  Within AWS, it's often more flexible to point this records to an EIP so you can attach it to different nodes over time.

Tristan

[#13]

Thanks for the quick reply. This is my personal setup and I am a starter in this area. Will you be able to help me with  baby steps ? APologies for being too demanding 🙂 

what i have now done is created a DNS is route53 in public zone. And i have updated the name servers into my domain at godaddy. 

Now what should i do next in AWS? Create a record set in AWS? 

And what should i do on my EC2 instance where the Workbench has been installed? 

[#14]

Did it !! Yohuuuu !!! I can see the page and am logged in!!! Thank you so so much !! You saved my day !!

[#15]

what did you do? did you have to edit /etc/resolv in on the individual instances?

[#16]

Hi Tristanzajonc,

Thanks for the explanation.

I am using cdsw for testing only.

So, i choosen the domain service with extention of xip.io

But , while i am launching the session it displaying as below :

It stays in schedulling phase and Terminal also not opening in client side.

Firewall restriction also i have done.

Please guide me

Thanks.

[#17]

Hi,

Pasted below is part of instructions for setting up DNS subdomain:

To access Cloudera Data Science Workbench, you must configure the wildcard DNS name *.cdsw.<company>.com for the master host as an A record, along with a root entry for cdsw.<company>.com.

My question: Does "master host" above refer to the edge node or the name node of the cluster?

Thanks!

Amit