nelasx's questions

I would like to get an advice how to fix the following situation.

My current infrastructure has 30+ linux boxes and 5 windows servers. I use bind dns master+2xslave with a non dynamic zone setup.

linux boxes are managed with an orcestration tool and login is done using ssh keys. Windows machines are in workgroup because we have only 5 of them and an AD was not needed.

Now the situation has changed and in a while there will be a massive addon for the windows servers, and im tinkering how to implement a Active directory for management and user authentication.

i came out with the following idea, but maybe someone can give me a better solution.

My current bind zone name is "example.local" and i need to keep it on the linux box.

I thought to install AD with an dns zone name "win.example.local" and configure the dns forwarder for "example.local" to my bind, and add a forward zone on the bind server to forward request for "win.example.local" to the windows box.

The other idea was to install AD as "example.local" manually add the records from existing bind to it and reconfigure the clients to use it as a new dns server.

thanks!

When the pods on GKE k8s are deployed they have the ability to connect to other GCE (google compute engine) instances by ip or google metadata DNS server name.

I use internal bind installed on 2 (master/slave) GCE instances for resolving. Let say example.local is the internal zone name, and all the instances are using it to do name-resolving. i do use custom dns, because i need to resolve on-premises dns records, and google cloud internal dns can't be managed.

GKE kubernetes pods are using the kube-dns and use /etc/resolv.conf resolver IP's which are using instance default google settings, and I can’t resolve my internal zone.

I really don’t know how to overcome this issue. Using Docker for example has the option to pass dns on container boot with “docker -d -p…… --dns=8.8.8.8…”.

can skydns be configured to have a zone forwarder defined for example.local ? just guessing.

I have a CentOS 7 machine with two disks mounted [ /dev/sda and /dev/sdb ] using ext4.

I need to extend /dev/sdb1 to over 2 TB.

I extended the disk from 2 TB to 2.5 TB (google cloud)

After using fdisk to delete and recreate the partition, after the reboot the resize2fs /dev/sdb1 does not resize the partition to 2.5 TB, since it looks like fdisk has reached the magical 2 TB limit.

Is there a way to extend /dev/sdb1 to lets say 3 TB without losing the data?

Thanks

update

as suggested by the fellow serverfault user @mzhaase I tried the gdisk with the following steps. The disk was formated with fdisk in total size of 2T

1. stop all services using the /dev/sdb1 partition

2. umount the device

3. Create a backup/snapshot

4. Extend the disk to 3T

5. install gdisk if not already installed on the instance

6. gdisk procedure
   gdisk /dev/sdb
   p #print and save the GUID
   o #delete all partitions
   n #create new partition
   c #label press ENTER or name if it had it
   x #enter expert mode
   g #paste the GUID
   w #write changes

7. umount /dev/sdb1 #if it gets remounted by gdisk

8. e2fsck -f /dev/sdb1 #check disk

9. resize2fs /dev/sdb1 #resize the partition

10. mount -a #check if the partitions mount as per fstab

11. reboot #just to be sure