Re: changing local domain name
- Date: Fri, 30 Mar 2018 19:24:21 +0100
- From: Brian <ad44@xxxxxxxxxxxxxxx>
- Subject: Re: changing local domain name
I do not know where the OP is coming from or, without further detail,
where he wants to go.
On Thu 29 Mar 2018 at 21:07:40 -0500, David Wright wrote:
> On Thu 29 Mar 2018 at 23:05:06 (+0100), Brian wrote:
> > On Thu 29 Mar 2018 at 18:34:42 +0000, Curt wrote:
> > > On 2018-03-29, mick crane <mick.crane@xxxxxxxxx> wrote:
> > > > following recent about hostname it seems I've been under
> > > > misunderstanding that ".local" was OK so now I change local domain to
> > > > ".home" .
> > > > It's not just domainname and /etc/hosts. It's every frigging where.
> > > > apache
> > > > roundcube
> > > > postfix
> > > > now my ISP SMTP server is moaning.
> Have you run
> # dpkg-reconfigure exim4-config
> yet? (Or equivalent for whatever's sending to it.)
> > > > think I got them all except cups is unhappy, I don't know why.
> Like exim, CUPS is more complicated as it works both ways. So it may
> depend on whether you're running it as a server for a local printer
> or a client for a networked printer. The latter has never caused me
> any problem when changing the name of my domain. Howver, I haven't
> done the former for about a decade, since my HP990 ran out of ink.
> That might be more complicated, but I thought CUPS only needed
> hostnames as it uses avahi (ie the "proper" use for .local).
You do well to point out that CUPS can be a server or a client. As a
server it only does DNS-SD advertising of printers. Upstream CUPS
expects the client programs to read the DNS-SD broadcasts and display
printers in their dialogs, as I believe happens on a Mac.
On Debian only clients which use the GTK print dialog are the ones I
am aware of which do this. The hostname they will know is that of the
remote system; "hostname = [desktop.local]", for example. In the most
general case the client machine cannot influence this.
Qt apps and libreoffice (or command line programs) do not browse the
Bonjour broadcasts from the server. There's a lot of unhappy customers
to begin with - which is why cups-browsed was invented. It too knows
the hostname of the remote system and can browse the server's Bonjour
broadcasts, which it can pass on to interested clients.
For network printers cups-browsed on the client needs avahi-daemon but
the hostname on the client is immaterial. All cups-browsed does is
browse avahi broadcasts from the server on behalf of clients which
cannot do it themselves.