new domain not working quite right...

[JacobJ]

this is strange...I registered a new domain, set it up an account on a server that i have other domains on...but now it only works if I don't type in the 'www.'

NSlookup shows its not in the system when I type in www.domain.com...but it works when I only type in domain.com..

the registrar is godaddy...

any idea what the problem is?

 

[KLin]

Originally posted by: JacobJ
this is strange...I registered a new domain, set it up an account on a server that i have other domains on...but now it only works if I don't type in the 'www.'

NSlookup shows its not in the system when I type in www.domain.com...but it works when I only type in domain.com..

the registrar is godaddy...

any idea what the problem is?

are you going to tell us what the domain is or do we have to guess?

 

[Anubis]

did you register it as www.domain or not?

 

[DeviousTrap]

Originally posted by: Anubis
did you register it as www.domain or not?

WTF?

Ask your host, or if you are hosting it yourself check if you have a dns a record set up for it.

 

[chasem]

set up a dns server on that box and forward www.domain.com to appropraite IP.

 

[Aves]

Originally posted by: JacobJ
any idea what the problem is?

The problem is that there is no "A" Record for the 'www' host.

Somewhere on GoDaddy's page you should be able to add that record to the zone (assuming they're hosting your DNS).

 

[JacobJ]

Wierd...nows its not loading at all...

I set the dns setting more than a day ago...

Whats an "A" record?

 

[jfall]

Originally posted by: aves2k

Originally posted by: JacobJ
any idea what the problem is?

The problem is that there is no "A" Record for the 'www' host.

Somewhere on GoDaddy's page you should be able to add that record to the zone (assuming they're hosting your DNS).

Bingo. Wherever your DNS is hosted needs to add an 'A' record for WWW to point to the IP of your site

 

[FoBoT]

you have to have dns for both with and without the www

 

[spidey07]

Originally posted by: FoBoT
you have to have dns for both with and without the www

although best practice says have an A record for www.domain.com. and a CNAME for .domain.com.

 

[Aves]

Originally posted by: spidey07

Originally posted by: FoBoT
you have to have dns for both with and without the www

although best practice says have an A record for www.domain.com. and a CNAME for .domain.com.

I've usually seen it the opposite way:


www.foo.com. IN CNAME foo.com.

foo.com. IN A x.x.x.x

 

[spidey07]

Originally posted by: aves2k

Originally posted by: spidey07

Originally posted by: FoBoT
you have to have dns for both with and without the www

although best practice says have an A record for www.domain.com. and a CNAME for .domain.com.

I've usually seen it the opposite way:


www.foo.com. IN CNAME foo.com.

foo.com. IN A x.x.x.x

yeah, the only problem is you're making a host record for a domain. Although either way would work it scales and works "easier" if you keep host records to the host. Makes any address changes that much easier especially if you get into load balancing/hot sites/load distribution and whatnot.

For exmample - www is the world wide web service and has 12 A records for load balancing purposes. changing a single host isn't that big of a deal because of the time to live for each record. .domain.com follows the domain TTL.

I could be way of base though. Just different approaches - I like A records to identify hosts.