Adding a host into local DNS services does nothing to anything other than adding the DNS translation. There's no web virtual host instantiated, no network interface is configured, nothing. Put another way, I don't understand why you've posted that DNS server configuration image.
As for the response, nslookup and dig ask the default or the specified DNS server for the translation information, and return what was provided by the DNS server.
If you have configured a host at the specified address and schumantrophy.cauwe.skp.server. isn't working, then you're potentially getting a stale translation from an old address (if the addresses have changed, flush the DNS caches), or you've got a network problem of some ilk.
With no disrespect to Camelot, configuring multiple IP addresses on the same web host network interface (outside of a few arcane cases) is generally a waste of time and effort and IP addresses. It's a 1990s IP solution, it only scales if you have unlimited IP addresses (which, yes, is technically the case here), and is an approach that largely fell out of favor shortly after the digital certificate vendors figured out how to sell multiple-domain certificates. Use virtual hosts.
i don't know what the best or the most modern solution would be.
Actually, i wouldn't really care if the solution was state-of-the-art or slightly old-fashioned, if I already could have a working solution !
i have put a DNS screnshot to show where I was.
Starting from there, what do i need to do to establish a virtual host, hoping that it will work ? (Host name ? IP address ? Host description ?)
At this point you have two options:
a) Use distinct IP addresses for each site and use IP-based virtual hosts
b) Use the same IP address for each site and use name-based virtual hosts.
Both are equally valid, with 'name-based' being slightly more 'modern', especially since all the servers are on a private LAN anyway.
Go to System Preferences -> Network on your server and create additional interfaces on the same physical interface (e.g. 'Built-in Ethernet') as your existing address.
For each interface, set its IP address to the new address you selected and entered in DNS. This is what will enable ping and traceroute to your server - just adding the name in DNS doesn't do diddly.
Then In Server Admin, add/edit your site. For the IP address, choose the newly-created IP address. This is what binds the site to that address, so that Apache knows to serve this site when requests come in on this IP address.
In DNS, change the new sites' host entry to a CNAME (alias) instead of an 'A' record. Set the record's value to the name of your server, e.g:
svenskaklubben.be CNAME macserver.cauwe.skp.server
This tells clients that the host 'svenskaklubben.be' is really the same as 'macserver.cauwe.skip.server'.
Now, in Server Admin, add/edit the site configuration for this site and set the servername to svenskaklubben.be (or whatever's appropriate) and leave the IP address as Any.
Now Apache will look at the hostname of any incoming request and match it to the configured sites - if a request comes in for svenskaklubben.be then it will use that site's configuration, otherwise it will use the default site.
I chose option A, as this is easier to store many sites along each other for development purposes.
Thanks for this clear explanation - indeed I was missing the additional Ethernet connections.
Now, everything works as expected ! Thanks a zillion - and have a nice Sunday.
Thanks too to MrHoffmann who made me realize how complex things could be, even if they look simple !
FTP is completely disconnected from web services. FTP access is based on the user account that logs in and isn't related to the IP address or the hostname that the user connects to.
If you really, really need FTP (check because it's really something you should try to avoid) then it's a matter of setting the access rights so that specific user accounts have access to the corresponding site's DocumentRoot.