I've perused numerous posts on the subject and still do not have anything working. Currently:
I've registered my domain (intertexti.com) with Network Solutions.
NS created A Records that I cannot delete.
When I try to create a C Record with the alias "www", it complains that an A Record already exists.
Somewhere I read something that web forwarding was needed, so I signed up for web forwarding, forwarding the A Records to proxy.heroku.com
I've also added my custom domains in Heroku, both "intertext.com" and "www.intertexti.com"
The app itself can be found at: radiant-basin-3170.herokuapp.com
So, what I am looking for are clear and concise instructions on what I need to do with Network Solutions A and C Records to get this properly working. I think at this point Heroku is set up correctly.
Thanks in advance, I realize this has been asked before, but none of the suggestions I have tried have worked.
Marc
I realize this is an old post and you've probably arrived at a working solution by now. Given the lack of documentation for the NS and Heroku combination, I wanted to record what worked for me.
My goal was to allow users to type the naked root domain or the www third-level name (eg: intertext.com and www.intertext.com) and access the heroku project site (eg. "radiant-basin-3170.herokuapp.com").
Various options seemed plausible. I found a useful page at dnsimple.com that provided some background on "differences-between-a-cname-alias-url".
The specific solution was:
On the Heroku side I followed the instructions at: https://devcenter.heroku.com/articles/custom-domains
And then read this page at NS even though it was for blogs:
http://www.networksolutions.com/support/how-to-forward-your-network-solutions-domain-name-to-a-free-blog-service/
With that background, I did this at NS:
Logged in to the NS account via the "Manage Account" button in the
upper right of the home page.
Selected "My Domain Names" then "Edit Advanced DNS Records" for the domain.
Selected "Edit A Records".
Set the #(none) record to 205.178.189.129 Checked the delete box for the www and *(All Others) rows. Selected "Continue" at the bottom of the form.
Selected "Edit CNAME Records"
Created a record with the "alias box" set to www Left the TTL at 7200 and selected the "Other Host" button. In the "Other Host" box entered the heroku project address (e.g. radiant-basin-3170.herokuapp.com.) Note the ending period, it was significant. Selected "Continue".
Initially the page did not reflect the edits. I clicked "return to domain details" and re-clicked the "Edit Advanced DNS Records".
I had to repeat steps 2-7 a couple of times until the records showed
A records: www and * as blank and # set to 205.178.189.129 and a
CNAME for www as the Heroku project address.
Note for step #4: The IP address (205.178.189.129) is the NS "Under construction" page. It's from the NS blog forwarding link.
I managed to get my network solutions dns resolve to my heroku app. Not saying that this is 'the' way but this is what I did.
Sign up for a free account at zerigo https://www.zerigo.com/
In network solutions click on Edit DNS and remove the two network solutions entries, mine were,
NS53.WORLDNIC.COM
NS54.WORLDNIC.COM
I deleted these and then added the Zerigo servers
A.NS.ZERIGO.NET
B.NS.ZERIGO.NET
C.NS.ZERIGO.NET
D.NS.ZERIGO.NET
E.NS.ZERIGO.NET
Step 3. In Heroku go to the Add-ons https://addons.heroku.com/zerigo_dns
Step 4. Click on the Zerigo Basic and then select your heroku app domain and click on the 'Add Zerigo Basic for Free' *
Step 5. In the Heroku App Settings domains add the network solutions domain, I added two entries
mydomain.com
www.mydomain.com (substitute mydomain for the name of your domain)
The same process is described in the heroku dev center articles 'zerigo_dns#configure-dns-servers' - although they mention using the command line to install the addon and also add the domains to heroku. I didn't follow the steps under 'Managing MX and other host records' as the domain i have does not have mail. If step 3 does not work for you then try adding the add on using the command line.
Related
I'm new to using Heroku so I'm a bit confused because I initially had my website hosted on GoDaddy, but when I added node to my web app I switched to Heroku.
So what is happening is when I visit my website using www. it goes to the correct, updated site, however, when I try the naked route it takes it to the older version of the website. I figured since it's still showing the older site with the naked route that there was a problem on GoDaddy, therefore, I updated one page on GoDaddy and sure enough, the page is updated via the naked route now.
That leads to my first question. If my website is now on Heroku, does it still need to be hosted on GoDaddy as well? Additionally, if the first question is yes, then how do I set up the naked route to point to the same site as the www. route?
I've already have the host as www with the 'points to' pointing to the Heroku domain name but still getting the problem above. This is why I believe the problem lies with the hosting on GoDaddy.
You don't need to host a copy of your site at Goddady.
In Godaddy, you must have a CNAME www pointing to heroku:
your_application_name.herokuapp.com
or
www.your_application_name.com.herokudns.com.
To use heroku for your naked domain, you can define a redirection for the naked domain to your www:
Go to My domains (https://dcc.godaddy.com/manage/)
Click on Manage connection
Set forwarding option (choose www.your_application_name.com, forward type permanent)
This is what helped me as of 2019. First, get to the list of your domain(s) on GoDaddy's interface. You'll see something like this:
GoDaddy's all domains page
Choose your domain. Once you're on your domain's settings, scroll to the bottom and click on 'Manage DNS'. You should see some records created, if there are any.
ACTUAL CONFIGURATION
FIRST STEP:
Create a CNAME record(there should be an 'add' button somewhere). The record should have the following parameters - Type - CNAME, Host - www, Points to - enter the link heroku created for your app.
creating a CNAME record on GoDaddy's
Sometimes when there are other old CNAME records, it'll throw an error. Erase old CNAME records and try again.
SECOND step:
Go to your terminal and enter the command 'host www.yourdomain.com'. If the CNAME record was successful, you should see the heroku domain you enter earlier. IMPORTANT - You should also see a bunch IP addresses which we will need.
THIRD step:
Create 'A' records for all the IP addresses provided on the 'host www.yourdomain.com' terminal command. They should have the following parameters: Type - A, Host - #, Points to - IP address, choose TTL custom and type 600 seconds.
This should do it
I am trying to build my first website on a domain that I purchased through Google Domains. I have followed this tutorial but am still unable to reach my site by visiting www.mysite.com
I have ensured that index.html and 404.html are set to public-read and I can see them by clicking on the public link button in the console, but that takes me to https://storage.googleapis.com/www.mysite.com/index.html
I want to simply be able to type www.mysite.com and see my index.html document.
I have added a record set with DNS Name www.mysite.com and Data c.storage.googleapis.com but still have no luck.
What am I missing?
UPDATE
This tool shared by a commenter below shed a bit more light on what seems to be causing the issue. It looks like my registrar setup is not finished, but I am not sure how to do so.
I noticed that when I search for www.mysite.com, every field says No record found, but when I search for just mysite.com (no "www"), some fields are populated (not AAAA, CNAME, A, SPF, SRV, TXT, SRV, or LOC, though)
I also noticed the "Registrar Setup" link on the Cloud DNS page, which says "This zone will not normally be usable until you register the related domain and configure these records with your registrar:" and lists ns-cloud-e1.googledomains.com for e1 through e4.
Why are fewer fields populated for www.mysite.com than for mysite.com, and what steps do I need to take to finish my registrar setup?
UPDATE: ANSWERED
I determined the issue and have posted the answer below
What error do you get exactly when you go to www.mysite.com? Does it resolve? Do you get a 404? Do you get the 404 you specified? Or a 404 from Google? Or something else?
Are you sure the CNAME is set correctly? You can check it with a tool like this:
https://www.ultratools.com/tools/dnsLookup
What happens when you go to www.mysite.com/index.html ? Did you assign pages?
https://cloud.google.com/storage/docs/hosting-static-website#optional_assigning_pages
I found the issue: I had added my CNAME entry on the Cloud Console > Cloud DNS page, rather than on my Google Domains registry. After removing the entry from the Cloud DNS page and adding it to the Google Domains Configure DNS page, my site is up and running.
I've searched everywhere about this issue and found nothing.
I want to authenticate my domain in MailChimp. My website is hosted in 1and1.
These are the instructions from MailChimp:
Create a CNAME record for k1._domainkey.YOURDOMAIN.com with this value:
dkim.mcsv.net
The problem is that 1and1 only allows CNAME records on subdomains, so I created a subdomain named mail.MYDOMAIN.com and set up a CNAME record for it with the alias dkim.mcsv.net. Waited for 24 hours and it doesn't work.
Does anyone know what's wrong and the correct way to do this?
No need to setup a subdomain. 1and1 previously didn't allow CNAME records on the main domain, but they now do. 4 months ago, I ran into the same problem you did, but I've just now verified my domain on 1and1 with mailchimp using CNAME. Just follow mailchimp's directives as they are.
1and1 do things deferently. Even though Mailchimp says - to create subdomain k1._domainkey.YOURDOMAIN.com or k1._domainkey.MYDOMAIN.com it does not work.
Also the interface accepts the values differently by separating them.
Here is what I have on "my working set up", to register your Domain authentication with Mailchimp using 1and1, please follow.
Log in and go to your Control Panel
Click Manage Domains
Click the three dots next to Actions, Select Advanced Settings.
Scroll down to DNS Settings, click edit.
For DKIM: Create a CNAME record for k1._domainkey.yourname.com with this value:
Scroll down to TXT, CNAME and SRV Records.
Click button Add record
Select CNAME from the drop down menu
In the Prefix box put "k1._domainkey" no quotes.
In the Value box put "dkim.mcsv.net" no quotes.
click Add.
To create a SPF: Create a TXT record for your domain.com
Click Add record for the last time.
Select TXT from the drop down menu.
In the Value box put "v=spf1 include:servers.mcsv.net ?all" no quotes.
click Add.
Now click Save!
All done... Wait 28/48 hours and go back to MailChimp and verify
the only correct way is to do exactly as MailChimp says - to create subdomain k1._domainkey.YOURDOMAIN.com or k1._domainkey.MYDOMAIN.com (not mail.MYDOMAIN.com) and set it value to dkim.mcsv.net.
When receiving part gets email it will found then that it refers in DKIM signature to lookup key in senders k1._domainkey subdomain.
I push my app I create with Ruby on rails on heroku and I have by default myapp.herokuapp.com
I buy my domain name on OVH I do heroku domains:add www.myapp.co to redirect to myapp.herokuapp.com.
I want to have only www.myapp.co this target and keep this went I am on the app. Could you guide to configure it on OVH.
I read this https://devcenter.heroku.com/articles/custom-domains and do what they say i don't understand check my url synestasia.co
Thank your for your help. really don't understand.
Steps needed to point (redirect) your OVH root domain (eg. yourdomain.com) to your heroku application.
Go to domain section in OVH and select your domain. Then click DNS ZONE
Remove entries (you can omit this step but OVH will tell you the same when you try to add an entry): Domain: www.yourdomain.com with types of: CNAME yourdomain.com, TXT 3|welcome, TXT l|pl (but this may depend on the
language as I'm using PL language).
Add CNAME record with www subdomain and target to your heroku CNAME domain you have from heroku website eg. my-application-fcmnqo274218034.herokudns.com. Confirm clicking next and confirm next step too.
Go to the Redirection tab and click Add a redirection. Leave both fields blank (one with domain address where you need to fill subdomain and Also redirect www.yourdomain.com checkbox unchecked. Click Next.
In the next page you should see What type of target do you want to redirect yourdomain.com to? question. Select to a web address and click Next
Next page says What type of redirection do you want to use to redirect yourdomain.com ?. Select with a visible redirection. and click Next.
In the next window select Permanent (301) redirection and then you will be asked to provide your full address as in the placeholder eg. https://www.yourdomain.com, then click next and validate the redirect rule.
Domain propagation might take a while (up to ~24h but mine was ready in few minutes). To not cache domain pointing to the DNS in your browser (as this might be fooling your with your website not found but it might work for others) you might want to use some tool to check if domain points to new servers (eg. https://dnschecker.org - that's not spam, I have nothing common with them)
Thanks to this user for posting that solution: http://community.ovh.com/t/redirection-vers-app-heroku/6392/16
To serve your domain name from Heroku, you need to tell the DNS service you use where your server is hosted.
Typically, this is done by declaring an A record DNS entry: A records expect a static IP address and so you just fill in your server's IP.
The challenge with Heroku is that it uses dynamic IP addresses, so A records are not an option.
So the other option is to declare a CNAME record: a CNAME points a name to another CNAME or an A record.
Problem is: CNAMEs are NOT supposed to be used for root domains (AKA base domain or apex domain.) They will only work with subdomains.
So you could easily declare www.example.com to point to your Heroku app (on ANY DNS service, including OVH), but not example.com.
To help with this problem, some DNS services came up with their own solutions that basically let you point a root domain to another domain.
The Add a custom root domain section of the Heroku docs mentions a bunch of these providers:
ALIAS at DNSimple
ANAME at DNS Made Easy
ANAME at easyDNS
ALIAS at PointDNS
CNAME at CloudFlare -- a bit of a misnomer
OVH offers no such option (maybe unsurprisingly given most of their business comes from hosting servers.)
Bottom-line: if your domain name is provided by OVH, either use a subdomain (e.g.: www.mysite.com) or change your NS records to use a different DNS service, one that supports CNAME-like functionality at the apex.
I'm no sysadmin. I spent a lot of time on this issue too and hope this helps.
Heroku panel -> Your APP -> Settings -> Domains and certificates -> Add Domain.
Copy DNS Target
Log in OVH
WEB -> DOMAINS -> Your domain
DNS ZONE
Field: www.yourdomain.com | Type : CNAME | Target: yourdomain.com
Click " ... " -> Change Entry -> Delete Target -> Paste Heroku DNS Target + " . (dot)"
Sometimes you have to wait 24 hours.
I'm using CloudFlare in my website and it works perfectly. Problem is, I decided to host my static files like JavaScript, CSS, etc. in static.example.com and I don't know how to set up the subdomain.
I already tried adding a CNAME record (static is an alias of example.com) and it didn't work, and as a A record (static points to IPAddress) where IPAddress is the IP address that both www and example.com use.
I'm I doing something wrong? I've waited about an hour for any DNS propagation problems and still doesn't work.
If you have added the subdomain in your CloudFlare DNS settings (settings->DNS settings), then it should start propagating out after a few minutes or so. If you're still having issues with the subdomain, please contact CloudFlare with the domain name so we can look at it.
I had the same issue until I realized I had to click on the greyed out cloud on that row to activate Cloudflare on the subdomain. This is what it currently looks like:
The instructions at the top of the page clearly say you have to do this, but I'm not one of those read the manual types for simple tasks. I guess what would have really got the point across was some sort of notice the very first time I added a subdomain on my account.
Once you've clicked the icon, then the activated proxy will be indicated like this:
Oh well, hope this helps somebody else.