some domain names won't resolve to domains

[storyleader]

I have set up a virtual domain under a reseller account, domain0.com. I set up 5 domain pointers to it, domain1.com, domain2.com, etc.

When I pointed a browser to domain0.com, I got a 404 error. Thinking it might have to do with the recent transfer of the name servers of all these domains (5 days ago), I removed the domain pointers and changed the domain.com to domain1.com. I still got a 404 error. The same happened when I changed the domain on the user to domain2.com, etc.

Next, I changed the domain on the same account to another domain name (new to this server), new.com. It worked great. At this point, I can use any domain names as pointers or as the primary domain for this user - except the original domain0.com through domain4.com.

It sounds to me like some file got set up and didn't get deleted or changed properly when I removed the domains, but I have no idea which file or how to fix it.

Any ideas?

Thanks!

 

[nobaloney]

Lots of possible reasons. No way to begin to guess if you don't give us actual domain names of what's supposed to be working.

Jeff

 

[storyleader]

Thanks! actual domain names:

don't work:

renewalresourcesgroup.com
renewalresourcegroup.com
aliciakorten.com
kortenconsulting.com
cortenconsulting.com
portalsoftime.net
wheelofrenewal.com

work:

storybusiness.org (now the principle domain attached to the account)
makingstorieswork.com (pointer to storybusiness.org)
appliedstorytelling.org (pointer to storybusiness.org)

Does this help?

 

[storyleader]

Okay, I figured this out. The problem was entries in the httpd.conf file that DirectAdmin added when I used it to create a domain, rename a domain, or add domain pointers - but did not remove when I used it to change or delete them.

To fix the problem, I searched through httpd.conf for the various domain names that weren't working, and removed all the entries that used those domain names.

Then I went back to DirectAdmin and added pointers, etc., as I originally had done.

By the way, none of the changes to httpd.conf took effect until I ran, via the command line (not through DirectAdmin) "service named restart" and "service httpd restart". Once I completed that last step, all the domain names worked properly!

Any idea why this might have happened? Is this a bug in DirectAdmin, to leave entries in httpd.conf after a domain or pointer has been deleted? Or could I have done something wrong in my noobie-to-DirectAdmin ignorance?