Site using www doesnt resolve

sh4ka

Well-Known Member
May 12, 2005
444
0
166
Uruguay
cPanel Access Level
DataCenter Provider
Hello,

Yesterday we registerd and created 2 domains in our server.
Everything is ok, files uploaded, dns zones created, httpd virtual host created...

The problem is that trying to browse the site trough http://www.site.com redirects me to http://XX.XX.XX.XX/ my main server IP address, this page shows a cPanel Welcome message.

But, using http://site.com/, the site is loaded ok, withouth any problems.

DNS zone shows:


Code:
; cPanel 11.11.0-BETA_16977
; Zone file for site.com
$TTL 14400
@      86400    IN      SOA     mydns1.wolo.com. admin.hostingserver.com. (
                2007092601      ; serial, todays date+todays
                86400           ; refresh, seconds
                7200            ; retry, seconds
                3600000         ; expire, seconds
                86400 )         ; minimum, seconds

site.com. 86400 IN NS mydns1.wolo.com.
site.com. 86400 IN NS mydns2.wolo.com.


site.com. IN A [B]IP_ADDRESS[/B]

localhost.site.com. IN A 127.0.0.1

site.com. IN MX 0 site.com.

mail IN CNAME site.com.
www IN A [B]IP_ADDRESS[/B]
ftp IN A [B]IP_ADDRESS[/B]
Apache virtual host code
Code:
<VirtualHost IP_ADDRESS>
ServerAlias www.site.com
ServerAdmin [email protected]
DocumentRoot /home/siteuser/public_html
ServerName site.com

<IfModule mod_suphp.c>
  suPHP_UserGroup siteuser siteuser
</IfModule>
<IfModule mod_php4.c>
  php_admin_value open_basedir "/home/siteuser:/usr/lib/php:/usr/local/lib/php:/tmp"
</IfModule>
<IfModule mod_php5.c>
  php_admin_value open_basedir "/home/siteuser:/usr/lib/php:/usr/local/lib/php:/tmp"
</IfModule>

User siteuser
Group siteuser
BytesLog /usr/local/apache/domlogs/site.com-bytes_log
CustomLog /usr/local/apache/domlogs/site.com combined
Options -ExecCGI -Includes
</VirtualHost>
Any ideas?
 

JofleyUK

Member
Sep 26, 2007
9
0
51
Looks OK

Everything there looks OK, in my experience the www is the last part of the domain to resolve, leave it for another 24hrs on newly regged domains before thinking it's the server.