Wondering if anyone has experience setting an email while hosting a site with Netfliy? I registered a domain name using google domains and pointed the name servers to Netlify that is hosting a Gatsby static site. I would like to set up an email on a shared hosting account (I’m using hostpapa).
The Netlify DNS is set up and the site is live. I have tried adding setting the A records to the hosting IP, and MX records to mail.domain… to Netlify DNS and Google Domain records... I guess the questions might be where should the name servers point first... In both cases, the nameservers are still pointed to Netlify where the site is hosted and I get the following error:
Please transfer the domain to this servers nameservers or have your
administrator add one of its nameservers to /etc/ips.remotedns and
make the proper A entries on that remote nameserver.
For setting up an email when using Netlify nameservers (DNS zone), you have to follow the instructions provided by your email provider.
This typically requires you to enter MX records into the DNS zone on Netlify. If you're using GSuite, go to "Synthetic Domains" on the google domains site and copy everything in there to the DNS zone of Netlify. You can ignore the warnings saying that you have to use google's names servers. As an example, this is my setup for email provided by GSuite:
I use Yandex.connect and Netlify make my personal mail service.
You can check the official doc. https://yandex.ru/support/connect/dns/mx.html?lang=en
Or see my steps:
register a Yandex.connect account
https://connect.yandex.com
set Domains on Yandex
set DNS on Netlify
Related
I'm after having associated a custom domain for firebase hosting and firebase dynamic links, I was trying to setup a custom domain for authentificatio email templates. However verification for the authentification fail.
I'm using Namecheap for the DNS configuration.
Is it because the cname and # directive conflict one with each other ? I chose a subdomain for the authentification template mail:
Information is DNS servers is public information. Trying to answer what is wrong is very hard when you hide the information required.
Go to Google Domains Is your domain verified in Google Domains? If not complete that step first.
The CNAME resource records appear correct.
Most likely the last two TXT records are wrong. I am guessing that you are using something like app.example.com. The managed zone is example.com. The host is app. Your TXT records should only have *app without the managed zone example.com.
After you modify DNS server resource records be prepared to wait. Firebase will say up to 48 hours.
If my answer does not solve your problem you will either need to disclose your DNS server resource records or find someone that understands DNS to help you.
I want to create a simple web app. where user can have a form to add domain and directory name( that is already created on our server ). And it simply starts pointing the domain to that directory. What apis should I need for this? Hosting and domains can be bought from same brand, like GoDady.
Cloudflare has an API to add DNS records.
However, if you go this route, these are the prerequisites:
User's domain must already be activated in Cloudflare. At least partial-setup with Cloudflare's hosting partner (Siteground etc which have Cloudflare integrations built-in) or full-setup (the domain's authoritative nameserver points to Cloudflare).
User must trust you with their email address linked to their Cloudflare account and their Global API key.
Your web app can then make the API call to the endpoint and Cloudflare will create the appropriate DNS records to point to your server.
I am little new to hosting and so I am confused for take step. My current situation is like below
I have one big wordpress site in site ground. Domain is from Godaddy and I am using CloudFlar. I want move this site on Google cloud Instance. So I have created Google cloud instance and have installed Cpanel/WHM. I have copied site on newly created cpanel account. Now My confusion is How I should change DNS for point my domain to Google cloud.
Domain on : Godaddy, Using CloudFlare : Yes, Current Hosting : Site
Ground, New Destination Hosting : Google Cloud, My Current Domain :
example.com
For More information I have setup host like host.example.com and NameServer as ns1.example.com and ns2.example.com on Google cloud. Let me know someone can help me for required step to change DNS so I can successfully move without downtime.
Thanks a lot.
You need to update the IP address for your domain in the DNS records which are hosted either with godaddy or with cloudflare. If you are not sure, do a dig NS yourdomain.com See which dns server's are coming. and accordingly make the change.
I have signed up with cloudflare and i am running a website on shared hosting. I changed the nameservers of my domain on the shared hosting. I was expecting the website to not be available since i changed the nameservers but that has not happened yet.
I plan on confirming my domain on mailgun and having business email with google g-suite which both require i update srv settings in my domain.
My question is, why is my website still not offline and will the g-suite and mailgun changes be now done on the domain control panel or from cloudflare?.
If you changed the records at your registrar to connect to cloudflare, and then provide the appropriate A (or combination of A and CNAME) records in cloudflare you will be able to connect properly to your shared hosting and manage DNS records like SRV directly at cloudflare.
My domain verification process is completed and i also update my domain's DNS records to point to Firebase using "CNAME records" method (updated before approx 96 hours) but my site was not "Go Live". In Firebase console Hosting menu that give me below message:
Your site will go live when your domain registrar propagates your updated records.
I have already deploy my site default index.html using "Firebase deploy" CLI command and it's already successfully uploaded on "mydomainname.firebaseapp.com"
My Question: why my custom domain is not redirect to Firebase hosting?
Note: I have set default GoDaddy DNS nameservers in my domain.
I had the same problem and here is how i resolved it :
I put three parameters in the DNS record :
CNAME with www
A with 1st IP
A with 2nd IP
and then i only add two nameservers i.e.: ns1 & ns2 out of the 4 default Nameservers provided by name.com
and now my website is live on firebase.
-extra info:
it was not going live when i was using the 4 default nameservers.
it was not working with only one CNAME or both CNAME, or only both A with IP
I even contacted support on name.com they answered it is essential to have NameServer.
If you're using GoDaddy
Just try changing your host name from 'customdomain.com' to '#'
That worked for me
I could never get the "recommended" CNAME record to work. I ended up just using the two IP's for the A record. It took about 5 minutes to propagate enough to get my site in a browser.
If you are customizing your url domian with Godaddy and Firebase, you need to do the following:
Remove your existing A record (domains from Godaddy has one A record by default).
Add the A records from the instructions found in your Firebase Console.
If you want to use www.yourdomain.com, you need to set up the subdomain in Godaddy Domain (Attached image).
Maybe this step is not necesary, but I also added CNAME found in my Firebase Console.
After this changes you need to wait a few hours. If you problem persists Firebase has an excellent support as #FrankvanPuffelen says above. They solved my problems fastly.
For me after adding those 3, that #Orkun Ozen and #SarkawtNoori mentioned:
CNAME with www
A with 1st IP
A with 2nd IP
(without touching the nameservers)
in the domain service site (in my case hostinger).
I added a new domain to Firebase and called it www.mydomain.com including to mydomain.com and it worked perfectly.... (though I had to wait for it to be secure).
I deleted the custom firebase hosting site and added it again, actually when I did that it automatically was set as "connected". I didn't need to set up verification records or wait for provisioning.