dns can't connect by www

my machine is debian sarge 3.1,

at client,
I success connect http://cartonus.com, but can't connect http://www.cartonus.com

Code:

cat /etc/bind/db.cartonus.com $TTL 604800 @ IN SOA cartonus.com. root.cartonus.com. ( 1 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS cartonus.com. @ IN A 203.aa.bb.cc dns IN A 203.aa.bb.cc www IN A 203.aa.bb.cc ftp IN A 203.aa.bb.cc

This could be any number of problems:

Is this DNS server open to public use? (i.e. are you hosting your own domain?) It could be that your system is asking your ISP's DNS server and getting a 'not known' response for the www address.

Does your web access go through a squid proxy (check proxy settings in your browser)? It could be asking internet nameservers that have no idea about your internal IP address structure, and even though your machine can sucessfully look up the www address, your proxy server (which your browser is asking for the pages) cant.

Is your DNS server actually running? Did you restart named after you changed the config?

Is the web server running? You dont have any firewalling service blocking access to port 80 on the web server machine do you?

Quote:

Originally Posted by Roxoff

This could be any number of problems:

Is this DNS server open to public use? (i.e. are you hosting your own domain?) It could be that your system is asking your ISP's DNS server and getting a 'not known' response for the www address.

Does your web access go through a squid proxy (check proxy settings in your browser)? It could be asking internet nameservers that have no idea about your internal IP address structure, and even though your machine can sucessfully look up the www address, your proxy server (which your browser is asking for the pages) cant.

Is your DNS server actually running? Did you restart named after you changed the config?

Is the web server running? You dont have any firewalling service blocking access to port 80 on the web server machine do you?

1) It comes to normal now.
2) It may cause by cache or something else. it returns to normal after
restart dns, restart apache, restart proxy at client, clear the cache at client and reboot both finally.

interesting topic... my dynamic DNS does the same thing... except that i'm sure it used to work with the www. I went to update the IP adress one day and at first i though it hadnt worked... then i realised it worked but without the www. weird... anyone know why that would happen?