Fedora install weirdness
-
Does reverse DNS lookup on the IP 192.168.1.100 result in that PC name?
-
@JaredBusch said in Fedora install weirdness:
Does reverse DNS lookup on the IP 192.168.1.100 result in that PC name?
Yes it does, which I suspected was the case. Is it normal for Linux distros to pull a host name from reverse DNS? If the answer is, yes - ok fine. that answers that question.
But that doesn't answer the storage name question - which is really the much more bizarre one.
-
@Dashrender said in Fedora install weirdness:
@JaredBusch said in Fedora install weirdness:
Does reverse DNS lookup on the IP 192.168.1.100 result in that PC name?
Yes it does, which I suspected was the case. Is it normal for Linux distros to pull a host name from reverse DNS? If the answer is, yes - ok fine. that answers that question.
But that doesn't answer the storage name question - which is really the much more bizarre one.
That never happens in my networks so I have no idea. I don't let things do that.
-
@JaredBusch said in Fedora install weirdness:
@Dashrender said in Fedora install weirdness:
@JaredBusch said in Fedora install weirdness:
Does reverse DNS lookup on the IP 192.168.1.100 result in that PC name?
Yes it does, which I suspected was the case. Is it normal for Linux distros to pull a host name from reverse DNS? If the answer is, yes - ok fine. that answers that question.
But that doesn't answer the storage name question - which is really the much more bizarre one.
That never happens in my networks so I have no idea. I don't let things do that.
eh - what? let things do what? I didn't 'let' Fedora pull from reverse DNS - it did it completely on it's own.
If you're saying that you never don't put in a host name during install - I guess congrats are in order?
As for reverse DNS still having an entry - it hadn't been scavenged yet, that's set for 30 days, and the fact that it pulled this name in didn't hurt anything, it was simply odd.
-
@Dashrender said in Fedora install weirdness:
As for reverse DNS still having an entry - it hadn't been scavenged yet, that's set for 30 days, and the fact that it pulled this name in didn't hurt anything, it was simply odd.
IMO, if using DHCP with DNS settings, not setting an IP or host name during install, I would expect the results you received.
I always set the host name and IP so I have not never run into this issue personally.
-
@Dashrender said in Fedora install weirdness:
@JaredBusch said in Fedora install weirdness:
Does reverse DNS lookup on the IP 192.168.1.100 result in that PC name?
Yes it does, which I suspected was the case. Is it normal for Linux distros to pull a host name from reverse DNS? If the answer is, yes - ok fine. that answers that question.
But that doesn't answer the storage name question - which is really the much more bizarre one.
If you leave the hostname blank during install, it has two choices. Make up something totally random (Microsoft's way) or to look up what you've set the network to tell it its name is.
In reality, what you are seeing here isn't weird in the least. It's the logical, polished way to handle it. It asks your network what its name is, it is told, it sets it automatically. Way more solid and predictable than Microsoft's "make some gibberish" method. That's what is weird. This is not weird.
-
@Dashrender said in Fedora install weirdness:
As for reverse DNS still having an entry - it hadn't been scavenged yet, that's set for 30 days, and the fact that it pulled this name in didn't hurt anything, it was simply odd.
How do you define that as odd? Isn't this the least odd possible thing?
-
@pmoncho said in Fedora install weirdness:
@Dashrender said in Fedora install weirdness:
As for reverse DNS still having an entry - it hadn't been scavenged yet, that's set for 30 days, and the fact that it pulled this name in didn't hurt anything, it was simply odd.
IMO, if using DHCP with DNS settings, not setting an IP or host name during install, I would expect the results you received.
I always set the host name and IP so I have not never run into this issue personally.
Same here. But if you have an infrastructure team doing one part and a build team doing another, using the DNS settings to push names via DHCP reservations or whatever is a part of build automation. So about the most clear and obvious and useful possible setup.
It only seems weird to people used to Windows where even with AD there isn't quite this much polish and automation. It's the expectation of "Windows like, less polished behaviour" that makes this seem odd.
-
@Dashrender said in Fedora install weirdness:
The blurred out text is the name of one of the computers on my AD domain - of which this new Fedora box knows (or at least should know) nothing about.
I bet you'll find it's in a DNS record somewhere, too.
-
@pmoncho said in Fedora install weirdness:
I always set the host name and IP so I have not never run into this issue personally.
Setting the hostname, of course. but setting the IP? Never. DHCP reservation, unless a hypervisor, router, or DHCP/AD/type server.
-
@Dashrender said in Fedora install weirdness:
I did NOT set a hostname
I know that Windows doesn't let you specify during initial install anymore. Such a stupid thing.
-
@JaredBusch said in Fedora install weirdness:
@pmoncho said in Fedora install weirdness:
I always set the host name and IP so I have not never run into this issue personally.
Setting the hostname, of course. but setting the IP? Never. DHCP reservation, unless a hypervisor, router, or DHCP/AD/type server.
DHCP Reservations would be a form of setting the IP.
-
@JaredBusch said in Fedora install weirdness:
@Dashrender said in Fedora install weirdness:
I did NOT set a hostname
I know that Windows doesn't let you specify during initial install anymore. Such a stupid thing.
Causes so many unnecessary steps and/or headaches for us. It's ridiculous. Such a trivial thing, made so hard.
-
@JaredBusch said in Fedora install weirdness:
@pmoncho said in Fedora install weirdness:
I always set the host name and IP so I have not never run into this issue personally.
Setting the hostname, of course. but setting the IP? Never. DHCP reservation, unless a hypervisor, router, or DHCP/AD/type server.
In regards to the amount of work, isn't Static IP basically the same as a DHCP reservation?
-
@scottalanmiller said in Fedora install weirdness:
@Dashrender said in Fedora install weirdness:
As for reverse DNS still having an entry - it hadn't been scavenged yet, that's set for 30 days, and the fact that it pulled this name in didn't hurt anything, it was simply odd.
How do you define that as odd? Isn't this the least odd possible thing?
I see your point - but what are the chances that you're going to have reverse DNS setup before setting up the server? I know I've NEVER done it on purpose. The only worked because DHCP gave an IP to my server that happened to coincide with an existing reverse DNS entry, which only existed because it hadn't been scavenged yet, so the situation seems odd to me.
If a hostname is critical, then I expect the machine to demand I provide one - it does irk me that MS doesn't prompt for a computername during install. Of course, no one said it was critical.
-
@scottalanmiller said in Fedora install weirdness:
@JaredBusch said in Fedora install weirdness:
@Dashrender said in Fedora install weirdness:
I did NOT set a hostname
I know that Windows doesn't let you specify during initial install anymore. Such a stupid thing.
Causes so many unnecessary steps and/or headaches for us. It's ridiculous. Such a trivial thing, made so hard.
@scottalanmiller said in Fedora install weirdness:
@JaredBusch said in Fedora install weirdness:
@Dashrender said in Fedora install weirdness:
I did NOT set a hostname
I know that Windows doesn't let you specify during initial install anymore. Such a stupid thing.
Causes so many unnecessary steps and/or headaches for us. It's ridiculous. Such a trivial thing, made so hard.
No doubt.
I like the old SCO UNIX 5.6 and prior install routine. Answer all needed questions with 4 screens and let it install. No muss, no fuss and all is set after it reboots. It was nice.
-
@pmoncho said in Fedora install weirdness:
@JaredBusch said in Fedora install weirdness:
@pmoncho said in Fedora install weirdness:
I always set the host name and IP so I have not never run into this issue personally.
Setting the hostname, of course. but setting the IP? Never. DHCP reservation, unless a hypervisor, router, or DHCP/AD/type server.
In regards to the amount of work, isn't Static IP basically the same as a DHCP reservation?
Up front, yes. Long term, generally no.
-
@scottalanmiller said in Fedora install weirdness:
@Dashrender said in Fedora install weirdness:
The blurred out text is the name of one of the computers on my AD domain - of which this new Fedora box knows (or at least should know) nothing about.
I bet you'll find it's in a DNS record somewhere, too.
Of course - the new IP it has on the new subnet it's part of.
-
@Dashrender said in Fedora install weirdness:
@scottalanmiller said in Fedora install weirdness:
@Dashrender said in Fedora install weirdness:
As for reverse DNS still having an entry - it hadn't been scavenged yet, that's set for 30 days, and the fact that it pulled this name in didn't hurt anything, it was simply odd.
How do you define that as odd? Isn't this the least odd possible thing?
I see your point - but what are the chances that you're going to have reverse DNS setup before setting up the server?
In a business where they are planning their deployments and managing IT: extremely high.
It's just the logical way to do it. Having haphazard records doesn't make logical sense. That's just sloppy. Basic infrastructure planning - using the tools you have as they are designed.
-
@Dashrender said in Fedora install weirdness:
I know I've NEVER done it on purpose. The only worked because DHCP gave an IP to my server that happened to coincide with an existing reverse DNS entry, which only existed because it hadn't been scavenged yet, so the situation seems odd to me.
Basically you have two issues. One, you aren't managing your system and just letting it exist. And two, you have the system not in place intentionally but using it as just part of an infrastructure that you didn't tie this system too. Had you put this system under AD to match the infrastructure you had chosen, it would have done exactly what it was supposed to do.
You are falling into a weird space of running infrastructure haphazardly, and trying to run two different systems that share some infrastructure and not others, and seeing the management of the one messing with the other because you are keeping them blind to each other.
