On Sun, Apr 18, 2021 at 09:21:55AM -0400, Gene Heskett wrote: > On Saturday 17 April 2021 23:31:20 Gene Heskett wrote: > > It boiled down to something, someplace, not liking a hostname starting > with a number, I recalled I had to rename another machine a couple > months ago because it didn't work either. > > But I changed its hostname to dddprint, based on the previous 3dprint, > and it now works as requested. So my problem is solved. > > Is that just a head scratcher, or is there a valid reason to not allow a > hostname such as 6040 or 3dprint? Something starting with a numeral IOW.
Well, it's in rfc1035 [1]:
"The labels must follow the rules for ARPANET host names. They must
start with a letter, end with a letter or digit, and have as interior
characters only letters, digits, and hyphen. There are also some
restrictions on the length. Labels must be 63 characters or less."
("label" is the rfc's parlance for a FQDN component, i.e. "what goes
between the dots [2]).
I guess what happens is that whatever program is trying to resolve
the host name relies on that and assumes an IP address was given
whenever the thing starts with a digit. Fair enough, I'd say.
> Is that a bug? Or is there a specific reason for the silent failure?
I don't think so.
Cheers
[1] https://tools.ietf.org/html/rfc1035
[2] Yes, I'm imagining dots at the beginning and the end of the
FQDN, you nitpickers ;-)
- t
signature.asc
Description: Digital signature
