I am trying to connect custom domain to firebase hosting.
According to firebase guidline, I added TXT records which is generated by them to my DNS provider - DreamHost
But I see this error message
"We couldn't verify your domain totalbodyconsulting.com. Please check your settings and try again."
Would you hint me?
Thanks
Related
I'm helping a friend to migrate a website to his server, however, after the domain transfer the client's emails stopped working. I believe their email was hosted on cPanel with the old provider. What does he have to do to get the emails working again? The old service hasn't been terminated yet.
With the limited information I would recommend looking into the following.
Verify the MX records are set correctly.
Verify any subdomains they are using for example mail.domain.com or imap.domain.com etc are still pointed to the proper email server. Can verify old DNS records on previous domain server.
I would also look into the error the mail client is getting. For example is the error an auth error, server not found or something else.
You can use online tools such as https://mxtoolbox.com/ to verify that the dns records are correct.
I have a client hosted with Godaddy and I am willing to change to Heroku.
I have tried installing Heroku Add-ons but that is not what I am looking for.
How can I create custom accounts for sending and receiving emails with a custom account (client#site.com)
I don't want to send mails via node.js nor PHP.
Thank you!
Heroku will only host your HTTP website. You need another provider for emails.
GSuite will give this to you for example.
By setting up your DNS records properly, you will then be able to tell your domain name to point to Heroku for HTTP requests, and to your emails provider for receiving those messages.
I followed the procedures and set up firebase hosting for my domain: when the user types in domainname.com or www.domainname.com the site hosted on firebase is opened.
But my emails do no longer come through :(
Error messages include
Action: delayed - Status: 4.4.1 -
Diagnostic-Code: smtp; The recipient server did not accept our requests to connect*
It will try a couple of times and then fail.
The domainname is registered with awardspace.com. There, I have the possibility to set DNS entries for domainname.com, mail.domainname.com, www.domainname.com and mx.domainname.com
Note: I can sent emails from info#domainname.com
Resetting DNS records at my provider, disconnecting the domainname from firebase hosting and connecting the domain again from scratch solved the issue for me.
Note: the previous connection used CNAME records, no longer used / needed by firebase.
I've recently setup a new Tomcat instance on Google Compute Engine and I can access my Tomcat instance via its IP address in the browser.
I've now setup a Cloud DNS entry and had my domain registrar point my domain name to the Cloud DNS servers. However this was 2 days ago and I still can't access my website via the domain name.
The WHOIS record shows the following Name Server entries
Name Server ns-cloud-e1.googledomains.com
Name Server ns-cloud-e2.googledomains.com
Name Server ns-cloud-e3.googledomains.com
Name Server ns-cloud-e4.googledomains.com
I've also setup an A record in the Cloud DNS console based on the feedback of my domain registrar. Is there anything else I need to setup in order for all this to work?
[EDIT 1] Having a look again at the instructions provided by Google it seems the name server names they wanted me to use have changed to
ns-cloud-d1.googledomains.com.
ns-cloud-d2.googledomains.com.
ns-cloud-d3.googledomains.com.
ns-cloud-d4.googledomains.com.
I've asked my registrar to make the change in case this is the problem.
[EDIT 2] My registrar has updated my DNS records and they resolve to Google's servers. However my website still doesn't show when entered into a browser I get an NXDOMAIN error, which implies my domain doesn't exist. Does anyone have a basic example of what the Cloud DNS settings should look like? Do I need to setup A records or CNAME records?
[EDIT3] My setup is shown here (domain name and IP addresses have been faked for screenshot)
Thanks in advance.
Andy.
OK, I finally worked out the problem.
In the screenshot in my question the following changes were required.
1) Replace the A record for *.andtest.com.au with an A record for just andtest.com.au
2) Replace the www.andtest.com.au A record with a CNAME record for www.andtest.com.au which points to andtest.com.au
Now when I enter www.andtest.com.au in a browser, I see my Tomcat web page.
I am trying to set up the CRM Email Router to allow our internally hosted ADX Studio Portal to communicate with our externally hosted Dynamics CRM instance.
I have set up the Configuration profile to meet the requirements of our exchange server and created a deployment to an online service provider with the necessary details.
When I attempt to load the data the Email Router Config Manager states that it was unable to retrieve the data:
Metadata contains a reference that cannot be resolved:
'https://CRM.URL/XrmServices/2011/Discovery.svc?wsdl
When we traced the email router with Fiddler the request receives a 407 Proxy Authentication Required message:
Your credentials could not be authenticated: "Credentials are
missing."
We have tested the Email Router tool on a personal network (with no proxy requirements) and everything works correctly. However once we are on the internal network which requires the proxy the Email Router Config Manager no longer works.
We have tried using the Dynamics CRM SDK and and the crmsvcutil.exe command line tool but are not sure how it actually tells the Email Router what configuration to use.
Any help is greatly appreciated. Thanks.
The only way to resolve this is to add an authentication bypass on proxy server for the server and/or service account of the email router.
You can try add section to email router .config file, with proxy settings. This is .net app, so it should pick it up. I never tried this for email router, but might be worth a shot. look here for details
The answer we received from a MS support technician was "you need to ensure that the proxy will let through (without any modification) any requests to the CRM Web Service”.
We also tried modifying the .config file to include the proxy settings but it didn't work.
We are going to open an official case with MS. Will let you know if we ever get it working.