Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #194272 > unrolled thread

changing local domain name

Back to article view | Back to linux.debian.user

Contents

  changing local domain name mick crane <mick.crane@gmail.com> - 2018-03-29 19:10 +0200
    Re: changing local domain name Curt <curty@free.fr> - 2018-03-29 20:40 +0200
      Re: changing local domain name mick crane <mick.crane@gmail.com> - 2018-03-29 22:00 +0200
        Re: changing local domain name john doe <johndoe65534@mail.com> - 2018-03-30 08:10 +0200
          Re: changing local domain name David Wright <deblis@lionunicorn.co.uk> - 2018-03-30 18:20 +0200
            Re: changing local domain name john doe <johndoe65534@mail.com> - 2018-04-03 08:40 +0200
              Re: changing local domain name David Wright <deblis@lionunicorn.co.uk> - 2018-04-12 22:30 +0200
                Re: changing local domain name john doe <johndoe65534@mail.com> - 2018-04-13 13:30 +0200
                  Re: changing local domain name Dan Purgert <dan@djph.net> - 2018-04-13 14:30 +0200
                    Re: changing local domain name rhkramer@gmail.com - 2018-04-13 14:50 +0200
                      Re: changing local domain name Dan Purgert <dan@djph.net> - 2018-04-13 15:10 +0200
                        Re: changing local domain name David Wright <deblis@lionunicorn.co.uk> - 2018-04-13 16:10 +0200
      Re: changing local domain name Brian <ad44@cityscape.co.uk> - 2018-03-30 00:10 +0200
        Re: changing local domain name David Wright <deblis@lionunicorn.co.uk> - 2018-03-30 04:10 +0200
          Re: changing local domain name Curt <curty@free.fr> - 2018-03-30 10:40 +0200
            Re: changing local domain name Brian <ad44@cityscape.co.uk> - 2018-03-30 15:10 +0200
          Re: changing local domain name Brian <ad44@cityscape.co.uk> - 2018-03-30 20:30 +0200
            Re: changing local domain name David Wright <deblis@lionunicorn.co.uk> - 2018-03-31 04:20 +0200
              Re: changing local domain name Joe <joe@jretrading.com> - 2018-03-31 13:40 +0200
                Re: changing local domain name David Wright <deblis@lionunicorn.co.uk> - 2018-03-31 17:20 +0200
                  Re: changing local domain name Gene Heskett <gheskett@shentel.net> - 2018-03-31 17:30 +0200
                  Re: changing local domain name Joe <joe@jretrading.com> - 2018-03-31 20:50 +0200
                    Re: changing local domain name David Wright <deblis@lionunicorn.co.uk> - 2018-04-03 00:10 +0200
                  Re: changing local domain name Dan Purgert <dan@djph.net> - 2018-04-03 13:30 +0200

Page 1 of 2  [1] 2  Next page →

#194272 — changing local domain name

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.

think I got them all except cups is unhappy, I don't know why.

-- 
Key ID	4BFEBB31

[toc] | [next] | [standalone]

#194277

On 2018-03-29, mick crane <mick.crane@gmail.com> 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.
>
> think I got them all except cups is unhappy, I don't know why.
>

There's actually a wiki on this:

https://wiki.debian.org/HowTo/ChangeHostname

For cups you might look at 

/etc/printcap

the part after rm=
 rm=einstein
    ********

Of course that part is the part to the left of the first dot in your
fqdn.

Anyway, good luck (my hostname is incorrect, but as it has never caused
me any misery, I've left well enough alone up to this point).

-- 
We are no longer the same, you wiser but not sadder, and I sadder but not
wiser, for wiser I could hardly become without grave personal inconvenience,
whereas sorrow is a thing you can keep adding to all your life long, is it not,
like a stamp or an egg collection, without feeling very much the worse for it,
is it not. --Samuel Beckett

[toc] | [prev] | [next] | [standalone]

#194279

On 2018-03-29 19:34, Curt wrote:
> On 2018-03-29, mick crane <mick.crane@gmail.com> 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.
>> 
>> think I got them all except cups is unhappy, I don't know why.
>> 
> 
> There's actually a wiki on this:
> 
> https://wiki.debian.org/HowTo/ChangeHostname
> 
> For cups you might look at
> 
> /etc/printcap
> 
> the part after rm=
>  rm=einstein
>     ********
> 
> Of course that part is the part to the left of the first dot in your
> fqdn.
> 
> Anyway, good luck (my hostname is incorrect, but as it has never caused
> me any misery, I've left well enough alone up to this point).

Oh, there's more in /var. I'm going to ignore the binary files as I 
don't think they are current and I don't know how to edit them anyway.
In fact the installation is a bit old I could do with tidying it all up 
anyway so I might as well start afresh.
Dunno if these configuration files couldn't use a persistent 
environmental variable for domainname.

mick

ps Samuel Beckett ++

-- 
Key ID	4BFEBB31

[toc] | [prev] | [next] | [standalone]

#194297

On 3/29/2018 9:56 PM, mick crane wrote:
> On 2018-03-29 19:34, Curt wrote:
>> On 2018-03-29, mick crane <mick.crane@gmail.com> 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.
>>>
>>> think I got them all except cups is unhappy, I don't know why.
>>>
>>
>> There's actually a wiki on this:
>>
>> https://wiki.debian.org/HowTo/ChangeHostname
>>
>> For cups you might look at
>>
>> /etc/printcap
>>
>> the part after rm=
>>  rm=einstein
>>     ********
>>
>> Of course that part is the part to the left of the first dot in your
>> fqdn.
>>
>> Anyway, good luck (my hostname is incorrect, but as it has never caused
>> me any misery, I've left well enough alone up to this point).
> 
> Oh, there's more in /var. I'm going to ignore the binary files as I 
> don't think they are current and I don't know how to edit them anyway.
> In fact the installation is a bit old I could do with tidying it all up 
> anyway so I might as well start afresh.
> 

I  always start from scratch when I need to change the hostname/domain 
on a host.
That's probably the only reason I need to start afresh!

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#194320

On Fri 30 Mar 2018 at 08:05:31 (+0200), john doe wrote:
> On 3/29/2018 9:56 PM, mick crane wrote:
> >On 2018-03-29 19:34, Curt wrote:
> >>On 2018-03-29, mick crane <mick.crane@gmail.com> 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.
> >>>
> >>>think I got them all except cups is unhappy, I don't know why.
> >>>
> >>
> >>There's actually a wiki on this:
> >>
> >>https://wiki.debian.org/HowTo/ChangeHostname
> >>
> >>For cups you might look at
> >>
> >>/etc/printcap
> >>
> >>the part after rm=
> >> rm=einstein
> >>    ********
> >>
> >>Of course that part is the part to the left of the first dot in your
> >>fqdn.
> >>
> >>Anyway, good luck (my hostname is incorrect, but as it has never caused
> >>me any misery, I've left well enough alone up to this point).
> >
> >Oh, there's more in /var. I'm going to ignore the binary files as
> >I don't think they are current and I don't know how to edit them
> >anyway.
> >In fact the installation is a bit old I could do with tidying it
> >all up anyway so I might as well start afresh.
> >
> 
> I  always start from scratch when I need to change the
> hostname/domain on a host.
> That's probably the only reason I need to start afresh!

Unless you're running an advertised server, in which case one would
wonder why you felt the need to change things (perhaps part of a
bigger disruption), I can only say I find this rather extreme. Years
ago, I would clone a system (or build in a different box) and then
move it into its new home with very few files to alter. About the only
confusion caused was to ARP, and that only happened when I was on
thinwire ethernet and lasted a few minutes.

I've struggled to find a multitude of files with the name of the
domain in them. Beyond hosts and mailname, where are you finding them
all? One might expect to check or reconfigure exim, dhcp and network
connection client, but what else? If the domain's name is that firmly
embedded into the system, how does anyone travel with a laptop?

For hostname, there are one or two extra places, like hostname
(obviously) and ssh keys, but again I'm struggling. Any software that
wants to know the hostname knows where to look. Most of the work in
changing hostname here would be self-inflicted because I share
configuration files between very different hosts, so the main config
files source other small files with names like .xsession-alum-jessie
for example. Probably not best practice.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#194431

On 3/30/2018 6:11 PM, David Wright wrote:
> On Fri 30 Mar 2018 at 08:05:31 (+0200), john doe wrote:
>> On 3/29/2018 9:56 PM, mick crane wrote:
>>> On 2018-03-29 19:34, Curt wrote:
>>>> On 2018-03-29, mick crane <mick.crane@gmail.com> 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.
>>>>>
>>>>> think I got them all except cups is unhappy, I don't know why.
>>>>>
>>>>
>>>> There's actually a wiki on this:
>>>>
>>>> https://wiki.debian.org/HowTo/ChangeHostname
>>>>
>>>> For cups you might look at
>>>>
>>>> /etc/printcap
>>>>
>>>> the part after rm=
>>>>   rm=einstein
>>>>      ********
>>>>
>>>> Of course that part is the part to the left of the first dot in your
>>>> fqdn.
>>>>
>>>> Anyway, good luck (my hostname is incorrect, but as it has never caused
>>>> me any misery, I've left well enough alone up to this point).
>>>
>>> Oh, there's more in /var. I'm going to ignore the binary files as
>>> I don't think they are current and I don't know how to edit them
>>> anyway.
>>> In fact the installation is a bit old I could do with tidying it
>>> all up anyway so I might as well start afresh.
>>>
>>
>> I  always start from scratch when I need to change the
>> hostname/domain on a host.
>> That's probably the only reason I need to start afresh!
> 
> Unless you're running an advertised server, in which case one would
> wonder why you felt the need to change things (perhaps part of a
> bigger disruption), I can only say I find this rather extreme. 

Thanks for the caution.
As part of improving my network; I went for meaningless hostname and 
using CNAME record to better describe the host.

> Years ago, I would clone a system (or build in a different box) and then
> move it into its new home with very few files to alter. About the only
> confusion caused was to ARP, and that only happened when I was on
> thinwire ethernet and lasted a few minutes.
> 
> I've struggled to find a multitude of files with the name of the
> domain in them. Beyond hosts and mailname, where are you finding them
> all? 

For starter I use recursive grep on '/etc' '/home' ...

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#194737

On Tue 03 Apr 2018 at 08:37:29 (+0200), john doe wrote:
> On 3/30/2018 6:11 PM, David Wright wrote:
> >On Fri 30 Mar 2018 at 08:05:31 (+0200), john doe wrote:
> >>On 3/29/2018 9:56 PM, mick crane wrote:
> >>>On 2018-03-29 19:34, Curt wrote:
> >>>>On 2018-03-29, mick crane <mick.crane@gmail.com> 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.
> >>>>>
> >>>>>think I got them all except cups is unhappy, I don't know why.
> >>>>>
> >>>>
> >>>>There's actually a wiki on this:
> >>>>
> >>>>https://wiki.debian.org/HowTo/ChangeHostname
> >>>>
> >>>>For cups you might look at
> >>>>
> >>>>/etc/printcap
> >>>>
> >>>>the part after rm=
> >>>>  rm=einstein
> >>>>     ********
> >>>>
> >>>>Of course that part is the part to the left of the first dot in your
> >>>>fqdn.
> >>>>
> >>>>Anyway, good luck (my hostname is incorrect, but as it has never caused
> >>>>me any misery, I've left well enough alone up to this point).
> >>>
> >>>Oh, there's more in /var. I'm going to ignore the binary files as
> >>>I don't think they are current and I don't know how to edit them
> >>>anyway.
> >>>In fact the installation is a bit old I could do with tidying it
> >>>all up anyway so I might as well start afresh.
> >>>
> >>
> >>I  always start from scratch when I need to change the
> >>hostname/domain on a host.
> >>That's probably the only reason I need to start afresh!
> >
> >Unless you're running an advertised server, in which case one would
> >wonder why you felt the need to change things (perhaps part of a
> >bigger disruption), I can only say I find this rather extreme.
> 
> Thanks for the caution.
> As part of improving my network; I went for meaningless hostname and
> using CNAME record to better describe the host.

It's not really the hostnames that concern me, but the name of the
domain. (I've only seen the one posting about hostnames, and it's
not settled whether they were serious or not. I tried to give them
the benefit of the doubt with RFC 8117.)

> >Years ago, I would clone a system (or build in a different box) and then
> >move it into its new home with very few files to alter. About the only
> >confusion caused was to ARP, and that only happened when I was on
> >thinwire ethernet and lasted a few minutes.
> >
> >I've struggled to find a multitude of files with the name of the
> >domain in them. Beyond hosts and mailname, where are you finding them
> >all?
> 
> For starter I use recursive grep on '/etc' '/home' ...

I didn't say "how do you¹ find them" but "where are you finding them".
I wouldn't be bothering with /home: anything there is self-inflicted
and can be tidied up any time. The critical ones are /etc and /var/lib
because files here are involved in running the machine.

Apart from the obvious suspects (the files that configure the network
and email system), I don't see many. On a wired system:

/etc/hosts:127.0.1.1 ← canonical domainname and hostname
/etc/exim4/update-exim4.conf.conf ← according to your configuration
/etc/mailname ← ditto

Everything else is either logs (in the past) or cache (ephemeral):

/etc/.git/logs/refs/heads/master ← etckeeper package is installed
/etc/.git/logs/HEAD ← ditto
/var/log/… ← occasional references
/var/cache/debconf/config.dat ← remembers what you configured

¹ "you" being the person who wrote "It's every frigging where."

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#194743

On 4/12/2018 10:21 PM, David Wright wrote:
> On Tue 03 Apr 2018 at 08:37:29 (+0200), john doe wrote:
>> On 3/30/2018 6:11 PM, David Wright wrote:
>>> On Fri 30 Mar 2018 at 08:05:31 (+0200), john doe wrote:
>>>> On 3/29/2018 9:56 PM, mick crane wrote:
>>>>> On 2018-03-29 19:34, Curt wrote:
>>>>>> On 2018-03-29, mick crane <mick.crane@gmail.com> 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.
>>>>>>>
>>>>>>> think I got them all except cups is unhappy, I don't know why.
>>>>>>>
>>>>>>
>>>>>> There's actually a wiki on this:
>>>>>>
>>>>>> https://wiki.debian.org/HowTo/ChangeHostname
>>>>>>
>>>>>> For cups you might look at
>>>>>>
>>>>>> /etc/printcap
>>>>>>
>>>>>> the part after rm=
>>>>>>   rm=einstein
>>>>>>      ********
>>>>>>
>>>>>> Of course that part is the part to the left of the first dot in your
>>>>>> fqdn.
>>>>>>
>>>>>> Anyway, good luck (my hostname is incorrect, but as it has never caused
>>>>>> me any misery, I've left well enough alone up to this point).
>>>>>
>>>>> Oh, there's more in /var. I'm going to ignore the binary files as
>>>>> I don't think they are current and I don't know how to edit them
>>>>> anyway.
>>>>> In fact the installation is a bit old I could do with tidying it
>>>>> all up anyway so I might as well start afresh.
>>>>>
>>>>
>>>> I  always start from scratch when I need to change the
>>>> hostname/domain on a host.
>>>> That's probably the only reason I need to start afresh!
>>>
>>> Unless you're running an advertised server, in which case one would
>>> wonder why you felt the need to change things (perhaps part of a
>>> bigger disruption), I can only say I find this rather extreme.
>>
>> Thanks for the caution.
>> As part of improving my network; I went for meaningless hostname and
>> using CNAME record to better describe the host.
> 
> It's not really the hostnames that concern me, but the name of the
> domain. (I've only seen the one posting about hostnames, and it's
> not settled whether they were serious or not. I tried to give them
> the benefit of the doubt with RFC 8117.)
> 
>>> Years ago, I would clone a system (or build in a different box) and then
>>> move it into its new home with very few files to alter. About the only
>>> confusion caused was to ARP, and that only happened when I was on
>>> thinwire ethernet and lasted a few minutes.
>>>
>>> I've struggled to find a multitude of files with the name of the
>>> domain in them. Beyond hosts and mailname, where are you finding them
>>> all?
>>
>> For starter I use recursive grep on '/etc' '/home' ...
> 
> I didn't say "how do you¹ find them" but "where are you finding them".
> I wouldn't be bothering with /home: anything there is self-inflicted
> and can be tidied up any time. The critical ones are /etc and /var/lib
> because files here are involved in running the machine.
> 
> Apart from the obvious suspects (the files that configure the network
> and email system), I don't see many. On a wired system:
> 
> /etc/hosts:127.0.1.1 ← canonical domainname and hostname
> /etc/exim4/update-exim4.conf.conf ← according to your configuration
> /etc/mailname ← ditto
> 
> Everything else is either logs (in the past) or cache (ephemeral):
> 
> /etc/.git/logs/refs/heads/master ← etckeeper package is installed
> /etc/.git/logs/HEAD ← ditto
> /var/log/… ← occasional references
> /var/cache/debconf/config.dat ← remembers what you configured
> 
> ¹ "you" being the person who wrote "It's every frigging where."
> 

As ilustrated by the above not every one is an english speaker and could 
misunderstand the point you are trying to make! :)

An other thing I'd like to add is that not every one has the same level 
of experience.

-John
-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#194744

john doe wrote:
> As ilustrated by the above not every one is an english speaker and could 
> misunderstand the point you are trying to make! :)

Even us native English speakers have trouble understanding what point
he's trying to maks :)

-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

[toc] | [prev] | [next] | [standalone]

#194745

On Friday, April 13, 2018 08:14:19 AM Dan Purgert wrote:
> john doe wrote:
> > As ilustrated by the above not every one is an english speaker and could
> > misunderstand the point you are trying to make! :)
> 
> Even us native English speakers have trouble understanding what point
> he's trying to maks :)

+1--- not only because he (David) quotes too much--he (David) could do with 
some strategic snipping of the quoted material.

[toc] | [prev] | [next] | [standalone]

#194746

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

rhkramer@gmail.com wrote:
> On Friday, April 13, 2018 08:14:19 AM Dan Purgert wrote:
>> john doe wrote:
>> > As ilustrated by the above not every one is an english speaker and could
>> > misunderstand the point you are trying to make! :)
>> 
>> Even us native English speakers have trouble understanding what point
>> he's trying to maks :)
>
> +1--- not only because he (David) quotes too much--he (David) could do
> with some strategic snipping of the quoted material.

Honestly, my trouble parsing his posts is that the questions aren't
"correct" (or perhaps they're just too subtle for my comprehension) --
leading to several rounds of miscommunication.


-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlrQqEEACgkQjhHd8xJ5
ooF6Awf/SZ2kQ7KpFblVPKNWsWhQ31HI6+T3UraGxXDGPZzAnucaGojt5buKHYjp
MR3blMRXj6KEBaqdKtimbP25b02ACOrZXpM74iCm83h36tF/Tjie7hirk6xM7llU
WV8788TaRiayuOvk/x1OGtbzidWMUzzIQlKZ+z8ed/pHuG5xGo22G+JKGLMm3q4I
3DWzuczjd76PQ8cHOYb8Dh6stXC6sNI8GPzeiriYUbfeabRpGLk6m8KbVUvcxEFl
8O5w+xboXNYo2pUjqkeORxmK4JoKeRmXRQ/R1oXpsEasDsgrmhBy83NoFc/Dtc72
y4a2IhaW6edw9z6Kj/pz7CfFddUFTQ==
=/GC3
-----END PGP SIGNATURE-----

-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

[toc] | [prev] | [next] | [standalone]

#194747

On Fri 13 Apr 2018 at 12:53:21 (-0000), Dan Purgert wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> rhkramer@gmail.com wrote:
> > On Friday, April 13, 2018 08:14:19 AM Dan Purgert wrote:
> >> john doe wrote:
> >> > As ilustrated by the above not every one is an english speaker and could
> >> > misunderstand the point you are trying to make! :)
> >> 
> >> Even us native English speakers have trouble understanding what point
> >> he's trying to maks :)
> >
> > +1--- not only because he (David) quotes too much--he (David) could do
> > with some strategic snipping of the quoted material.
> 
> Honestly, my trouble parsing his posts is that the questions aren't
> "correct" (or perhaps they're just too subtle for my comprehension) --
> leading to several rounds of miscommunication.

Well, here's a chance to correct my questioning. In
https://lists.debian.org/debian-user/2018/03/msg01049.html
the OP wanted to change the name of the domain of their computer from
.local to .home. They wrote "It's not just domainname and /etc/hosts.
It's every frigging where."

As usual, the thread drifted into other areas; someone suggested
looking at the wiki https://wiki.debian.org/HowTo/ChangeHostname
but hostnames weren't the issue, just the domain's name.

After asking the question "Where is this 'every frigging where?'"
I'm told to do a recursive grep. Not exactly an answer to that question.

I listed the places where *I* could find the domain name corp on
a computer here (I assume you could understand that). I did a
recursive search of /etc and /var and eliminated the strings
[a-z0-9]corp and corp[a-z0-9].

In short, there were three significant files.
/etc/hosts /etc/exim4/update-exim4.conf.conf /etc/mailname

Is that 'every frigging where'?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#194285

On Thu 29 Mar 2018 at 18:34:42 +0000, Curt wrote:

> On 2018-03-29, mick crane <mick.crane@gmail.com> 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.
> >
> > think I got them all except cups is unhappy, I don't know why.
> >
> 
> There's actually a wiki on this:
> 
> https://wiki.debian.org/HowTo/ChangeHostname
> 
> For cups you might look at 
> 
> /etc/printcap
> 
> the part after rm=
>  rm=einstein
>     ********

Whatever the OP's problem is (which he doesn't say) /etc/printcap will
not solve it.

brian@desktop:~$ ls -l /etc/printcap
lrwxrwxrwx 1 root root 22 Oct 13 13:31 /etc/printcap -> /var/run/cups/printcap

brian@desktop:~$ cat /etc/printcap | head -n 3
# This file was automatically generated by cupsd(8) from the
# /etc/cups/printers.conf file.  All changes to this file
# will be lost.

https://debian-handbook.info/browse/stable/sect.config-printing.html

Bug#187954.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#194288

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@gmail.com> 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).

> > There's actually a wiki on this:
> > 
> > https://wiki.debian.org/HowTo/ChangeHostname

I don't see the word "domain" on that page. But grepping for the
old name of the domain has never thrown up many references for me.
After all, software should be using getdomainname(), shouldn't it?

> > For cups you might look at 
> > 
> > /etc/printcap
> > 
> > the part after rm=
> >  rm=einstein
> >     ********
> 
> Whatever the OP's problem is (which he doesn't say) /etc/printcap will
> not solve it.
> 
> brian@desktop:~$ ls -l /etc/printcap
> lrwxrwxrwx 1 root root 22 Oct 13 13:31 /etc/printcap -> /var/run/cups/printcap
> 
> brian@desktop:~$ cat /etc/printcap | head -n 3
> # This file was automatically generated by cupsd(8) from the
> # /etc/cups/printers.conf file.  All changes to this file
> # will be lost.
> 
> https://debian-handbook.info/browse/stable/sect.config-printing.html
> 
> Bug#187954.

Yep, rebooting will recreate that file anyway, because /var/run is
just /run, and therefore ephemeral.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#194300

On 2018-03-30, David Wright <deblis@lionunicorn.co.uk> wrote:
>> 
>> https://debian-handbook.info/browse/stable/sect.config-printing.html
>> 
>> Bug#187954.
>
> Yep, rebooting will recreate that file anyway, because /var/run is
> just /run, and therefore ephemeral.

I was just blindly regurgitating the wiki (that dates from the fifties),
which is probably a factor of aggravation rather than mitigation.

Luckily a proviso is clearly written at the top of /etc/printcap, which I
also failed to notice.

Three strikes and you're out.

> Cheers,
> David.
>
>


-- 
We are no longer the same, you wiser but not sadder, and I sadder but not
wiser, for wiser I could hardly become without grave personal inconvenience,
whereas sorrow is a thing you can keep adding to all your life long, is it not,
like a stamp or an egg collection, without feeling very much the worse for it,
is it not. --Samuel Beckett

[toc] | [prev] | [next] | [standalone]

#194308

On Fri 30 Mar 2018 at 08:34:21 +0000, Curt wrote:

> Three strikes and you're out.

You are much too hard on yourself. Without your mail the wiki mistake,
which has since been dealt with, would not have come to light.

Keep batting!

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#194330

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@gmail.com> 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.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#194351

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.crane@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.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#194361

On Fri, 30 Mar 2018 21:17:26 -0500
David Wright <deblis@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.crane@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. 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.

It is a matter of practicality, therefore, to give a private network a
domain name. 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.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#194364

On Sat 31 Mar 2018 at 12:35:08 (+0100), Joe wrote:
> On Fri, 30 Mar 2018 21:17:26 -0500
> David Wright <deblis@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.crane@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.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web