I'm trying to follow the steps on https://cloud.google.com/storage/docs/hosting-static-website to host a static website on Google Cloud Storage. The domain, "peek.solutions", I bought on Google Domains.
I'm at the "Creating a CNAME alias" part. On the Google Domains Registrar, in "DNS settings" and "Custom resource records", I added one with the NAME "www.peek.solutions". However, I noticed that after I click "Add" the NAME gets truncated to "www":
Also when I try to change it to "www.peek.solutions" with the "Edit" button, like so,
After clicking "Save" I still get the same truncated "www" name.
The problem with this is that according to the instructions, I'm supposed to create a Bucket with a name that matches the CNAME I created for my domain. If I try to fill in "www" in the "Name" field, I get "The bucket is already in use":
Why is Google Domains truncating the "NAME" field when defining a CNAME alias?
Try creating the bucket with the full name, so www.peek.solutions.
You've had to show you own the domain so you should be able to create this bucket.
Buckets namespace is fully global. So if someone in the entire world had the idea to name his/her bucket 'www', this means it's not available for every other person on the planet. Other naming requirements are listed here, but you should just name it www.peek.solutions
In this documentation under CNAME, google seems to only display www as well.
I suppose it's the right way of doing it, just not an intuitive way of displaying it by Google.
Either way you can still modify the CNAME setup once you've created the bucket, so just create it and see if it works!
Related
there is an obligatory CNAME entry for one of my Google domains.
It reads:
_domainconnect.[mydomain].de CNAME 6 hours connect.domains.google.com.
What is this CNAME entry used for? As far as I have understood DNS this should not be necessary to find the actual server IP.
It is indeed not necessary for IP lookup. I suppose maybe Google itself uses it for something. I've found this https://community.cloudflare.com/t/domainconnect-in-dns-record-is-it-needed/185059 but no actual explanation of what it is.
I noticed this entry in one of my domains I have in CloudFlare that is registered via Google Domains, I also have another domain purchased there with a DNS zone on CF that does not have it. I'd say it's safe to get rid of the record — Google's dashboard never complained about it and DNS itself certainly does not need it.
It is more protocol than anything, and is not used to find your server's IP.
There is an open Web standard called Domain Connect that Google adheres to. Within Domain Connect's specifications (at this link at the time of writing) there is a section called DNS Provider Discovery that gives a full explanation of the spec Google is trying to fulfill by having that CNAME record.
To summarize what the Domain Connect docs say on this spec:
Every domain name, to meet this spec, needs to provide information on what DNS provider is being used (in your case, Google). It says that that information must be available via a TXT type DNS record with the host name of _domainconnect.<your domain name here>.
However, the docs alternatively allow for a CNAME type DNS record (CNAME is used as an alias record) with host name _domainconnect.<your domain name here> to point to another domain/subdomain that contains this TXT record with the record value the spec asks for. (Google does it the CNAME way with connect.domains.google.com. as the value.)
Whichever way this spec is done, the record value of this final TXT record should be a domain that you can do an HTTP GET request to, with the full URL being in the form of https://<the TXT record value>/v2/<your domain>/settings to get a JSON response that contains information about the DNS provider.
To see this in action:
If I go to a DNS lookup tool site like https://mxtoolbox.com/txtlookup.aspx, I can put the value of the CNAME record, connect.domains.google.com, in the search bar and see the corresponding TXT record, which has a record value of "domainconnect.googleapis.com". (Note: of course, when I use this value in an HTTP GET request in the next step, I'm going to strip off the double quotes.)
I should then be able to do an HTTP GET request to https://domainconnect.googleapis.com/v2/mydomain.de/settings and get a JSON response with information on Google as a DNS provider. I can see the JSON by just entering that URL in a browser URL bar. At the time of writing, assuming mydomain.de was a valid domain with Google Domains as its DNS provider, you should get:
{
"providerId": "domains.google.com",
"providerName": "Google Domains",
"providerDisplayName": "Google Domains",
"urlSyncUX": "https://domains.google.com/domainconnect",
"urlAPI": "https://domainconnect.googleapis.com"
}
And that entire journey was so that people/software can see who your DNS provider is, and some basic info about them, all via DNS. Phew...
Be advised that Google isn't the only big DNS provider that adheres to Domain Connect specs.
I try to achieve something like this.
My App runs on xyz.azurewebsites.net .
Now I want that the CNAME 123.azurewebsites.net redirects to xyz.azurewebsites.net
123.azurewebsites.net --> xyz.azurewebsites.net
I tried to add that CNAME in the Azure portal under custom domains put everytime I click "Add Custom Domain" I get the alert Message "Your unsaved edits will be discarded." And when I click "Ok" nothing happen.
In my notifications I get the message "Failed to add hostname 123.azurewebsites.net. 123.azurewebsites.net is invalid."
Is this a problem because I try to redirect from one "azurewebsites" domain to another "azurewebsites" domain or do I miss out something?
Adding a custom domain sometimes takes a long time to update. Check back in 20 minutes to see if the change has gone through. If you go to www.digwebinterface.com and type your custom domain name in, "xyz.azurewebsites.net" you should see that it has mapped it to your original host name, "123.azurewebsites.net".
now getting some ip instead of txt key file
please give me tips to get dns text key to publish my firebase application in google domain
From the Search Console, when you navigate to Settings -> Users and permissions, you can get to this URL where you will find the verification details. I couldn't find it nowhere in the new Search Console, only there apparently.
It appears you already verified the TXT record according to your screenshot.
Your next step would be to add the A records that Firebase is listing within the DNS records on your registrar.
I looked up your domain, and it appears you registered it with Key-Systems GmbH. This is where you'll need to configure and create those A records Firebase is giving you.
I have purchased a domain name from a local hoster.
When I go to may panel it shows the following things.
Registered Domain
I want my blogger to point here. But I have no idea what to do here.My domain name is bropoint.com. Heres what blogger says.
Blogger Details
Any one could help me with this ? Thank you.
Note
- Depending on your Domain Provider, the process may vary.
In BlogSpot
Head over to Settings > Basics and you will see an option which says Publishing >Blog address > + Setup a 3rd party URL for your blog
After adding the domain name, it will give two CNAME records. Once you have these CNAME details, login to your domain control panel.
If You are Using InMotionHosting
Click the Advanced Zone Editor button in the Domains section.
Click the drop-down menu, and choose the domain you want to edit the DNS for.
Click the drop-down menu under Type, and choose CNAME.
Add the record like this
Similarly add the second CNAME also.
You should be able to see both the CNames then.
I have created a new account on WHM and given it my domain name as the name. I then got the 2 name servers used by every site on my WHM server and inserted them into the Nameserver fields on the my registrars site. Is that all I have to do?
I know it sometimes takes a while for the domain name to perpetrate but when I type in the url it says it still parked. Is this ok?
Actually it seems what I've done is correct. The domain name did propagate eventually