I bought a domain from godaddy for my service running on Gcr, for example: foo.com (I didn't know about the existence of Cloud Domains). In order to establish a domain relationship with my service, I first verified my domain over https://www.google.com/webmasters/verification/home
Then I added a record via Google cloud console -> Network Services - Cloud DNS and added the incoming records to my records in GoDaddy.
and when I check my Domain Name on https://dnschecker.org/, the results do not confirm the operation.
However, even though 16 hours have passed, my transaction is still not confirmed.
How can I confirm this domain? What is a wrong or missing transaction?
I've done it! But by using cloudrun only. I mapped my domain via godaddy by following these steps medium.com/#sandymadaan/domain-mapping-in-gcp-1126a8d29202.
Note:
Remove all the default A and AAAA in godaddy before putting all your DNS records from cloudrun
Related
I have application deployed in Heroku with Godaddy domain.
After trying several methods done dns setup.
Add CNAME www with value DNS target provided by heroku.
This is working fine for domain with www. But I like to open domain without www(naked domain). which is not working currently.
What I have already tried and nothing worked for me.
Add CNAME with name(naked domain) and value(heroku app url)
(a) Add a Domain with naked domain name(domain name without www)
(b) Add CNAME with name(naked domain) and value(heroku app DNS Target
value from(a))
Add Forwarding https:// with www.domain-name
Then tried configure DNS setup in cloudflare there everything problems got resolved, But there website's speed got slow and even some JS was not working. Tried several code changes and deployment, Nothing worked so finally back to GoDaddy for DNS Setup.
Somewhere got to know that CloudFlare provide CName flattening which GoDaddy not. Due to CName Flattering Redirection works fine with CloudFlare.
Please suggest me steps to resolve this. domain URL
Got response from Heroku team.
Redirecting from root domain [http://mysite.in/] to sub domain [http://www.mysite.in/] can be done at application level or on your DNS provider [GoDaddy] settings. Heroku or any other similar platforms won't have such an option.
Heroku recommends you to point the root domain to its DNS target with an ALIAS/ANAME record type. Unfortunately, Godaddy doesn't give that option. The root domain's DNS target can be an IP address as well, but the IP addresses of your application on Heroku keeps changing, at least once a day, so you can't use that as DNS target. We have an article on how you should set up the domains for a Heroku app, please give it a read https://devcenter.heroku.com/articles/custom-domains and let me know if you have any question there.
So the options you are left with is to make use of an add-on like Quotaguard which will give you a static IP address against your Heroku application, this IP can be used as DNS targets or change the DNS provider, we have a list of DNS providers which support ALIAS/ANAME record type.
I'm working on a Rails app that is hosted on Heroku and has a custom domain configured to point to the Heroku DNS target. In other words, it can be accessed at both appname.herokuapp.com and appname.com.
The owner of the app experienced an issue recently where the domain name registrar mistakenly deactivated the domain due to an error in recording the subscription payment. The issue has since been resolved, but the owner wants to know if we can set up a custom error page to show in this situation, instead of the browser error page that would normally show in this case.
I am a novice developer, but my suspicion is that this is not possible. If the registrar believed at the time that the domain did not belong to the person, why would they allow that person to decide the error page or redirect to an alternate version of the site?
Am I correct on this or is there an alternative solution?
Since DNS resolves appname.com to an IP Address. then if DNS is unavailable the machine trying to resolve the address won't have an address to connect to to get the website from.
If the DNS records have a long TTL (time to live - basically the time that it takes to flush the name from the cache of nameservers) then it will stay online even if the DNS server is offline. However this would only work for nameservers that have previously resolved those records.
We have a website displaying some weather data, which can be accessed using a second level domain name: weather.ourdomain.org
Now, the marketing department has just released a brochure with a typo, where the url is listed as www.weather.ourdomain.org
What can we do to make it work? We have a Windows server with IIS where weather.ourdomain.org is configured.
Thanks in advance!
Basically you need to configure weather.ourdomain.org as a subdomain. You can then put an A record at the Apex (weather.ourdomain.org)so it still points to whatever it points to now, and have another A record / CNAME registered at www
Obviously this all depends on whoever it is that is the registrar for your domain name and whether they allow sub domains. If they don't you can probably register Azure DNS or some other DNS service to actually run your Nameservers.
Who is your registrar? we can probably tell you what they allow.
Edit: Just to be clear, actually I only want to use a different webserver, not mail server. It has to stay the same.
I've got a 1and1 plan including webspace and email service. As 1and1 doesn't support Ruby, I created my website at Heroku.
I'm now trying to point my www.example.de url to my example.herokuapp.com domain. As this is the very first time I'm doing this, please alert me if I'm missing something important.
The website uses the 1and1 mail server. I found out that, due to that fact, I can't go the cname way but need a A Record (or ANAME Record?). I already pointed heroku to the right urls and now need to set up 1and1 and a dns service.
I registered at dnsmadeeasy.com and created an ANAME Record:
Name: [left blank]
FQDN or IP: myapp.herokuapp.com
TTL: 1800 (I've got no idea what that is)
After creating that, dnsmadeeasy.com shows me several "System NS Records" which look like nameservers?
ns0.dnsmadeeasy.com
upto
ns4.dnsmadeeasy.com
As far as I understand I now have to enter the nameservers above at 1and1.
My question now is, does this disable the by default working mail server connection? If yes, how would I point back to it from dnsmadeeasy.com? Or is there a better way to do this?
It seems the easy way to do it now is with Point DNS. They have a free developer plan: https://devcenter.heroku.com/articles/pointdns
Enter the Point DNS servers into the 1and1 Domain Manager.
The problem was solved by just adding a A-record at 1and1 pointing at Heroku. No nameservers or any extra service needed.
Here is a more detailed update:
First you have to go to the Heroku app settings. There you can add domains for your app, like www.mydomain.com.
Then you use a service to get the IP address of the server where your Heroku app instance is running. (Just get the IP address of your instance of yourapp#herokuapp.com.) Then you add this IP address as a A-record to the 1and1 app settings. Now you have to wait for the settings to propagate over the DNS servers.
Basically you point your 1and1 app to the server on which your Heroku app runs and inform your Heroku app that there probably is some app trying to reach through to it, which has a specific address, like www.mydomain.com. That's how they find each other.
I have uploaded a rails application to Heroku. I have a domain hosted with bluehost. I have assigned the domain to bluehost and set the CNAME properties of the WWW record point to the herokuapps URL. I have the # A-record pointing to the bluehost shared Host ip address. Because I dont have a HerokuApps unique IP address, I havn't assigned an A-Record.
Currently when I go to the www.rememberlenny.com and the rememberlenny.com, they are displaying two seperate sites.
Today I changed the domain record of the CNAME on WWW to the heroku app. The non-WWW domain propagates to the old shared hosting location. I want both the www.rememberlenny.com and rememberlenny.com to show the same place.
Do I wait for the DNS change to propogate, or is there some setting that I am not changing the host records?
Your ttl is set to 14400 or 4 hours. It's always a good idea to set that very low BEFORE you need to change the DNS records.
Here is info on heroku dns settings: https://devcenter.heroku.com/articles/custom-domains
Heroku does NOT support A records on the bare domains name (without the www), so you need to change that to a url redirect or forward record and remove the A record on the bare domain.
I have tried configuring Heroku custom domains using Bluehost and Hostmonster in the past (currently use Hostmonster), and in their CPanel DNS Zone Editor the TTL (time to live) for any DNS changes is 14400, or 4 hours.
I tried to lower this setting, and they don't permit it. There's no way around it - you have to accept their default TTL of 4 hours. I'm really hoping my change works, because the idea of a 4 hour trial and error cycle sounds dreadful.
Anyway, hope this answer sheds some light on what has been a hellish process - trying to get Heroku to play nicely with Hostmonster's DNS settings.
D.