Ubuntu 22.04 docker failure in name resolution after moving homes #networking #server #netplan #hostname

https://askubuntu.com/q/1484175/612

So, I want to give #Promo a try... anyone know the #hostname and #port to #login And before anyone asks, yes you can play #MUDs on a #Chromebook but the experience isn't the same as on Windows or a Mac

Massive #nerds everywhere: what are your favorite #hostname conventions for computers and #IOT devices around the home and office?

Of late I've been going with Hebridean islands for system names, Star Wars critters for IP cameras (because one of the first ones I installed reminded me vaguely of a Jawa), and characters from #MontyPython and the Holy Grail for other minor network-enabled microcontroller-based gizmos.

I definitely need to start a process of not committing to a #hostname until I've typed it a dozen times at different levels of tiredness, etc. Named a system 'igneous' and by damn it's a PITA to type more than 50% of the time for me. Stupid Rocky Linux.

When change the hostname the content of the file /etc/hosts must be updated manually? #networking #networkmanager #dns #hostname

https://askubuntu.com/q/1477503/612

How to change my user or computer name which appeares before each command in the terminal window? #hostname #username #devicename

https://askubuntu.com/q/1470880/612

Ubuntu clients can't resolve LAN hosts stored in local unbound server #networking #dns #netplan #lan #hostname

https://askubuntu.com/q/1469997/612

@vinc17

Try this on for size. It's what the command actually does, what's actually common with all other operating systems (even HP-UX), and what it deprecates is what the Tobias hostname(1) manual has been deprecating since around the turn of the century.

http://jdebp.info/Proposals/Debian-hostname.xml

Many guides even for Debian actually stick to the conventional use. This one has "linux.example.com" as the hostname from "hostname" and "hostname -s" shortening it.

https://hostingdata.co.uk/linux-hostname-command-tutorial-examples/

#DebianBugs #hostname

@vinc17

This is, ironically, why the old confusing hostname(1) manual has all of these backpedallings about not using "hostname -fqdn". It's a misfeature that no other implementation has, invented peculiarly for Debian and the peculiar Debian notion that we still live in 1981.

The Debian command was done badly in the middle-1990s, and the hostname(1) manual has been trying to un-dig the hole ever since, the hostname(7) manual having the real 40-year convention.

#DebianBugs #hostname

@vinc17

Since the 1980s, everyone else has been happy to have and document multi-label names as the norm.

RedHat's doco, for example, has almost equally long said to use a multiple-label name as the hostname. Just like the actual Unix operating systems all did before it.

RHEL 9 says "new-hostname.example.com" for example.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_networking/assembly_changing-a-hostname_configuring-and-managing-networking

#DebianBugs #hostname

@vinc17

On the contrary, multiple-label hostnames work with most softwares, even UUCP being able to have multiple-label names in bang paths, because it's been the convention since at least 1983.

Debian has had this wrong for a long time.

Debian's focus on putting a short hostname in and letting the HOSTS file expand it using name qualification and canonicalization mechanisms is straight out of the pre-DNS times.

#DebianBugs #hostname

@marlowe@universeodon.com @cks

Interesting factoid:

The HP-UX manual is about the only one to describe a convention of the UUCP node name (available via uname(1) and uname(2)) as a distinctly configurable thing separate from the Unix hostname. (It's almost universally the same thing under the covers in modern Unices and Linux distributions nowadays.)

The HP-UX hostname(1) has a table with the UUCP nodename as "sys" and the Unix hostname as "sys.x.y.z...".

#hostname

@marlowe@universeodon.com @cks

On the subject of UUCP and nostalgia:

I actually glanced at the rmail(1) manual page this month. Not because I was going to use it, mind.

I was trying to find the earliest that it became the norm to use a multiple-label name as a Unix hostname, something that happened pretty soon after the advent of the DNS.

The 4.2BSD manual has that convention described, with the infamous "monet.Berkeley.EDU". So too does the SCO Unix System 5 Release 3 manual.

#hostname

StackOver Flow Error: 2103 ERROR oslo.messaging._drivers.impl_rabbit Connection failed: failed to resolve broker hostname #openstack #hostname #rabbitmq #nova

https://askubuntu.com/q/1462906/612

I seem to have written a manual page. (-:

http://jdebp.info/Proposals/Debian-hostname.xml

#Debian #hostname

nslookup NXDOMAIN error in local network #networking #networkmanager #localhost #hostname

https://askubuntu.com/q/1462191/612

Unable to resolve hostname of Ubuntu 20.04 server after adding second ip address on a second adapter - no local DNS server #server #2004 #dhcp #ip #hostname

https://askubuntu.com/q/1459598/612

How can I pass the FQDN hostname to systemd? #systemd #amazonec2 #hostname

https://askubuntu.com/q/1459316/612

Who creates /etc/hostname #networking #2004 #dns #hostname

https://askubuntu.com/q/1457386/612

mdns hostname not fixed #hostname #avahi #mdns

https://askubuntu.com/q/1455388/612