Still having issues -- is this an issue with Apache or mardns?

Greg Platt - Platt Consultants GregPlatt at ix.netcom.com
Mon Aug 4 14:25:24 EDT 2008


Okay, the domain name server appears to be working now. At least when I
point to a domain that has only ever been defined on our new server, the
domain name does resolve to my new server and it forwards the user's request
to Apache on the new server. Similarly, when I request a domain whose
registrar record has been repointed to this server, the domain also resolves
to the new server and the request gets handed to Apache on the new server.

 

However, once the request is handed to the new server, Apache ALWAYS
delivers the home page for the default domain on the server no matter what
domain was actually requested. Even though I have the new domains defined to
Apache and enabled there, Apache doesn't deliver the user to the home
directory (and thus the index.html file) for that domain. Instead, it
delivers them to whatever is the default domain on the server at the moment.

 

My conclusion is that the issue appears to be caused by Apache on the server
and is not being caused by maradns. Is that the same conclusion you come to?

 

Thanks!



More information about the list mailing list