i bought an domain on google domain and developed a web app in elasticBeanstalk, how do i let the web app use the domain name i bought from google?
I read the aws tutorial but looks very confusing to me.
what I did:
I created an alias record on route 53 for the eb instance, and copied the NS url to google domain dns config. it's has been done less than an hour ago.
my approach there is correct. turns out you need to wait at most 48 hrs for dns to take effect.
Thanks for posting this.
I am in the same situation that you described; bought the domain name from Google, and ended up wanting to use it with EBS on Amazon.
I would like to clarify the part about entering NS data from AWS into domains.google.com. This part appears at the top of the "DNS" page of Google Domain.
At first, I added the NS records similar to other records (CNAME, etc) that I previously created, but this did not work. Hence, I look around the page and saw that at the top of Google Domain page is where the "Name Server" information needs to be configure.
One caveat, about changing it this way if I understand the alert from Google Domain correctly, is that all other records previously created have to be re-created again in Route53.
Note: After adding the NS records, it works almost instantly for my case.
Related
So i have a senario, where i have an application which can be assigned to any client's domain without doing anything on the application side. Client just adds the Cnames (the long url that is assigned to every Beanstalk app) of the Elastic Beanstalk URL.
So when client goes to www.example1.com they will see the website, similarly when another client goes to www.example2.com they will also see the same website. Now the issue is that i use clean url's without the www. In order to do that i have to Use A records, but Godaddy only let A records to be assigned to IP addresses but in the case of AWS beanstalk. I know you cant assign IP addresses to the Application url as the instances get deleted when scaled, so is there any other solution to this problem?
I have read somewhere that cloudflare can help but have no idea how to use it.
Well i know the question is not related to programming but i can see many similar questions asked over here, so i guess it should be OK.
As always, any help is appreciated. Thankyou :)
Use Route53 with ALIAS.
You can do something manually, but the changes won't be permanent. See here for the full list of options: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options.html#command-options-general
Create a hosted zone "example1.com." in route53 and create an alias record "example1.com" pointing to the ELB of your environment in this hosted zone.
Now you can give the name servers for your route53 hosted zone to GoDaddy. Let me know if this setup does not work for you.
I've read other questions before posting this one, none of them is having the solution to what im facing. Im not new to Azure websites and already have a few websites running already but this one in particular is being a pain. I have a domain something like www.abc2wxyz.com (sorry can't reveal the name). I have made the required CNAME with awverify and awverify.www but still even after 24hrs Azure keeps giving me abc2wxyz.com or www.abc2wxyz.com. On the other hand if i add another domain called abc-wzyx.com it gets added. Could this be due to the first domain containing numerics? or is this something else?
Also whenever i visit my domain abc2wxyz.com i get that blue Azure 404 image which shows that the domain's CNAME have infact propogated and all that is left is adding it to the respected Azure Website.
I guess problem was due to the fact that I had a number in my domain name e.g. www.abc2wxyz.com but as soon as i got a domain that was www.abctowxyz.com it started working. Im not sure what the problem might be but if you know, i would be happy to know about it.
Thanks!
i am not sure whether this correct words to describe the problem, but i try my best to explain.
Suppose i deployed a cloud service with A Name. now client ask me give me something good domain name rather than A.cloudapp.net, so according to need i given him fancy domain name A.myapp.com.
After some time they thinks A is not a good name , give me B. so i change the deployment to B.cloudapp.net and then configured custom Domain Name as B.myapp.com.
Client again comes as says my customer is still using A.myapp.com. Can you do something to redirect them to B.myapp.com. with message that it moved to another address.
As i know i used only CNAME and ARecord on domain registrar . how can show a message over there. That this page is moved to other domain.
If A.myapp.com is no longer in the DNS records then the only way that it's still working is that the DNS propagation hasn't taken full effect yet. That can take even up to a few days. Once that happens then A.myapp.com should no longer resolve. This might also be working if you have a wildcard record for #.myapp.com pointing to the same A.cloudapp.net site.
You can create the A.myapp.com DNS record (if it's not still there) and point it to the same cloudapp.net app again, but then in your cloud app look at the hostname as it comes it to the request. If it is A.myapp.com show them a specific page that reminds them this is now B.myapp.com and then redirect them.
Im running SAAS where customer signs up and a script installation takes place in a subdomain, i.e., subdomain.mydomain.com and starts using the site. Now I want to allow my customers to map their FULL domain eg. www.customerdomain.com to subdomain.mydomain.com, something like bloggers.com or wordpress does. How I can do this. I am using Linux dedicated server. Help would be greatly appreciated. I dont want URL masking or redirection.
I'm currently developing a project and have recently faced the exact same issue. Here's two ways you can go about solving it:
Super-easy
A little more tricky, but not impossible
The first would be to allow domain mapping of subdomains (e.g. http://subdomain.example.com). This is dead simple for your users to setup. They would head over to their registrar and create a new CNAME record as follows:
(name) subdomain.example.com -> (record) subdomain.yoursite.com
Unlike changing A Records, this change only takes about 120 mins to fully propagate (compared with up to 72 hrs).
If your users pay for the privilege of using the domain mapping feature (i.e. it's not made available to users on a free plan), then you could could store each user's custom subdomain in your database, then check against this (in .php) when they try to access your website via their custom subdomain. If they're allowed, do nothing, otherwise redirect them to an alternate url.
So that's the easy one over and done with. Now for trickier option. If you have a dedicated IP address, or in your case a dedicated server, you can use the cPanel API to dynamically create A Records, this way users would be able to map their domain (rather just their subdomain) to your website. You would need to make the following A Record for your customer, together with getting them to update their domain's A Record with your dedicated IP address:
Your server:
(name) customersdomain.com -> (record) subdomain.yoursite.com
Customer's registrar:
www -> (record) [YOUR IP ADDRESS]
I'm not going to detail the API process for you, but you can read through the documentation here:
http://docs.cpanel.net/twiki/bin/view/SoftwareDevelopmentKit/ApiAuthentication
Anyways, I hope this helps and that you have fun building your website!
J
The (name) represents the custom domain belonging to your customer (e.g. customerdomain.com). The (record) would point to their subdomain on your SAAS site. So if I signed up to your website with a username of 'nike', you would use 'nike.yoursite.com'.
J
Install the wordpress domain mapping plugin, obviously your wordpress installation is setup for Wordpress MU.
Now the way I understand it you want to give your bloggers the opportunity to host their blog on their own personal domain while still hosting on your sever. Under "Domain Mapping" in "Settings" of "Network Administrator"(Super User).
There is Domain Options:
You want to check the User domain mapping page that's Option 3.
This will allow your blog users to specify the domain of their personal site. One thing to remind them is that their DNS records should point to your web server.
So:
i have a domain example.com
i have a microsoft azure project at example.cloudapp.net
i used a CNAME record to make www.example.com work with example.cloudapp.net.
now the problem:
the domain without the www. part does not work!
i don't have any options to redirect it in my domain provider account. I can only set: A, MX, CNAME, TXT, AAAA or SRV records.
The CNAME and A don't work. I've try CNAME but it dosen't work for example.com. For the A record you have to provide a IP, which is also not very smart for a azure account.
The only record i can imagine to accomplish this is the SRV, but i don't know how to use it properly. Any help or suggestions?
with best regards,
cris
This is more DNS managing question then Azure question.
You can certainly use A record with your Azure deployment. It was at least 6 months back in time (if not longer) when MSFT announced the persistence feature of a VIP (Virtual IP Address). Which means that your deployment (once deployed!) will have 1, non-changing public IP address as long as you do not delete the deployment! That VIP will be persisted across upgrades.
You can find out more about managing deployments here. And here there is a full section "Persitence of VIP", where it is explained how your VIP address is persisted.
So, just A record to your VIP address, and it will work as long as you do not delete the deployment. Who needs to access a deleted deployment anyway. Just try to not forget to update the A record when you create new deployment in case you deleted old one.
UPDATE **
I just made couple of checks and I think it's worth trying following SVR record:
_http._tcp 21600 IN SRV 10 10 80 yourservice.cloudapp.net.
Note the dot at the end, it is essential and important!
(I will try it myself as soon as I can - it is definitelly worth exploring this)
UPDATE 2 **
Interesting observation. I made one such record for one of mine domains. However the result is plain redirect to http://yourservice.cloudapp.net/ and not staing on http://mydomain.com/. So the result is - SRV cannot be used. Just use A record to point to your VIP.