DNS errors on Cpanel migrate: MX records not pointing correctly?

BTW, this has happened with several Cpanel migration/imports now. I didn't notice these errors at first, but I've been working on nameserver stuff (https://virtualmin.com/node/22463), so could that be causing me trouble?

The only thing I can think to add to this is that I'm setting up ns1/ns2 inside this system, but those nameservers currently resolve to the old server I'm moving away from. I planned to leave ns1/ns2 live on that server until I had all the Cpanel accounts imported, then I was going to switch their IP records at the registrar to point to this Virtualmin setup.

If the NS records doing currently point to these servers/systems (sorry, still struggling to know which terms to use), could that be my only problem here?

I couldn't think of another way to set up these systems in a way that I could then quickly flip the switch to move from one server to another (from Cpanel server to these Virtualmin servers).

Hope this info helps. Thank you.

Crap... BIND isn't running, it turns out. It wasn't obvious to me while rummaging through the config pages, but the darn thing isn't even started up! I'll try to sort this out first, so sorry for bothering you with this issue, since it appears to be something else going on.

I'll update this after I work on this for a bit longer. Sorry.

Also, I'll put in a feature request for Virtualmin while I'm at it:

It would be excellent to have a "server status" sort of notice right on the page where you're editing the options for a given server! For instance, for the BIND DNS Server, there is a "Module Config" and a "Start BIND" link up at the top, but they're very subtle (I didn't really even see them for a while.)

If there was a box up there with those links in it, which could also have a bright red & bold "DOWN" or a green "UP" status, so you could see right there what's going on, it would really rock.

As it is now, I have to navigate away from this page each time I want to try restarting the service in Virtualmin. Going back/forth between config and restarting is clunky.

Thanks!

Oy, so sorry... indeed this was my only problem. BIND wasn't running. (Ugh.)

I did figure out that there was a zone that was duplicated on both the master and the slave DNS servers, so I deleted the offending zone and BIND was able to start back up.

...clearly I still have a lot to learn about how to manage the whole Master/Slave relationship.

(sigh)

So sorry for the annoyance of these long messages. I'll close this now, if that's proper etiquette.

Cheers, Paul

Just to add another bit of info for future researchers on this set of keywords, errors:

I figured out about the offending DNS zone by running the BIND config checker...

Webmin > Servers > BIND DNS Server > Check BIND Config

Hope this helps someone down the road. :)

(This concludes this conversation with myself.)