I recently acquired a domain while buying a logo and some business cards through logomaker.com. I took this opportunity to claim the domain that I want to use for my rails app on heroku (Was this a mistake?).
Currently I seem to be required to use Weebly to edit the site for this new domain (But I'm thinking about transferring the domain to my GoDaddy account for simplicity. Is this a good idea?) I'm trying to route the simple domain to my rails app. In other words, I want users to be able to type mrzschool.com and get routed to mrzschool.herokuapp.com. I haven't been able to find a way to do this through Weebly.
I also have access to DNS and nameserver settings, such as imap and pop, through logomaker.com. This seems like it might be a way to change the routing, but I'm realizing that I'm unschooled in the realm of domains and DNS.
I'd suggest you go through the the process of moving your domain registrar from logomaker to your goDaddy account, were you can keep an eye on this domain along side any other domains you've there. It's a tedious process but worth it in my opinion. However, it's optional since you have all the control you need to do that via logomaker.
The heroku docs mentions (found here) how you can point your own custom domain to your heroku app subdomain. Keep in mind that you will need to verify your account and your ownership of the domain.
You will also find some useful troubleshooting steps here.
Related
As part of the upcoming changes to Facebook Ads, you now must verify ownership of your domain name.
We operate a SaaS platform where user content is hosted on subdomains (myaccount.example.com etc). We need these users to be able to verify ownership of their domain so they can track their own events. We have enabled them to add the meta tag on their domain, and this verifies okay.
<meta name="facebook-domain-verification" content="codefromfbhere" />
However, the problem is, when you go into 'Events manager' -> 'Aggregated event measurement' -> 'Configure web events', it shows me the root domain instead of the subdomain I just verified (e.g. example.com instead of myaccount.example.com).
This is possible, as Leadpages has achieved the same goal. When you add in a Leadpages subdomain, you're able to verify it via meta tag, and it shows the subdomain in the 'Web event configurations' area.
I don't see any extra headers that they have provided or anything else that would enable this.
How do you mark subdomains as independent from the eTLD+1?
I wanted to chime in with the perspective of someone who works for Facebook. For most businesses, even ones that host pages for other businesses, Aggregated Event Measurement without anything extra is the correct solution.
Advertisers who do not own their own domains will not be able to verify the domain for the purpose of event configuration in Ads Manager. Advertisers may consider purchasing their own domain to continue running their campaigns uninterrupted, or moving toward link clicks/landing page views for campaign optimization and reporting. We are currently investigating other solutions for this use case but do not have any additional information to share at this time.
For a very small number of businesses already on the Public Suffix List (PSL) subdomains will be able to get data as if they were a root domain. This is because being on the PSL basically makes the root domain name act as if it was a TLD (such as “co.uk“ or ”gov.au“). In almost every case it does not make sense for sites to request to be added to the PSL as this dramatically changes how the Public Suffix listed domain name will function.
The PSL process is intended only for platform providers that provide subdomains for large numbers of small businesses which really ought to be treated as though they were in fact separate domains.
The Public Suffix List is not useful, nor intended to be used as a means to gain additional subdomain events reporting. Adding a domain name to the PSL means that there will be total cookie separation between subdomains and that cookies will become disabled on the root domain. If you a domain gets added to the PSL you'll not have much control for that site itself. For example, if you have a /login page on that domain. This may not work as it does today if you proceeded with a PSL addition, as cookies may get disabled on the root domain.
It’s also important to note that browsers will enforce the behavior described based on their own update cadence of the PSL. Some browsers don't update their lists more regularly than bi-annually. This means that if you're on the list and a browser updates their copy of the list, and you later decide to not be on the list, there may not be an easy way to back out the effects; it's not as simple as submitting another request to get taken off of the list.
More information can be found at Facebook’s help center article here.
[Update Mar 19 2021]
Facebook just announced they will be supporting the Public Suffix List for domain verification and event configuration. This means that merchants using a registered domain on the Public Suffix List will be able to use that domain for verifying and configuring their top 8 events on the domain. For example, if myplatform.com is a registered domain on the Public Suffix List, then Jasper, a merchant with the subdomain jasper.myplatform.com, would now qualify as an effective eTLD+1 and would be able to verify "jasper.myplatform.com" and use it to configure their top 8 events in the web events configuration tool.
Read more here:
https://developers.facebook.com/docs/sharing/domain-verification
[Original Answer]
For the upcoming changes for Apple iOS 14.5, you can only verify root domain, which is example.com in your example in order to setup the web event configurations.
The only way you can do this is provide your client's a way to buy/setup their own domain on your service.
You may watch the webinar recording here
https://www.facebook.com/business/m/sessionsforsuccess
Firebase hosting requires that a TXT setting be set up to as they call it
Prove the domain is yours
I purchased a domain. It is mine. In order to set this TXT setting I have to have the domain hosted. The place I purchased the domain from sells hosting for minimum one year at a time. What is the point of firebase hosting when I have to buy hosting somewhere in order to prove that the domain is mine? Is there any way to get around this catch 22?
Proving ownership is done by putting a TXT record in the DNS. This doesn't require that you have a website hosted yet, it merely requires access to the DNS settings for your domain.
It's hard to help beyond that without knowing where you registered your domain.
Update. I took Frank's advice and set up a few Namecheap accounts. Wowie! The discount names are as cheap as 50 cents/year if you buy 1 or 5 years. Thanx for the advice. There is a caveat to using Namecheap/firebase, however.
Do not take this as if I were looking a gift horse in the mouth. I am super grateful to Google for free hosting. I merely want to warn users that firebase is not a free country. Google forces the s religion. I put in many hours of work to create my website using my girlfriend's hosting MySQL. Her hosting platform does not have an s in the URL: https. So the Angular 5 HTTP calls barf. I also included a contact page and a share via email popup. I used my girlfriend's hosting and set up a poor man's PHP web service for that. That does not work because girlfriend's hosting uses HTTP not https. So now I have to go back and recode these backend connections to use Google firebase and Google functions/SendGrid. I could have done that from the get-go and saved myself the time and aggravation.
I have signed up earlier for the google apps account which is now called as legacy and the primary domain has got expired. I am trying to bootstrap a startup ourselves and thought of using this legacy account. below are the steps I tried so see if I can change the primary domain. let me know if anyone of you know about any existing solutions.
No option to add a secondary domain because its a legacy account. Google removed the option.
Added our new domain as a domain alias.
Went through the GAM tool, Admin SDK.
There are couple of options which I could think off to achieve this.
Upgrade the google legacy account to a 30 day trial account and get the option to add a secondary domain and then make the primary domain change and downgrade. However, from what I have read in the internet, there is a risk where when I downgrade there would be only 1 license to use.
https://www.isaumya.com/how-to-change-primary-domain-for-google-apps-legacy-account/ here is a website telling me they have a script to run and make these changes and asking for 30 dollars.
https://github.com/marcelobern/Google-Admin-SDK-Domain This is another option that I came across.
I know it a sounds a bit crude but I am just trying to use a freebie till we get a funding for the startup :) Let me know if anyone of you have any solutions.
If you do the free trial, you will gain the ability to add a domain rather than a domain alias. However, you will not be able to downgrade back to legacy free until you remove the domain. (I tried this on an account I was willing to lose).
For your purposes I think you could get away with using the domain alias. Your users will need to sign in under the old primary domain name but your users can configure your domain alias as the default outgoing email address under settings/Accounts/Send mail as.
I have a domain example.com and www.example.com. I'm using Heroku and Zerigo for DNS.. Right now I have a forwarding from the root domain to the www.example.com from my Hostgator account but that's not working. I'd prefer to use Zerigo with the redirecting or by using an ALIAS. A lot of the articles I've found talk about ALIAS and ANAMES but I can't find those on Zerigo unless an ALIAS is specified by the letter A.
Does anyone have a solution to pointing naked domains to their www using Zerigo??
I have done this already -
Went to Zerigo dashboard
Clicked Add Snippet
Click Heroku
Add both of those
Change the CNAME to my heroku app name
It seems like this makes it work temporarily only.
Heroku support didn't even give me a great answer at all...
Looks like one short-term solution would be to point an A-record to 174.129.25.170
If you go to http://wwwizer.com/naked-domain-redirect they free-of-charge redirect naked domains to full domains if you point the record to that address. Also, instead of using Zerigo I did this on my domain registrar's website. But using Zerigo should work as well.
Hope this helps anyone who has this trouble in the future. Remember, this isn't the best solution but it does work. If anyone has a better answer please let us know for future reference.
EDIT on April 10, 2014
The best solution is to buy an SSL certificate for your website. With Heroku, you can use their SSL Endpoint add-on which requires you to buy a certificate elsewhere. This isn't the easiest process, but will work 100% of the time.
Happy coding
We are in the process of building a Multi-Tenant, SaaS type web app. Everything is set to go on the application part but when it comes to email there is a problem.
Each tenant/user of the application has a subdomain based account. However, there will be the option for that tenant to associate a top level domain to their account. Here is where the problem comes for us.
Basically, if the user sets up their DNS to point to our SaaS web app everything works good on the app front except that it now makes us responsible for handling their Email as well. Incoming and Outgoing.
What is the best way to handle this? I really was hoping their is a 3rd party site that handles outgoing and incoming email for multiple top level domains under one company name but am unsure.
There is always the option of doing our own SMTP/POP service, but we would really like to steer away from the responsibilities of email.
Thanks everyone,
~kvq
Can't they just setup an A record or a CNAME to point to your servers?
If they did an A record it would allow just webapp.theirdomain.com to go to your severs and everything else can just stay on their DNS.
The other option and maybe a better option is for them to setup a CNAME. Then you can just setup companyA.yourdomain.com and then they can just setup a CNAME that points webapp.theirdomain.com to companyA.yourdomain.com
You really do not want to be responsible for all of their DNS. They can keep their DNS where ever they want and keep their MX records the way they are.
I hope this helps