Virtualmin GPL on Rackspace CloudServer - can I use BIND?

Virtualmin
1

Hi there! I’ve recently discovered Virtualmin GPL, and it looks like a great tool to aid in getting a Rackspace CloudServer up and running. However, I seem to be getting jammed up on one thing. I see that Virtualmin GPL is setting up a slew of DNS records in bind when I create a new virtual server, but no matter what I do I cannot seem to get the registrar (in my case domaindiscover.com) to recognize the CloudServer (host-01.octobang.com) as a nameserver. I get the following when I run dig from another CloudServer, which looks to my (DNS-related) inexperienced eye to be a valid nameserver response (the IP address returned for the server is correct):

# dig arpieb.com @host-01.octobang.com

; <<>> DiG 9.7.1-P2 <<>> arpieb.com @host-01.octobang.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21538
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;arpieb.com. IN A

;; ANSWER SECTION:
arpieb.com. 38400 IN A 184.106.96.85

;; AUTHORITY SECTION:
arpieb.com. 38400 IN NS host-01.octobang.com.

;; Query time: 0 msec
;; SERVER: 184.106.96.85#53(184.106.96.85)
;; WHEN: Mon May 9 04:59:22 2011
;; MSG SIZE rcvd: 75

Rackspace of course just says to use their nameservers, but I’d like to leverage the automagic DNS record creation within Virtualmin.

Has anyone tried this, or know if it can even be done? I’m running a CentOS 5.6 image over there, bare-bones before I installed Virtualmin - and still nothing new has been added other than creating the new virtual server.

Thanks in advance for any assistance!

2

Howdy,

It sounds like you need to register your server’s IP address as a nameserver with your registrar. There’s some details on doing that here in the section “How do I setup nameservers for my server?”:

http://www.virtualmin.com/documentation/dns/faq

3

@andreychek, thanks for the link. I hadn’t run across that FAQ page yet in my searches, and was getting no love from Google or my registrar searching for the solution either.

Registered the server with the registrar, THEN designated it as the nameserver for the domain. Guess that was a step I’ve never had to deal with before. It looks like the TTLs are so high for the old nameservers that I’ll have to wait about 8-12 hours to see if the changes took.

Thanks again!

4

Great, glad you got that working!

Let us know how that all goes after you wait out the TTL’s.

Have a good one!

-Eric