[SOLVED] Moving a DNS Subnet

I am trying to move a DNS subnet, using webmin on Mandriva Linux 2010.1 (I know it's old). More information here: https://forums.techguy.org/threads/m...ubnet.1187054/. Please help.

Originally Posted by des_a I am trying to move a DNS subnet, using webmin on Mandriva Linux 2010.1 (I know it's old). More information here: https://forums.techguy.org/threads/m...ubnet.1187054/. Please help.

I have done something like this, but from the command line not using webmin.

The way I have done something like this using webmin was to add the new domain, manually add the host names and addresses, gradually migrate usage to the new domain, then retire the old one. I know of no automated way to do the migration, though someone else may.

If it's not too late to do it that way then, how do you do it from the command line? Right now, when I tried to do it the best I knew how via webmin, now nothing resolves, not even on the server itself, and it can't find it in DNS if I look it up without ping either, not even on the server itself.

As long as the changes will show up in webmin, I don't care if I do it from the command line or not...

Originally Posted by des_a If it's not too late to do it that way then, how do you do it from the command line? Right now, when I tried to do it the best I knew how via webmin, now nothing resolves, not even on the server itself, and it can't find it in DNS if I look it up without ping either, not even on the server itself. As long as the changes will show up in webmin, I don't care if I do it from the command line or not...

You could Google for that and find several dozen examples, I believe, but first we need to get it back into working order using the OLD domain.
I suppose it is too much to expect that you took a couple of backups before you started? If not, please remember that for next time. If yo did, can you restore form the most recent backup?

If yo have no backups: What exactly did you do in webmin? Not just what you think broke things, but what you really did. We need to figure out what consequences may have obtained on the file system to determine what we need to get back.

I believe what I did was leave everything the same, and manually change all the IP addresses to the new subnet in my zone. Then saved and reloaded. I believe it loaded with errors and I tried to fix them then. I don't remember what those errors were.

If I can't figure out for sure what I did, I may have to start from scratch. No backups were made. I wasn't that smart about it. The network is working, but names do not resolve.

I never thought to try from the command line, but why not? I should've assumed that it could be done. I believe I did try to Google the general idea of what I wanted to do, and turned up with no useful results.

I would make a backup before redoing everything, if that's what I had to do. My whole IP structure is pretty disorganized by this point, but since it functions okay, I was going to leave it the way it was until I got other things working.

This is what I came up with when I Googled: https://www.google.com/search?q=move...&bih=652#spf=1

OK, with no backups, no urgency, and no record of the steps you took, it may be best to just start clean.

1. how many nodes have you in your current network?
2. have you used DHCP in your local network?
3. are you at all familiar with dnsmasq? (It can replace bind for a SMALL network, does caching DNS for efficiency, and can optionally act as a DHCP server.)

One option you have is to clear the bind tables and start over using bind and webmin. This could be the best option.
Another is to move to dnsmasq. It does not require elaborate tables:loads initial tables from your local hosts file, automatically loads DHCP client records into the DNS tables in memory, is smaller and very efficient, and can be configured by editing the conf file. There was a WebMin module for it, but it was orphaned the last I knew and I am not sure if there is a current one.

There IS a WEB GUI for dnsmasq. Although I have not used it, some swear by it.

OK. Thanks anyway. I'll start clean. I'll use webmin and my printer to save the values I began with, and then delete them in the easiest way. I'll generate my new DNS server the same way I did before. I think that just regenerating it will automatically wipe what I don't need.

I first use drakwizard, and then I use webmin to finish the job. I'll just make sure I save it first. My configuration can be found using my router's DHCP entries. Yes, I use DHCP. The bummer is going to be all the CNAMES. But that is why it will be important to print it first. Thanks. Since there's nothing more you can do, marking as solved.

Well, starting from scratch was exactly what I did. I saved it, (See: http://www.linuxquestions.org/questi...43#post5695843). Now my problem is that everything will resolve from the server whether I do it locally or not. However, it won't resolve from the clients. The problem is that mainrouter (one of the CNAMES that won't resolve!), is not getting the update proper from the server to serve it to the rest of the clients. It's not getting CNAMES is all. Maybe the equivelant of a /flushdns command or something? I have ran /flushdns from my clients with still no success.

I suggest that you "dive beneath the covers" of this webby-thingy and see what it actually did. Find the DNS daemon and find its configuration file, probably in /etc.

Look for any technical description on the web about "how the damned thing works."

Then, fix it.

So I modified the db file directly, and still have the same problem. Now, when I ping from the server, it will ping fine. When I ping from the client running Windows, it will not find the name. It seems to find all the names, except for some of the CNAMES do not return the domain name portion of the server name and only the hostname portion. I have already tried to google it, and I haven't found what I'm looking for, but sometimes I'm not as good as googling things like this as I would like to be. I'll try two more things, and check in, but just in case they don't work, I'm updating you here. I'll try rebooting the server, to see if that helps, and then I could flush the DNS cache on the Windows client. I have tried multiple times rebooting the router, and although at some point part of it "fixed itself" over time, the whole thing has not. So I'll try to do those two things and see if that helps.

Still no dice.