Take the 2-minute tour ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

I am using GoDaddy for my domains. Lately I've noticed that none of my domain.com addresses are mapping to the server correctly. I used "Forward" option from Domain Manager and forwarded it to www.domain.com, but it still is not working after a week.

I don't have access to the server, so I can't use redirecting or URL rewriting. What else can I do about this problem?

share|improve this question
add comment

migrated from superuser.com Feb 21 '11 at 10:36

This question came from our site for computer enthusiasts and power users.

3 Answers

This is a DNS record issue.

Make sure that you have a DNS A record called domain.com, and that it's pointing at your server. A lot of the time, people only have the www.domain.com. A record believing you have to put www. before all domain names. However, people like myself never bother typing www., so we end up putting "domain.com".

share|improve this answer
    
This is what I do every time I have this issue. It's one of the first things I set up. –  Melanie Feb 22 '11 at 3:32
    
The site I am pointing to only gives me a CNAME record, no A records. I tried creating 2 CNAME records -- one for www and the other for domain.com -- pointing to the same server, but didn't work. :-( –  picardo Feb 22 '11 at 9:55
    
There are several types of domain records. You need to create two A records, not CNAME. –  mickburkejnr Feb 23 '11 at 8:52
add comment

There you go:

RewriteCond %{HTTP_HOST} !^www\.yoursite\.com [NC]
RewriteRule ^(.*)$ http://www.yoursite.com/$1 [R=301,L]

Put that in your .htaccess file. Also, if you don't have a line which states "RewriteEngine On" in your .htaccess, make sure you put one like that:

RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.yoursite\.com [NC]
RewriteRule ^(.*)$ http://www.yoursite.com/$1 [R=301,L]
share|improve this answer
    
He said he can't use URL rewriting. –  mickburkejnr Feb 21 '11 at 11:29
    
Oh! My bad, sorry :( –  Vergil Penkov Feb 21 '11 at 16:32
add comment

Why is .www deprecated?

In order to answer this question, we must first recall the definition of WWW:

World Wide Web: n. Abbr. WWW

1) The complete set of documents residing on all Internet servers that use the HTTP protocol, accessible to users via a simple point-and-click system.

2) n : a collection of internet sites that offer text and graphics and sound and animation resources through the hypertext transfer protocol. By default, all popular Web browsers assume the HTTP protocol. In doing so, the software prepends the 'http://' onto the requested URL and automatically connect to the HTTP server on port 80. Why then do many servers require their websites to communicate through the www subdomain? Mail servers do not require you to send emails to recipient@mail.domain.com. Likewise, web servers should allow access to their pages though the main domain unless a particular subdomain is required.

Succinctly, use of the www subdomain is redundant and time consuming to communicate. The internet, media, and society are all better off without it.

Using the links at the top of the page, you may view recently validated domains as well as submit domains for real-time validation.

Taken from no-www.org

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.