Samuel Sieb: >> That shouldn't work. A name without a domain isn't valid. You >> need to set things up so there's a domain (and don't use >> local!). You can have a default domain, so that bare names will >> automatically be tried with the default domain.
Javier Perez: > Sorry. It works. I do not have a domain name because this is my > personal, home network. Never got a domain name to it, in fact my > connection to the internet is not a static IP, it is whatever the > box my ISP gave me assigns to my router. Is there any suitable name > one can use as "domain" for local networks that do not clash with > already defined names (like there is for IPs, 192.168.x.x is > supposed not to be a public IP). Once I looked it up and did not > arrive to a satisfactory answer, got a lot of contradictory info > from google. It *may* work, it *may* give you problems. I don't know. DNS servers can be used beyond what people are used to seeing with them, but on the other hand you could have a configuration battle in the future. The one word "localhost" is handled by BIND quite fine. My prior response pointed out that ".internal" is a domain name set aside for such use. There are a bunch of reserved names for non- internet use (registrars can't sell/give them to someone), though you mayn't want to use some of them: .example (intended for similar reasons that example.com exists, but that doesn't stop you using it inside a LAN - and any postings you made about your networking problems would be both textbook examples, and working examples for you) .internal (intended for internal use within some organisation, which doesn't preclude personal use) .invalid (however using something that's often intended for use for failure-testing might cause problems if something's precompiled to react to .invalid addresses in a special way) .local (should *only* be used with mDNS, Avahi, ZeroConf, Bonjour and other *automatic* and self-managing naming schemes, and not in traditional DNS or /etc/hosts files) .localhost (can be used for your situation, it is *not* the same as "localhost" that represents 127.0.0.1, but could be mistaken for it by badly coded software) .test (suggested for test purposes, such as work in a lab, where you wanted something distinctly separate from the rest of your normal LAN) You could certainly whack ".internal" onto the end of your hostnames to make up a FQDN without issues. And even though it's a long thing to type, you can make use the search domain feature so it's configured into the networking parameters, and you only ever have to type the hostname. For donkey's years Linux has used .localdomain as a pseudo domain name. While it's not reserved, it's use is widespread and I think you'll hear about it on the grapevine if it ever became unviable to keep on using it. A computer can be assigned a hostname, it can be assigned a domain name. That can be by your configuration (which gives you consistent naming, even when IPs allocated to you are inconsistent), it can be remotely set up by DHCP. In the absence of being assigned either (or both), a computer can work it out by reverse IP lookups on the IP it has, or has been assigned. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
