I take that to mean that a system needs to cope with _other_ hosts having numeric hostnames when communicating with them over the Internet. It doesn't mandate that a given host must be able to be configured by its user to have a numeric Unix hostname. It's perfectly reasonable for a system architecture to have additional restrictions on its own hostname over what the Internet permits.
You have, at best, a wishlist item that Ubuntu (or other POSIX-like or Unix-like distributions if you wish) support all-numeric hostnames. Although you might want this for rabbitmq-server, it is really a general wishlist item, not one that is specific to rabbitmq-server. I don't believe that this is something that will ever be supported by any Linux distribution because it goes quite deep into how underlying APIs operate - for example to tell the difference between a host specified by IP and a host specified by name. If you want to take this further, re-opening the bug won't help. This is an architecture level wishlist item that would impact many packages. The appropriate bug status is somewhere between Invalid and Won't Fix because it isn't something that I believe the Ubuntu project (or even the wider ecosystem) considers to be a problem that is worth addressing. ** Changed in: rabbitmq-server (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529033 Title: Install/start fails when hostname is numeric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1529033/+subscriptions -- ubuntu-bugs mailing list email@example.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs