• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Hosting websites best practices

I always create four host ("A") records for all public DNS zone records. I don't use CNAMES at all for my (admittedly simple) business domains:

mydomain.com xxx.xxx.xxx.xxx
www.mydomain.com xxx.xxx.xxx.xxx
smtp.mydomain.com xxx.xxx.xxx.xxx
remote.mydomain.com xxx.xxx.xxx.xxx

The first two are for the default web site and have the same IP address. I hate it when people require me to type "www.mydomain.com" to get to their web site.

The third is for the email server and the fourth is for the remote access server.
 
Originally posted by: Cloud Strife
But isn't "www.domain.com" the politically correct way? Most websites like google forward their website to www.
Click to expand...

Editing the dns zone at zonedit = free
having your domain respond every which way, every time = priceless
Rebatemonger spelled out what I do at zoneedit also.
 
Originally posted by: Cloud Strife
But isn't "www.domain.com" the politically correct way? Most websites like google forward their website to www.
Click to expand...
Creating the extra Host ("A") records is the easiest, fastest, and least resource-intensive way to directly folks to your web site. Clients searching for your site only have to do a single DNS lookup and they get what they need. Anything else requires more queries, generates more network traffic, and takes longer.

Domain Forwarding has its uses, as do CNAMES, but I wouldn't use them unless I had to.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top