FOG Server IP Keeps Changing in DNS!
-
@Shuey said in FOG Server IP Keeps Changing in DNS!:
@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).
The delete all DNS records for the fog server, and let it be found the natural way.
With time.
-
@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...?
-
@Shuey said in FOG Server IP Keeps Changing in DNS!:
@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...?
DNS isn't dependent on AD.
-
@Shuey Do you have Dynamic updates set to Secure only or Nonsecure and secure?
-
@black3dynamite "Nonsecure and secure"
-
Okay, so to recap... there is NO issue on the FOG system and the entire thread is actually about a problem with Windows DNS getting bad updates. The AD DC is running DNS, and DNS keeps showing an A record for the FOG server that is the old DHCP assigned address for that rather than the current statically assigned one?
-
@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:
- The Ubuntu server picked up a DHCP address when the server was first setup (prior to FOG getting installed and configured).
- That address then appeared in DNS as I would expect, but of course was the wrong IP (since it was not statically assigned yet).
- 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).
- 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....
-
@Shuey said in FOG Server IP Keeps Changing in DNS!:
@black3dynamite "Nonsecure and secure"
Have you already try setting it to secure only and then delete dns record?
-
Your Ubuntu Server DNS setting is probably configured with your DNS Server IP.
-
@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...
-
@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...
-
@Shuey said in FOG Server IP Keeps Changing in DNS!:
@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...
The issue is clearly your DNS server then
-
@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
-
@Shuey said in FOG Server IP Keeps Changing in DNS!:
@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
You said you weren't able to access the server, didn't you?
-
@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 :-/...
-
@Shuey said in FOG Server IP Keeps Changing in DNS!:
@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 :-/...
Could be, I'm not really paying attention to ML atm.
-
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 ??
-
@Shuey said in FOG Server IP Keeps Changing in DNS!:
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 ??
DNS is shown in the file /etc/resolv.conf
-
If you do an nslookup command, it will show you which DNS server it queried at that time, as well.
-
@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)
