Unassigned domains forward to user

Hostteam

Verified User
Joined
Oct 18, 2008
Messages
7
Hello there,

I've got a strange problem here, all the domains that redirect to my server but are not assigned to a user redirect to one single user. This is pretty annoying because typo's in the subdomain also redirect to there.

example
correct:
http://crizit.nl
wrong:
http://t.crizit.nl

I really can't find the problem anywhere, i hope someone recognizes this problem and can point me in the right direction.

Thanks!
 
I've seen this before, but I don't remember all the details. It has to do with the apache configuration. In a shared hosting environment if there's no apache configuration for the name of the site, apache will deliver files for the first site it finds for the IP as it looks through your configuration.

I'm sorry I don't remember more details but perhaps someone else will have the time to look up the difference between the configuration on a which works and a system which doesn't.

Jeff
 
Anyway without a wildcard «*» in DNS zone for the domain Apache can not get requests.

p.s. The pointed domain has a dedicated IP 178.18.87.5.
 
Last edited:
Anyway without a wildcard «*» in DNS zone for the domain Apache can not get requests.
I don't believe this is always true. If an IP# is listed in apache configuration but not captured elsewhere it will be captured somewhere. If I recall correctly.

Unfortunately I don't have time to check right now.

Jeff
 
OK, I probably need to be more clear. Let me explain what I meant. Sure wildcard in DNS zone does not influence on Apache directly, and that goes without saying.

Let's imagine that there is no a wildcard in DNS zone at all, then all request with hosts that has no A record will not get to the server (defaults domain.com and www.domain.com), and of course Apache won't serve them. And it does not matter how Apache is configured. You'll get something like:

Code:
$ nslookup blablabla.gmail.com
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find blablabla.gmail.com: NXDOMAIN

That's clear, I hope?

If we have a wildcard in DNS zone, then all requests with any hostname in it are supposed to get to the server and in this case Apache will serve them. You'll get an IP address with nslookup something like:

Code:
$ nslookup blablabla.gmail.com
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:  blablabla.gmail.com

That's what I'm talking about. And since the domain of a topic starter has a private (dedicated) IP, Apache should not additionally be configured to serve any requests in that IP.

Of course, the case, which you've mentioned above, can take place. And if I'm right this happens, when the following lines are missed:

Code:
NameVirtualHost IP:80
NameVirtualHost IP:443

That's my point of view.
 
Hey guys! I am sorry for the late reply. Indeed removing the * pointer in my DNS would stop redirecting to the package but it will not solve my problem. Also browsing to the IP will end up on that user. It is most likely the problem jeff is mentioning.

Zeiter, can you explain me wht you mean by this:
NameVirtualHost IP:80
NameVirtualHost IP:443

Thanks guys!
 
Does the account with the domain has its own private (dedicated) IP?

I'm not sure, what exactly is not clear for you with NameVirtualHost? Please be more specific. That's mostly were my supposition about Jeff's guess.
 
Back
Top