I have had a VERY hard time getting a simple website up and unfortunately 000webhost support doesn’t read more than the 1st line of a submitted ticket.
We cannot and do not want to use the 000webhost name servers.
We DO want to simply point our website via an Alias to our website hosted at 000webhost.
What would be the literal path to our website?
The CPanel states:
Server Name:server22.000webhost.com
Home Root /home/a3138665
I created a Website Coming Soon index.html file
I placed it in the public_html folder
No matter what I try I cannot get the site to show up. Once we find out the literal path I can then create an CName and A Record to point our true www.company.com to the above path and it should work, but what is that path?
There isn’t a path you can use, you can however just create an A record and point it to the IP address of the 000webhost server listed in your control panel.
I take it you created the 000webhost account stating your domain name is company.com, if so just create the A record. If you have selected a sub-domain, then also park your domain in the 000webhost control panel.
You also have to create an www. CNAME record pointing to company.com in your domain control panel.
I found a problem that I believe MopedManiac was hinting at but I am not quite sure how to correct.
www.company.com works fine in a web browser. company.com errors out and doesn’t go anywhere in a web browser.
Do I need to create a DNS record so that if someone uses a web browser and accidentally or on purpose types company.com it will know to go to www.company.com?
Your DNS should laid out like this…
You have an A record for company.com pointing to 000webhost IP
You have a CNAME record www. pointing to company.com
I see how that goes, and with your information I have created the correct CName. I was under the impression that you could only have one or the other pointing to the same place, but your excellent information makes perfect sense.
Creating first the A record and then Aliases to those A records afterwards.
Thanks again for the help! This has been a great DNS lesson for me and much appreciated!
Looks like I still have a problem, and while a PM is ok i like to post here in case others have a similar problem.
Anyways, I thought I had this working but it was a cached copy. Let me post my DNS entries and see if you notice an error.
*I altered the actual domain name so as not to broadcast our website here.
A -> www -> 31.170.160.86 -> 1 Hour
CNAME -> company -> www.company.com -> 1 Hour
So when I do the www.company.com that is working great, no issues.
The company.com which we had hoped in a browser to go to www.company.com is still not working. I am not sure what I have done wrong.
Thanks for the quick reply, but I seem to have found the problem.
I was testing this on IE 8, and it would always fail and go to Bing stating it couldn’t find company.com
I then used a fresh session of Firefox, typed company.com, and it works. I also went to a VM system and verified the problem exists there, FF is ok, IE is not.
Strange. Oh well, I guess we will have to live with it as is.
If the DNS provider calls for FQDN (fully qualified domain name) entries as CNAME data, the CNAME data entry should be terminated with a period: company.com.
company.com > A record > 31.170.168.86
www > CNAME > company.com.
ftp > CNAME > company.com.
mail > CNAME > company.com.
We currently use MS Office 365 for email which is just stellar, the Sharepoint not so stellar. Currently our DNS is pretty basic and as follows:
A company 31.170.160.86 1 Hour
CNAME www company.com 1 Hour
In the A record, I am not allowed to make company.com just company, so I suspect that is the problem, but what is weird about that is the WWW is pointing to company.com and that works. Bizarre.
So we are not in any critical stage anymore thanks to Mopedmaniacs (And others’) help! Just this little annoyance which seems to be more with the MS Office 365 DNS manager than anything else at this stage.
@ corresponds to the $ORIGIN record in DNS data where it represents the FQDN (fully qualified domain name).
Many domain registrars assume that the domains they ‘sell’ will only over be addressed using example.com and www.example.com** so they simply offer the ability to enter records @ and www respectively.
@ is never used in email data within DNS records.
There is an email component to the SOA (start of authority) record, but the email address @ is always replaced with a period.