I'm trying to connect my Heroku App via a custom GoDaddy subdomain. The subdomain is "subdomain" (for the sake of example). What I'm doing is, copying the DNS Target from Heroku and adding it in GoDaddy as a CNAME such that it is pointing to the DNS Target given by Heroku. Nonetheless, I'm getting the following error when going to www.subdomain.mysite.org
I have previously created subdomains and connected them to GoDaddy with the DNS Target that Heroku provides. Don't know what I'm doing wrong. I tried to refresh the DNS but it's not working.
Related
I have deployed a django based website on my AWS lightsail instance. the web address has a port 8000 (:8000). I own a domain on (host =fatcow.com). I have created a hosted zone on AWS and pasted the ns values to my provider(factor)'s Nameservers values. In the amazon route53, I have created a new record with a simple redirect A ipv4 and entered the resolver IP address value - my web address with port value. it doesn't work.
Also, I have read that the redirect will not work for its with port numbers. I have tried redirecting my domain to the static ip, then created another hosted zone record trying to redirect the static ip to the ip+port value - error pops up saying it is not a valid address.
I currently use the development server provided by django as it is a personal website and currently it will not have a lot of traffic - portfolio website.
Also, on my fatcow.com domain settings, the Nameservers are updated and in the whois values, new Nameservers are seen. I have only added the 4 NS values. AWS also created SOA ip values but I was not able to add them to the domain (Inputs were not taken by fatcow ).
In the NSLookup website, I can see NS values and SOA values which are on the AWS hosted zone but A records show none.
Edit: sorry for the confusion. my domain is www.chandradhar.com. I'm not a web dev but I'm trying to deploy a django based portfolio website. I have added Amazon Lightsail DNS nameservers to my domain (host=fatcow.com). the web address is :8000 port. Without the port number, the website isn't loading at all. Only with the port number along the static IP, the website loads. 'A' record isn't taking the port number. I did add a SRV record with the port number(in AWS route 53) but still doesn't work. when checked from the website nslookup.io, the nameservers are updated correctly
Not reproduceable.
> host fatcow.com
fatcow.com has address 65.254.254.33
fatcow.com mail is handled by 10 mail.fatcow.com.
Most probably your changes in DNS have already propagated.
Steps to successfully deploy one or more websites on lightsail AWS when the domain is on another website like godaddy/fatcow.
Create a dns zone in the networking section of the lightsail instance.
Copy the name servers from the dns zone and paste it in the name servers section of the domain provider (fatcow/godaddy) - it might take upto a day for the values to get updated - i used nslookup.io to see if my nameservers were updated.
Create 'A' records and SRV records pointing to the static ip of the lightsail instance.
Install Nginx
Create a simple script with the (name of the website).conf in the conf.d folder/available sites folder
Add the following script:
server
{
listen 80;
server_name domainname.com;
location / { proxy_pass http://ipAdd:PortNum;
}
}
Repeat the same code block with different domains and redirect ports. I guess we can also use 301 redirect to achieve the same.
This might or might not be the proper way of achieving what I required but it'll work.
I'm having trouble getting the custom domain I bought from GoDaddy to work with the Django app I have hosted on Heroku's free dyno. The Heroku app is accessible from the custom domain, however, I keep getting a privacy error from chrome. See below:
My Heroku dashboard confirms that I have added my custom domain. I have tried doing this through both the CLI and GUI, with no different results.
My DNS settings on my domain in GoDaddy are configured as follows. Someone had mentioned the CNAME setting should be the .herokudns domain generated by the addition of the custom domain in the Heroku dashboard, but when I make that change the website is not accessible at all. The Heroku app is named:
desolate-basin-60228 and can be accessible at https://desolate-basin-60228.herokuapp.com/
and in GoDaddy I have confirmed that my forwarding is set to http (not https as I don't need a security cert. for this site):
I also thought that it may be an issue with my Django settings.py file. So I adjusted any line with mention of https. This did not have any effect.
Does anyone have any thoughts on what I'm missing here?
Based on this Heroku help center resource, if your site needs SSL support, then it's not possible to set up a GoDaddy domain with Heroku. That could explain why you're having trouble.
However, there may be a few workarounds:
https://domainpromo.com/1831/godaddy-heroku-setup
https://medium.com/#successengineer/how-to-setup-heroku-with-godaddy-d8e936d10849
I have a django application that I launched with heroku. I have a challenge of adding my custom domain to change the www.example.heroku.com to www.example.com. I got my domain with hostgator and I have changed the cname to point to www.example.com.herokudns.com. but after 48 hours I am unable to use www.example.com and I contacted my domain provider which is hostgator but I was told I needed nameserver which is not provided by heroku. I am confused at this point as this is my first time of trying a custom domain with an heroku application
Heroku doesn't use nameservers. All you can do is point the CNAME in hostgator to your heroku app which is something along the lines of :
myapp.herokuapp.com
Double check that it is the right app domain.
You also need to add your custom domain to the heroku project through the heroku dashboard: https://devcenter.heroku.com/articles/custom-domains
I have been trying to connect my domain with my elastic beanstalk instance.
My domain was purchased off GoDaddy and I have updated the nameservers to point to AWS and verified through dig. If dig comes up with the NS, it means GoDaddy is properly configured to point to the DNS right?
The Test Record Set function also does not show any error and has a proper response returned which has NOERROR
Problem is I still receive an ERR_NAME_NOT_RESOLVED everytime I try to load the website on browsers even tried on different devices
I have also checked the alias used in my Hosted Zone and its up and running
What I have already done:
Initialized and created Beanstalk environment - Up and Running
Public Hosted Zone - Created A record for www.mysite.com
GoDaddy DNS NS - updated with AWS 4 nameservers
Checks I have done:
Internal Test Record for A www.mysite.com
Dig Command
What could I be missing?
UPDATE***
So I figured "www.mysite.com' was working but 'mysite.com' alone was not. I'm assuming route53 will automatically use the www A record? But seems like its not?
Hope ya'll could help
Thanks!
Got it to work.
Looks like besides creating a www A record, I had to create a record for the root domain i.e mysite.com in the Record Set of my Hosted Zone
Solved!
I have a basic Django website running on an AWS EC2 instance. Command I use to run server:
python3 manage.py runserver 0.0.0.0:8000
Website is accessible when I used the public IP of the EC2 instance in the browser.
EC2 Security group settings
Next step I tried was to set up DNS using AWS Route53. Created a hosted domain as shown here -
Hosted Domain
I have added record sets for www.mysite.com. and mysite.com.
My domain is registered with namecheap.com and I have added the 4 name servers shown in my hosted domain to it in the custom DNS section under name servers.
The state of my domain on whatsmydns good. I have created a health check under route53 and it shows red. The website is not accessible when I type in www.mysite.com in the browser.
I tried pinging the domain. It times out but maps to the correct public IP.
What am I missing here? Please advise.