Posts made by Shuey

@scottalanmiller Cool, at least it's one extra thing that was caught and fixed : )

@scottalanmiller I cat'd my /etc/resolv.conf file and there's nothing in it (except for the default two comment lines).

I went ahead and added a DNS server and search (nothing was configured previously and I was unable to ping anything by name) and nslookups are working now.

I've gone so far down this rabbit hole since yesterday that I'm asking myself out of confusion now: "What again does all this have to do with the fact that our AD DNS was changing?" (especially since I didn't even have DNS configured on the Ubuntu server before this morning)

OK, so I gained access to the CLI again. There doesn't appear to be any DNS servers configured for my Ubuntu server to talk to (even though it can get out to the Internet for updates without any problem, because it at least has a gateway configured).

This seems to rule out black3dynamite's theory that my Ubuntu server DNS is configured with my DNS server IP...

Where else should I check for these settings, besides in /etc/network/interfaces ??

@DustinB3403 No... I think you should slow down and read what I say before you reply, lol. I said "I can still login to the web console no problem"... I'm NOT able to login to the CLI (because my password is failing, not because I can't GET to the CLI :-/...

@DustinB3403 Now I'm crazy confused... what does me not being able to login to the CLI have to do with my AD DNS? O_o

@black3dynamite I'm trying to check the DNS settings right now, but oddly enough, I can't login anymore... (I just rebooted the server and after it came back up, I'm not able to login to the CLI). I can still login to the web console no problem, but the CLI creds are not working O_o...

@black3dynamite Nope :-/... DNS in our environment has always been configured for "nonsecure and secure" and I've never changed it because I'm not familiar with how to properly set it to "secure only", nor am I familiar with what kind of repercussions there would be :-S...

@scottalanmiller Pretty much, yep. I say "pretty much" because I'll also re-clarify that the entry in DNS is accurate for a couple of days, and then it suddenly changes to the FOG server's old DHCP address.

Here's a recap of the server's DNS record:

1. The Ubuntu server picked up a DHCP address when the server was first setup (prior to FOG getting installed and configured).
2. That address then appeared in DNS as I would expect, but of course was the wrong IP (since it was not statically assigned yet).
3. I configured the Ubuntu server with a static IP, then I updated the DNS record, making it static instead of DHCP assigned (as well as the PTR), then installed and configured FOG (using the same static IP of course).
4. I thought everything was fine, but a couple days later I noticed that I couldn't ping the FOG server. I checked DNS and noticed that the static entry I had configured had changed to the original DHCP address that the Ubuntu server had picked up....

@black3dynamite "Nonsecure and secure"

@DustinB3403 If a non-domain server is configured with a static IP, the host record won't get automatically created in AD DNS... How is it supposed to be "found the natural way - with time" when it'll never be discovered automatically :-S...?

@DustinB3403 The FOG SERVER is not defaulting back to the DHCP address, our AD DNS is where the IP keeps reverting back (and this is all BEFORE ever creating a dedicated reservation that matches the correct IP).

@DustinB3403 I thought I clearly stated in my original post that it's not getting a DHCP address; it's been configured with a static IP ever since I installed FOG. And yes, the interface is named "ens160" (confirmed with ifconfig).

@DustinB3403 Yep, prior to configuring FOG:
auto ens160
iface ens160 inet static
address <hidden>
netmask <hidden>
gateway <hidden>

I went ahead and created a DHCP reservation for the server (even though the server is configured for a static IP), and as soon as that was successfully created, the A record vanished in DNS (not what I was expecting to see happen). I went ahead and manually created the A record again, and I left the DHCP reservation in place, but obviously the reservation will not be of much use unless I change the server to use a DHCP assigned IP instead of a static one (something I'd really rather not do)...

@coliver Nope - only one NIC (and this server is a guest VM).

@black3dynamite Ubuntu 16.04.1 LTS (64-bit)

When I deployed our FOG server, I chose an IP in advance and configured the server to use that static IP as I was deploying it. I created a static host entry in our AD DNS, and everything seemed fine... Until I noticed that the host record and IP reverted back to the original DHCP IP (FOG will always pick up a DHCP IP prior to setting a static IP and finishing the deployment).

I've verified in the FOG web console that the IP is still correct (the static IP I assigned), and I also double-checked the .fogsettings file to make sure that the IP is correct there as well. One last ditch effort I did was I deleted the A and PTR records in DNS and verified that the deletion successfully replicated across all internal DNS servers, then I created a fresh A record (which automatically created a fresh PTR record). I let the addition replicate and waited a couple days to see if that fixed the issue; it did not! A couple days after doing this, the IP has reverted back to the original DHCP address, and it's not pingable. If I ping the server by the correct IP, it works (but the DNS name is obviously wrong)

Why is this happening, and what can I do to fix it!?

@Carnival-Boy Cool, I'll look into that.

If I was going to try a P2V of this server, what would be the best way to go about it?

1. I could consider a cold clone (the only disc I have available to try this is the VMware cold clone 3.0.3 disc; not sure if that will work or not)
2. Another option I was considering is installing VMware Standalone Converter, then booting into DSRM mode and performing the P2V. Once the server was successfully converted, I'd shutdown the existing server, fire up the virtual, and make sure the IP was the same.

Thoughts on these options, or other possibilities?

@NetworkNerd I feel your pain, believe me. A couple of examples of how misguided they are (and stubborn - I add that because I've expressed the dangers of various decisions they've made, and my input has fallen on deaf ears multiple times....):

1. There are two main data centers. One of the main data centers is stored in a "janitor's closet/storage room" and there's no lock on the door O_o... The building that this data center is located in has no alarm system! The other main data center is cooled by a wall-mounted AC unit. And prior to the AC unit, the room was only cooled by a standard AC vent from the main AC unit that runs throughout the entire building. This data center used to overheat all the time, and the fix that the previous IT Director had for this issue was to continually (pretty much 3-4 days per week) "open the main doors and setup some floor fans to blow the air out of the room" O_o...
2. Another example: When I first started working at this place, they didn't have ANY spare PCs built and ready to go in case of an emergency. It was like pulling teeth to convince the previous IT Director to allow me to build at least one spare for each site, but I finally talked him into it.

@NetworkNerd Great info to put things in perspective, thank you. A couple things to note here too:

1. I'm not the manager of the IT department, so I don't have the ability to talk to upper management about this stuff. I just do my best to convey the info and impact to my "IT Director" and let him know the dangers (in writing), and then try to let go of it so I don't stress myself out.
2. Upper management is SO cheap that there have been multiple times where I've shown them "deals" that we could purchase from various vendors, but management says that I HAVE to get them quotes from Amazon (because they "get points for shopping on there, and then use the points for 'free purchases'"). It's hard to work with bean counters who don't even know how to logically count beans... :-S

@NetworkNerd Yep, the servers are also out of support. The hosts are located in separate data centers (different physical sites across town, in a network that's all connected by fiber).