On Sat 31 Mar 2018 at 12:35:08 (+0100), Joe wrote: > On Fri, 30 Mar 2018 21:17:26 -0500 > David Wright <deb...@lionunicorn.co.uk> wrote: > > > On Fri 30 Mar 2018 at 19:24:21 (+0100), Brian wrote: > > > I do not know where the OP is coming from or, without further > > > detail, where he wants to go. > > > > AIUI or thought I did, the OP wants to change their host foo's > > domainname from foo.local to foo.home. > > > > > > > > On 2018-03-29, mick crane <mick.cr...@gmail.com> wrote: > > > > > > > > > It's not just domainname and /etc/hosts. > > ↑↑↑↑↑↑↑↑↑↑ > > I'm not sure what is meant here. > > > > > > > > > It's every frigging where. > > > > This surprises me. > > > > > > > > > apache > > > > Can't help with this. > > > > > > > > > roundcube > > > > > > > postfix > > > > > > > now my ISP SMTP server is moaning. > > > > It can't come as a surprise that one should reconfigure the email > > system (and network connection) after changing the name of the domain, > > and it shouldn't be that difficult. > > There is a deep well of ambiguity here, and inevitably it was dug by > Microsoft. From the beginning of networking in DOS, an MS computer had > an individual name and a group name. Initially the group was a > 'workgroup', then along came NT with its security/vendor-lock-in > feature of 'domains'. MS domains are basically Kerberos realms > underpinned by LDAP, and in their beginning, had no connection with > Internet domains. For the last decade or so, MS domains have been > somewhat aligned with Internet domains, and the Windows DNS server is > closely tied to the LDAP Active Directory. > > Over on this Path, domains have always been an Internet issue, for > finding servers and sending email. They do not have any real meaning > for Linux workstations. However, if CIFS is in use in a network, most > of its tools will want the name of a workgroup or domain, for > interoperation with Windows machines, of which Samba is a simulation.
I hadn't given that any consideration. Somehow I thought anyone in the OP's situation would probably have any MS "domain" set to WORKGROUP. > A > working Internet mail server will also need to know its domain name(s) > and will itself have at least one public FQDN, but there's no reason why > any of the domain names it serves need to have any CIFS awareness or > connection with a Windows or other local domain name. My mail server at > present handles three public domains, only one of which I use locally. > If a DNS server is in use in even a small network, again this will need > a domain name. I think we can discount that if the user's FQDN was foo.local. I think both you and I may be overthinking the OP's comment above, which reads like a tautology: to change the domainname, you need to change the domainname. > It is a matter of practicality, therefore, to give a private network a > domain name. So it's said, but the nature of these practicalities hasn't exactly been forthcoming in the long thread that's been running two months (apart from getting a dot in the FQDN). > If you lease a public domain name, there is no real > difficulty about using it also in a private network, just a matter of > making sure that external resources using the name can also be found in > local DNS or hosts files. If you could elaborate. Say I have leased example.org, currently at 93.184.216.34, and apart from what's out there on the Internet I have hosts foo.example.org at 192.168.1.2 and bar.example.org at 192.168.1.3 with a router at 192.168.1.1. What do I need to do? For simplicity, I use dhcp from the router which also has no DNS server. So /etc/hosts. Cheers, David.
