Apache 2 configuration problems - Cannot resolve domain
 

Hullo all

I've recently installed apache 2 on my server (running Debian, managed by Bytemark hosting, it is a virtual server, using Usermode Linux). All is working well, apache is serving pages:

http://212.13.209.171/

As can be seen. However I'm trying to get it to resolve the domain www.cxv.cc. The information is on the DNS servers of the company who manage the server. They have confirmed that the information is up there, so there shouldn't be a problem there.

Here is my http.conf file:

http://212.13.209.171/httpd.conf.txt

Using the command ./apachectl -t (to check the syntax of httpd.conf) works fine, no errors there.

I've added the following line to the /etc/hosts file:

212.13.209.171 cxv.cc cxv

I've even used wget (from the same server admittedly) to get the index.html page I've put up there, using:

wget http://www.cxv.cc/index.html

But when I try the same with a browser (Firefox) it cannot resolve the host. I'm using Win XP to try and view the webpages. According to my log files everything is working too.

Would I need to add www.cxv.cc to my hosts file? Should I be adding a similar line to /etc/hosts.allow?

What have I missed? I'm getting rather confused as to what to try next!

TIA

Matt

Well your www.cxw.cc is pointing somewhere else and not at the IP address you've provided. it cannot, hence serve your pages

H:\>nslookup

> set type=a
> www.cxw.cc
Non-authoritative answer:
Name: www.cxw.cc
Address: 206.253.214.102
>


Get them to point the "A" address of www.cxw.cc correctly and everything should be OK

if you add www.cxw.cc to the 212.13.209.171 then yes it would work but ONLY on that computer. Not for everyone on world wide web.

My domain is www.cxv.cc *not* www.cxw.cc. I'm assured by the guys running the nameservers that all the information has been added there correctly. That is why I'm thinking it is a Apache cinfiguration problem.

Cheers

Matt

Hmmm... just try doing an nslookup www.cxv.cc
I don't get anything on that adress, so I'm sure the mistake is at the nameserver's side
when I do an nslookup on the ip adress it resolves to:
hugh.vm.bytemark.co.uk
so My guess is that it is a nameserver problem.