Virtualmin & Mandriva 2006?


Does Virtualmin support Mandriva 2006 yet? I have version 2.609 installed in my attempts to resolve my nameservers that are not resolving.

When I ran dig, this is what I got back:

;[<>> DiG 9.3.1[<>> @
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6389
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

; IN A

;; AUTHORITY SECTION: 38400 IN SOA hostmaster.marine 1134503735 10800 3600 604800 38400

;; Query time: 13 msec
;; WHEN: Fri Dec 16 11:45:41 2005
;; MSG SIZE rcvd: 99

I don’t see ns1 & ns2 (as like in Chap 8: Bind example by Joe). My site is not resolving and it’s been over 4 days.


Hey Greg,

Mandriva is in development. Platform support seems to always eat far more time than anticipated…but it’s getting a little bit faster with each new OS. Mandriva is probably another week or two away.

In the meantime, if DNS trouble is all you’ve got to complain about in Virtualmin GPL, let’s address those issues and get you running nicely with what you’ve got.

Check your glue records first. i.e. be sure your registrar agrees with you about what your nameservers are. is an excellent and easy to use tool to tell you lots of stuff about your domain.

When I run it for your domain, it complains quite a bit about one of your nameservers:

WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed). returns 0 answers (may be a referral)

ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:

ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:

ERROR: I checked with your nameservers to see if there were any CNAMEs for (there shouldn’t be), but they all timed out.

ERROR: I couldn’t find any A records for… If you want a website at, you will need an A record for… If you do not want a website at, you can ignore this error.

These problems would definitely cause nothing good to happen with your domain, and need to be addressed. We can probably help, but it’s hard to tell exactly where things are falling down. Though the most glaring issue is that there is nothing at that is actually answering DNS queries. If you’ve got no working DNS server, you won’t get DNS service! So, that’s probably the first problem to solve…check to be sure named is running, is not blocked by a firewall, and has no errors in /var/log/messages.