virtualbox.org

I'm learning so much from VirtualBox, trying things that I would never have tried before. Set up a DNS server for the first time, and am able to run machines on a virtual network to access it. Very exciting.

Host: openSUSE 12.2 (x86_68)
VirtualBox 4.2.10 r84101
Guest: CentOS 6.4 (no X, with Guest Additions installed for shared folders)
BIND 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.4

I'm using a basic CentOS installation without customizations that I clone to build new machines. The only customization is the Guest Additions for shared folders. BIND was installed with YUM.

When I first start the DNS server, it works.

• A VM on the virtual network can use dig or nslookup to get a result, a VM browser can surf the internet.
• ps aux lists the STAT of named as Ssl
• if I watch top while sending a query to named, it lists the STAT of named as S (that's as far as I am able to see it)

After sitting idle for some time (an hour?) the DNS fails to work.

• dig or nslookup just time out.

  nslookup xxx
  ;; connection timed out; trying next origin
  ;; connection timed out; no servers could be reached

• service named status returns:

  version: 9.8.2rc1-RedHad-9.8.2-0.17.rc1.el6_4.4
  CPUs found: 4
  worker threads: 4
  number of zones: 21
  debug level: 0
  xfers running: 0
  xfers deferred: 0
  soa queries in progress: 0
  query logging is OFF
  recursive clients: 1/0/1000
  tcp clients: 0/100
  server is up and running
  named (pid 2425) is running...

  Then only difference with when it is running is that the recursive clients was 0/0/1000 when running.
• If I log in to the DNS server and restart named (service named restart), then a dig or nslookup from a client works again.

My guess is that a stock installation of CentOS with BIND as a 'real' machine would create a DNS server that doesn't stall after an hour. That's a guess. So my next guess is that there is something that needs to be tweaked in VirtualBox.

• Is this a VirtualBox issue?
• Is this a named configuration issue?
• Both?

Any help is much appreciated as my search attempts have only produced random noise.

The first pieces of information we would need are the VM log file and the VM infos, both describe here.
Make sure you post it as a zipped attachment.

Info and Logs attached.

Few things here :
1. you use the 4.2.10 build which had broken guest additions. Try reinstalling the newer build (simply download again) or the new 4.2.12 version.
2. You have a NAT interface - I would suggest something more adequate for your task : bridging
3. You use two types of interface : the old AMD for your first and an Intel for your second. I would suggest sticking with only one, the Intel in this case.

Try changing these settings and see if there is any improvement.