On Thu, 2016-01-28 at 15:18 -0500, Bill Shirley wrote:
On 1/25/2016 10:35 PM, Tim wrote:
> Allegedly, on or about 25 January 2016, Greg Woods sent:
> > (I can't remember how to get a dump of the zone, but I remember doing
> > it in the past.
> Simply stopping the nameserver ought to cause it to reconcile its
> records on file. That's what I do when I've struck a DNS/DHCP foul-up.
> Stop DHCP server, Stop BIND, edit records, increment the serial number,
> restart BIND, restart DHCP server.
>
>
Try using:
rndc freeze
example.com
edit the zone
rndc thaw
example.com
If you are using DNS views:
rndc freeze
example.com in <view name>
edit the zone
rndc thaw
example.com in <view name>
Don't forget to increment the serial no.
You don't have to stop DNS or DHCP.
Bill
--
Thanks for the feedback
I've hacked together a script to do as you suggest whilst
I'm experimenting to try and find out how/why my server
became/becomes corrupted.
I now think it is to do with the way I cloned these particular
client machines.
I used a variation of
Create a valid F23 master machine/SSD and dump it whilst unmounted
...
dump 0f /mnt/zip/F22_dump_2015_06_22 /dev/sdb5
...
Restore to the disk/SSD of another machine
restore -rf /mnt/zip/F22_dump_2015_06_22
(This took less than 120s)
...
mount /dev/sda6 /mnt/zip
mount -o bind /dev /mnt/zip/dev
mount -o bind /proc /mnt/zip/proc
mount -o bind /sys /mnt/zip/sys
chroot /mnt/zip
gedit /etc/fstab
gedit /etc/hostname
Sort out grub2
I used to
gedit /etc/sysconfig/network-scripts/ifcfg-eno1
but recently I have been lazy and let
NM "sort it out" - for F23 I think it/I didn't get it quite right!
Adding an extra "mount -o bind /run /mnt/zip/run" to the list above
lets me use nmcli in the chroot environment but it is not quite
clear to me exactly what to do at that stage!
John