I have another image of this VM, I just wanted to keep using it out of spite. We have two, Im replacing the primary right now, then Ill build a new slave to replace the other. These were built originally using prebuilt appliance VMs that wont update anymore. I ended up just deleting all the zones.
Then I added the zones manually as slaves and once they synced I copied each ones config file and deleted the slave zone (it errors when you try to convert a slave back to master) created the zone again as a master and pasted the config in. Just copying the configs directly had errors, that was part of the problem, doing the slave transfer must put it syntactically correct. Is there a way in mass to reset all the ttls to the system default, alot of these over the years had been changed for migrations to short times, etc, would prefer to not have to go in and manually change all that back. On Tue, Apr 21, 2015 at 9:12 AM, David <dmilho...@wletc.com> wrote: > Heres an example > $ scp -P 2264 foobar.txt > your_usern...@remotehost.edu:/some/remote/directory > > -P is for the port being used > > when using from CLI be sure your in the directory where foobar.txt is > > Foobar.txt being the good file to send over to damaged box > > > > On 04/20/2015 09:28 PM, That One Guy /sarcasm wrote: > > Ive totally hosed a bind configuration through webmin. I was dicking > around trying to migrate over to the new server copying config files for > the zones, now all i get are errors I dont care to troubleshoot. > > I just want to "factory default" bind and start over, Ill manually > create all the records, there arent alot and I didnt build the originals or > configure them anyway, so what little i do know about configuring one I > dont know if the last guy googled differently than me. > > Some day I will have to learn how to actually use Linux stuff > > but is there something along the lines of a factory default? > > -- > If you only see yourself as part of the team but you don't see your > team as part of yourself you have already failed as part of the team. > > > -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.
