Random Tech Thoughts: You Can’t Shut Down Your DNS Server And Then Keep Remoting Into Things On The Network

We have kind of a weird server setup at the office where we run a physical server and a virtual server, and the virtual server is kind of the brain of our network; which means that we have to shut down the brain to reboot the body when it comes time for maintenance tasks like Windows updates.

Listen to “You Can’t Shut Down Your DNS Server And Then Keep Remoting Into Things On The Network” on Spreaker.

The transcript below is not a good one, it was done using an app and has not been reviewed; it is there simply to provide some very basic SEO of this page.  Lame, I know, but it helps.

Speechnotes
So these podcast are not rehearsed they’re not clean or not edited these are my quick technical socks so I am outside walking my dog right now so what happened was this firewall that we have two windows servers on the physical server ones a virtual machine virtual machine which runs on hyper-v and it sits on top of the physical server you have a Windows Server 2008 R2 I think that’s what it is on both machines physical server with hyper-v installed running the virtual environment which is our DNS server it’s not a great system and not a great setup but it’s one that I inherited to keep it that way just as a matter of it not being a big enough priority to change because everything else going on small business blah blah blah all right that means when we do updates you have to windows updates at a specified time do it on the virtual machine first you shut that down then you install the update on the and then you and then you have to manually start back up well someone had tried to do that remotely just fine and were connected they install the updates on the machine and they were still connected rebooted the what that they got disconnected they couldn’t get back in the the iP address so I went over to the office physical servers on all I do is start the first varmint everything connected everything was fine to put your server in that kind of environment sure that it’s one just don’t don’t mess with the remotely site no big deal no work was hindered lost I’m going to be like that this was all after hours anyways just didn’t want to drive up to the office and then to the office quick start on the virtual machine you couldn’t do unless you when into a machine add stay connected because once that DNS server is turned off you lose the ability to get new IP address Lisa

Temi
These podcasts are not rehearsed, they’re not clean, they’re not edited. These are my quick technical saw, so I am outside walking my dog right now and we had an issue with the office earlier this week where people didn’t have Internet connection. So what had happened was this, we have a firewall, so dark the firewall and that, uh, protects all of our traffic coming in and out of that work, we have two windows servers once a physical server, once a virtual machine, the one that is the virtual machine, which runs on Hyper v a is our dns server and it sits on top of the physical server. So you have a windows server, 2008 or two operating system. I think that’s what it is on both machines. Uh, you got the physical server with Hyper v installed running the virtual environment, which is our dns server. It’s not a great system and not a great setup.

It’s one that I inherited and we have to keep it that way. Um, just as a matter of it not being a big enough priority to change because everything else going on small business, blah, blah, blah. All right, well that means when we do updates and you have to install your windows updates at a specified time, you do it on the virtual machine. First you shut that down, then you install the updates on they are on a physical machine and then you reboot that and then you have to manually stuck back up the virtual machine inside the Hyper v environment. Well, someone had tried to do that remotely and they vpn in just fine and we’re connected and they install the updates on the machine. Then they shut it down and they were still connected, but then they rebooted the other server with that. They got disconnected and then they couldn’t get back in.

They couldn’t get back in because the dns server was still shut down. So the physical server couldn’t go get a IP address, couldn’t get the local Ip. So I went over to the office. His Service on I’d do is start with the virtual environment. Everything connected, everything was fine. Um, I’m just still work to the wise you’re going to put your dns server and that kind of environment to make sure that it’s one that you can do the maintenance on remotely for or just don’t, don’t mess with it remotely. Do the updates on site, you know, that type of thing. No big deal, no work was hindered nobody. Um, last time, you know, nothing like that. This was all after hours anyways, this person doing the maintenance didn’t want to drive up to the office and then somebody ended up having to go up to the office to fix it before everyone else got there early in the morning up. It was just, it was a five minute fix just, you know, click start on the virtual machine and you’re good, but it’s something that you couldn’t do, um, unless you know, women into a machine that had already had our, unless you’d been able to stay connected, I should say it that way because once that dns or is turned off, you lose the ability to get new ip address. Lisa’s just doesn’t happen. All right, so that’s today’s thought.

Welcome to this summit.

Leave a Reply

%d bloggers like this: