Site displays only partially, no theming

I doubt that they are resolving other than going to the right server.  Looks to me like you are just getting a simple default page for Apache.  Looks like you're hosting on OLM, LLC.  Is that right?

I am indeed at OLM. Can you help me to get it to the right directory then?

I think you probably have to identify the sites properly in Apache.  But OLM's nameservers have to first direct the requests to your servers.  They should be able to tell you what you need to put there.  Do you have unique IP addresses for each site?

I have only one IP. But this is a Drupal multisite where multiple sites are served  from the same core/directory, so If I can get the traffic to reach my public_html directory, Drupal is supposed to take it from there.

I thoughr the nameserver thing was done?

Not themed? Well, what I get under these URLs is no site at all.
DNS is resolving to the new VPS, that much is true, but there is no custom web page - let alone Drupal - in the web root. What you see is, as DaveBaldwin pointed out already, just a default Apache page for checking web server functionality.

This could mean one of two things: 1.) you uploaded your site to the wrong place or 2.) the VPS webserver is not yet sufficiently configured. Since you say that a web control panel is running on the server (DirectAdmin) I'd venture to say that #2 is unlikely, but there is a chance that 3.) the web panel still needs to be configured.

There are lots of web control panels, and they are meant to make things easy for non-experts. But in many scenarios they tend to complicate matters enormously. In the end, they require just as much time and effort to be learnt decently as they promise to save you by not learning Linux.
So please consult the DirectAdmin manual; also check out migration howtos on the Drupal site, and the FAQs of your hosting provider.

Here's what I think is happening:
On a normal Linux server, there is a default web root folder; often /var/www, but others are possible. When a domain name gets bound to the IP of the server it points to this default directory. That's where you should find a "index.html" containing the words: "Apache is functioning normally" - which is what we see when browsing to your sites.
A web control panel alters these default Apache settings, and creates a new jailed virtual Apache environment somewhere else in the folder tree. That's where it will point external requests to - if configured to do so.

I don't know DirectAdmin. But judging by my experience with some other panels I'd assume you will have to create a new domain/site inside your panel and make the domain names point to it - via a DNS module or whatever the panel has to offer. There should be an FTP access linked to this new site which will let you connect to the correct root folder inside the panel's virtual environment; use FTP to upload simple index.html and index.php files so you can check if it works.
Once your domains display these simple files correctly, proceed with migrating, but pay attention: database access and drupal config files could still pose some problems.

Sorry, took me some 20 minutes to write my post, so it is only reflecting the first answer.

hi
can you try to apply theme again also check where is your theme is it in /httpdocs/sites/all/themes or in the main folder try applying another theme and see what happens

You are right, I see that now, it displays not an unthemed page but only the line that Apache is functioning. And you are right as well that Direct Admin needs some further configuration, but alas you are not familiar with it (not Drupal apparently).

I can go to Olm-support, they usually help, but you guys here are usually a lot faster. I was thinking it was mainly a matter of changing the httpd.conf file, but so far I get no confirmation of that.

hi
i think i know what the problem is there is a index.html file your httpdocs which is perventing your drupal app to display can you change the name of index.html to x.html

hi
can you post back and let me know whether you found this index.html file in the httpdocs folder?

hi
if you cant find index.html then this file could have a name called default.html

The nameserver only gets the request to your server.  Your server has to be set up to respond properly.  While we can make suggestion, OLM should know what needs to be done... since you're not their only customer with sites like this.

Just hear from OLM that they do not support DirectAdmin

Oh I see...
So they don't offer a control panel, and you set DirectAdmin up yourself?

In that case I should say that you were asking for trouble.

I suggest you reinstall the OS on the VPS via the VPS control panel, so you get a fresh new start. Update the OS and install a basic LAMP system; there are loads of tutorials on the net for this. Here are just two:
http://www.howtoforge.com/ubuntu_lamp_for_newbies
http://www.techiecorner.com/125/how-to-install-lamp-apache-php-and-mysql-in-linux-using-yum/

Make sure that PHP is running fine (by using a phpinfo file, for instance) and that MySQL is configured. Then maybe run a clean Drupal test installation.
If this goes well, remove the test installation and follow the guides for migrating a Drupal site.

Good luck.

No it is not that bad. They instlled Direct Admin allright and afaik a well running VPS, but when it comes to the configuration of that server there is no support from them. That is unfortunate since there was some pressure from their part to let me switch from shared hosting to a VPS. Some more help would've been nice as I am a total newbie as to the administration of a VPS.

But maybe I should repost my question:
I am trying to get a Drupal multisite running. The site is uploaded to a public_html directory. It is accessible at: http://69.94.32.233/~theorichel/

I have two domain names that are correctly pointed at my VPS, but all they produce is a message that "Apache is functioning normally" . How do I get these domains to point to the public_html directory (where Drupal picks up).
The domain names are present in Admin-level dns administration.
I was suggested to use pointers, but when I try to add one I get the message from DirectAdmin: 'You cannot use that domain as a pointer. It already exists on the server'.
Should I remove these domain names from the dns administration page and then try a pointer? Should I edit httpd.conf? Or what?

Solved it myself