Ok, you type in
HTTP://DOMAIN.COM ... and everything works correctly, I'm assuming.
However, when you type in
HTTP://1.2.3.4 ... you get the "It Works" default apache page.
Short answer - it can't look up 1.2.3.4 in the server to resolve it to your website
Longer answer - because of BIND, your server doesn't know how to look up 1.2.3.4 in its DNS tables, so if you type in DOMAIN.COM, the nameserver points to your machine, in which it resolves DOMAIN.COM to /var/www/clients/clientX/webX/web/index.html (or php if you prefer).
The reason it cannot resolve 1.2.3.4 to DOMAIN.COM, is that ISPConfig can be configured for multi-domains. So if you had DOMAIN1.COM and DOMAIN2.com, they'd both point to your IP address, but on the server, be two different directories.
In this case how would it resolve 1.2.3.4? To DOMAIN1.COM or DOMAIN2.COM?
In fact, the default Apache2 has its root document directory at /var/www ... and if you look in there, there's a INDEX.HTML file sitting there.
Recent comments
17 hours 59 min ago
20 hours 55 min ago
22 hours 9 min ago
23 hours 32 min ago
1 day 1 hour ago
1 day 2 hours ago
1 day 3 hours ago
1 day 19 hours ago
1 day 20 hours ago
2 days 25 min ago