Can't resolve server's hostname (CentOS 5.5 in VBox)

[Boris-B]

I'm working on a project for school and I'm setting up a server. I wanted to try it first so I ran it in a VM. everything works fine except that I can't resolve my server's hostname. This is from my laptop and desktop. They are both running Arch Linux and can resolve each other's hostnames.

I don't understand why. I tried to look on google and I didn't get much.

The problem might be caused because I didn't install any extra packages (including the base one)

I'm pretty sure that it's simply set not to respond to it's hostname. I don't know how to change it.

[editline]19th November 2010[/editline]

I have a router that runs dd-wrt and it seems to be a DNS server. All computers point to it as a nameserver in resolv.conf. I wonder if it's the router being way too stupid to register my server or if it's the server itself.

I just ran an nmap on it and it has the domain port open.

[boris@boris-linuxPC ~]$ sudo nmap -sS 192.168.0.1
Password: 

Starting Nmap 5.21 ( http://nmap.org ) at 2010-11-19 21:51 EST
Nmap scan report for DD-WRT (192.168.0.1)
Host is up (0.024s latency).
Not shown: 997 closed ports
PORT   STATE SERVICE
23/tcp open  telnet
53/tcp open  domain
80/tcp open  http
MAC Address: 00:1A:70:FC:63:0E (Cisco-Linksys)

Nmap done: 1 IP address (1 host up) scanned in 0.66 seconds

[editline]19th November 2010[/editline]

On my router's page it gives me my laptop's domain but not the server's

#server
*	192.168.0.127	xx:xx:xx:xx:D7:CD	1 day 00:00:00
#laptop
boris-laptop	192.168.0.131	xx:xx:xx:xx:0D:D3	1 day 00:00:00

[Nipa]

Has the VM been set up to use a bridged connection?

[Boris-B]

Yes. It's bridged.

Also, I'm able to connect to the server through ip but the hostname won't be resolved.

[q3k]

I think your router's DNS daemon might just not be letting resolve by local machine hostnames.

[Boris-B]

The problem is that it is. I'm still able to access both my PCs through their hostnames.