[opensuse] Where to set the domain name? - Leap 15.1 beta
Hi, Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y Elesar:~ # hostname -A Elesar:~ # hostname Elesar Elesar:~ # So, I start and look into Network Settings, and in hostname I try to write a domain name after a dot - it does not allow me to set a domain name. Where is one supposed to write the domain name? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 12:52 PM, Carlos E. R. wrote:
Where is one supposed to write the domain name?
There's another box just to the right of host name for domain name. However, it doesn't appear to save it. I use Domain Search as a work around. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 19.07, James Knott wrote:
On 05/06/2019 12:52 PM, Carlos E. R. wrote:
Where is one supposed to write the domain name?
There's another box just to the right of host name for domain name.
No, I don't. See photo.
However, it doesn't appear to save it. I use Domain Search as a work around.
Yes, me too, but still... -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test))
06.05.2019 20:28, Carlos E. R. пишет:
On 06/05/2019 19.07, James Knott wrote:
On 05/06/2019 12:52 PM, Carlos E. R. wrote:
Where is one supposed to write the domain name?
There's another box just to the right of host name for domain name.
No, I don't. See photo.
However, it doesn't appear to save it. I use Domain Search as a work around.
Yes, me too, but still...
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 01:53 PM, Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
???? We were talking about Yast. In the hostname/dns config, there is a domain name box that doesn't seem to work. However, the domain search does, so that's the work around. If you don't have one of those, then you can't reach devices on the local LAN via host name only. The domain search box is intended to add other domains, beyond the one specified in domain name, for searching. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
06.05.2019 20:57, James Knott пишет:
On 05/06/2019 01:53 PM, Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
????
We were talking about Yast.
YaST is frontend to individual low level configuration items (mostly various files). What configuration item was modified when you changed "Domain Name" in YaST?
In the hostname/dns config, there is a domain name box that doesn't seem to work.
There is no domain name box.
However, the domain search does, so that's the work around. If you don't have one of those, then you can't reach devices on the local LAN via host name only.
Apples and oranges ...
The domain search box is intended to add other domains, beyond the one specified in domain name, for searching.
Value entered in "Domain Name" input field was not used for searching anything. At least in more or less recent openSUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 02:11 PM, Andrei Borzenkov wrote:
YaST is frontend to individual low level configuration items (mostly various files). What configuration item was modified when you changed "Domain Name" in YaST?
/etc/resolv.conf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
06.05.2019 21:16, James Knott пишет:
On 05/06/2019 02:11 PM, Andrei Borzenkov wrote:
YaST is frontend to individual low level configuration items (mostly various files). What configuration item was modified when you changed "Domain Name" in YaST?
/etc/resolv.conf
See attached screenshot (I tried text mode but am afraid of line wrapping).
On 06/05/2019 20.25, Andrei Borzenkov wrote:
06.05.2019 21:16, James Knott пишет:
On 05/06/2019 02:11 PM, Andrei Borzenkov wrote:
YaST is frontend to individual low level configuration items (mostly various files). What configuration item was modified when you changed "Domain Name" in YaST?
/etc/resolv.conf
See attached screenshot (I tried text mode but am afraid of line wrapping).
But in 15.1 the domain box has disappeared, also in text mode. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 02:11 PM, Andrei Borzenkov wrote:
Value entered in "Domain Name" input field was not used for searching anything. At least in more or less recent openSUSE.
My understanding, going all the way back to when I was doing 3rd level OS/2 support at IBM was the domain name specified the first one searched. If additional search domains were needed, they were added to the domain search list (LAN domain search in OS/2). In openSUSE 15.0, the Domain Name box is still there but, as I mentioned, doesn't save it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 20.11, Andrei Borzenkov wrote:
06.05.2019 20:57, James Knott пишет:
On 05/06/2019 01:53 PM, Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
????
We were talking about Yast.
YaST is frontend to individual low level configuration items (mostly various files). What configuration item was modified when you changed "Domain Name" in YaST?
I have no idea. On another machine, it is "/etc/hostname". cer@Elesar:~> cat /other/main/etc/hostname Telcontar.valinor cer@Elesar:~> If I do the same here: Elesar:~ # cat /etc/hostname Elesar.valinor Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # So, where is the proper place to write the domain name? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, May 6, 2019 12:53:13 PM CDT Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
It's likely package leafnode won't work without a FQDN. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 22.37, Robert T Hardy wrote:
On Monday, May 6, 2019 12:53:13 PM CDT Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
It's likely package leafnode won't work without a FQDN.
True. And postfix. And maybe dovecot. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
06.05.2019 23:37, Robert T Hardy пишет:
On Monday, May 6, 2019 12:53:13 PM CDT Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
It's likely package leafnode won't work without a FQDN.
"Domain Name" field in YaST has very little to do with FQDN. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, May 6, 2019 11:09:44 PM CDT Andrei Borzenkov wrote:
06.05.2019 23:37, Robert T Hardy пишет:
On Monday, May 6, 2019 12:53:13 PM CDT Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
It's likely package leafnode won't work without a FQDN.
"Domain Name" field in YaST has very little to do with FQDN.
OK. It's what I did back in about 13.1 days in order to get leafnode to work. And I did it again with a 15.0 fresh install despite problems I don't remember with Yast, referenced in this thread. For all my trouble I get the log messages: May 07 03:18:24 sgt.decathlon.org nscd[1184]: 1184 monitored file `/etc/ resolv.conf` was written to and May 07 03:18:24 sgt.decathlon.org NetworkManager[31378]: nisdomainname: you must be root to change the domain name And I did it in earlier days (2000 onward?) where the complaint was that you shouldn't be assigning yourself a domain name that's not registered with DNS. My recollection of how it was all supposed to work is pretty vague, and it's gotten a bit more complex since then. I don't think I ever had a complete solution, but the idea is to preserve flexibility, so a computer can be part of a LAN, or part of the internet, or both; can use multiple interfaces, etc. What should I be doing? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, May 07, 2019 at 03:56:26AM -0500, Robert T Hardy wrote:
On Monday, May 6, 2019 11:09:44 PM CDT Andrei Borzenkov wrote:
06.05.2019 23:37, Robert T Hardy пишет:
On Monday, May 6, 2019 12:53:13 PM CDT Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
It's likely package leafnode won't work without a FQDN.
"Domain Name" field in YaST has very little to do with FQDN.
OK. It's what I did back in about 13.1 days in order to get leafnode to work. And I did it again with a 15.0 fresh install despite problems I don't remember with Yast, referenced in this thread. For all my trouble I get the log messages:
May 07 03:18:24 sgt.decathlon.org nscd[1184]: 1184 monitored file `/etc/ resolv.conf` was written to
and
May 07 03:18:24 sgt.decathlon.org NetworkManager[31378]: nisdomainname: you must be root to change the domain name
And I did it in earlier days (2000 onward?) where the complaint was that you shouldn't be assigning yourself a domain name that's not registered with DNS.
My recollection of how it was all supposed to work is pretty vague, and it's gotten a bit more complex since then. I don't think I ever had a complete solution, but the idea is to preserve flexibility, so a computer can be part of a LAN, or part of the internet, or both; can use multiple interfaces, etc.
What should I be doing?
Even if this is mixed up: NIS (Network Information Service) != DNS (Domain Name System) The domain name set by domainname(1) (also called ypdomainname or nisdomainname) set the NIS/YP doamin name seen in /proc/sys/kernel/domainname. Indeed only root can do this. Also echo or sysctl can be used to set the domainname. The DNS domainname can not set local but only provided by the (remote) name server providing the database of the DNS. For this /etc/resolv.conf is used to get the address of the remote name server. You can also run a local name server daemon (bind or dnsmasq) to provide such a DNS for the LAN, for this then the /etc/resolv.conf points to 127.0.0.1. To solve trouble at boot (local or of the host providing the name server) or lost LAN some common FQDN can be written into /etc/hosts. -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On Tuesday, May 7, 2019 4:30:13 AM CDT Dr. Werner Fink wrote:
Even if this is mixed up:
NIS (Network Information Service) != DNS (Domain Name System) [...]
I think the following provides fair clue. It'll give me plenty to read, anyway. I'd like to see a top down overview that gets into things from this angle, but I don't think one is available that is in any way current. I know that entering a domain name in Yast makes leafnode happy. sgt:~ # fetchnews -vv leafnode 1.11.11: verbosity level is 2, debugmode is 0 try_lock(timeout=5), fqdn="sgt.decathlon.org" reader80.eternal-september.org: connecting to port 80... reader80.eternal-september.org: connected to 144.76.35.198:80, reply: 200 reader80.eternal-september.org: connected. [...] It won't do that if it doesn't get that "fqdn" (from Yast in this case). The whole stack, or chain, or pile of software involved can get pretty confusing. For instance, Yast>Network Settings>Hostname/DNS shows "Name Server 1 is 8.8.8.8. Why? Because I entered that in Network Manager's configuration for a particular interface, and that was done because Sprint DNS munges entries. It would try to sell me ietf.org! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 11.30, Dr. Werner Fink wrote:
On Tue, May 07, 2019 at 03:56:26AM -0500, Robert T Hardy wrote:
On Monday, May 6, 2019 11:09:44 PM CDT Andrei Borzenkov wrote:
06.05.2019 23:37, Robert T Hardy пишет:
On Monday, May 6, 2019 12:53:13 PM CDT Andrei Borzenkov wrote:
What exactly does not work now? What setting (on actual system, not in YaST) is missing now? What should have happened if you had Domain input field?
It's likely package leafnode won't work without a FQDN.
"Domain Name" field in YaST has very little to do with FQDN.
Then where?
OK. It's what I did back in about 13.1 days in order to get leafnode to work. And I did it again with a 15.0 fresh install despite problems I don't remember with Yast, referenced in this thread. For all my trouble I get the log messages:
...
My recollection of how it was all supposed to work is pretty vague, and it's gotten a bit more complex since then. I don't think I ever had a complete solution, but the idea is to preserve flexibility, so a computer can be part of a LAN, or part of the internet, or both; can use multiple interfaces, etc.
What should I be doing?
Even if this is mixed up:
NIS (Network Information Service) != DNS (Domain Name System)
The domain name set by domainname(1) (also called ypdomainname or nisdomainname) set the NIS/YP doamin name seen in /proc/sys/kernel/domainname. Indeed only root can do this. Also echo or sysctl can be used to set the domainname.
Ah, you are saying that a call to domainname can set the domain name. man: «When called with one argument or with the --file option, the commands set the host name or the NIS/YP domain name. hostname uses the sethostname(2) function, while all of the three domainname, ypdomainname and nisdomainname use setdomainname(2). Note, that this is effective only until the next reboot. Edit /etc/hostname for permanent change.» So the file to edit is "/etc/hostname". Elesar:~ # domainname Elesar Elesar:~ # domainname Elesar Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # Well, no, that's not quite it. man «It is not possible to set the FQDN or the DNS domain name with the dnsdomainname command (see THE FQDN below).» Ah. «The FQDN (Fully Qualified Domain Name) of the system is the name that the resolver(3) returns for the host name, such as, ursula.example.com. It is usually the hostname followed by the DNS domain name (the part after the first dot). You can check the FQDN using hostname --fqdn or the domain name using dnsdomainname.» Well, no: Elesar:~ # hostname --fqdn hostname: Name or service not known Elesar:~ # As it is a dynamic IP, the DNS can not know about the machine. «The recommended method of setting the FQDN is to make the hostname be an alias for the fully qualified name using /etc/hosts, DNS, or NIS. For example, if the hostname was "ursula", one might have a line in /etc/hosts which reads 127.0.1.1 ursula.example.com ursula » Well, as I said, this method collides with postfix. When I did that, I got this once per minute: .... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2 «Technically: The FQDN is the name getaddrinfo(3) returns for the host name returned by gethostname(2). The DNS domain name is the part after the first dot. Therefore it depends on the configuration of the resolver (usually in /etc/host.conf) how you can change it. Usually the hosts file is parsed before DNS or NIS, so it is most common to change the FQDN in /etc/hosts. If a machine has multiple network interfaces/addresses or is used in a mobile environment, then it may either have multiple FQDNs/domain names or none at all. Therefore avoid using hostname --fqdn, hostname --domain and dnsdomainname. hostname --ip-address is subject to the same limitations so it should be avoided as well.» Well, as the IP is set by DHCP, I need some script to write the correct current entry to /etc/hosts. Meanwhile, write it manually on each boot. But with that alone, "hostnane -f" fails.
The DNS domainname can not set local but only provided by the (remote) name server providing the database of the DNS. For this /etc/resolv.conf is used to get the address of the remote name server. You can also run a local name server daemon (bind or dnsmasq) to provide such a DNS for the LAN, for this then the /etc/resolv.conf points to 127.0.0.1. To solve trouble at boot (local or of the host providing the name server) or lost LAN some common FQDN can be written into /etc/hosts.
The man page says it is set in /etc/hosts :-? Well, as dnsmasq is running on another computer, how do I tell it to write an entry for this machine every time DHCP changes the address? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
«The recommended method of setting the FQDN is to make the hostname be an alias for the fully qualified name using /etc/hosts, DNS, or NIS. For example, if the hostname was "ursula", one might have a line in /etc/hosts which reads
127.0.1.1 ursula.example.com ursula
Well, as I said, this method collides with postfix. When I did that, I got this once per minute:
.... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2
On 15.1 ? I have all of Gertjans 127.0.0.1 entries in my /etc/hosts (office33), postfix works very well. Your 127.0.0.2 entry does not come with the default postfix install.
Well, as dnsmasq is running on another computer, how do I tell it to write an entry for this machine every time DHCP changes the address?
Google "dnsmasq dynamic dns updates". You'll find e.g. http://lightofdawn.org/wiki/wiki.cgi/-wiki/LocalDynamicDns -- Per Jessen, Zürich (10.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 13.39, Per Jessen wrote:
Carlos E. R. wrote:
«The recommended method of setting the FQDN is to make the hostname be an alias for the fully qualified name using /etc/hosts, DNS, or NIS. For example, if the hostname was "ursula", one might have a line in /etc/hosts which reads
127.0.1.1 ursula.example.com ursula
Well, as I said, this method collides with postfix. When I did that, I got this once per minute:
.... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2
On 15.1 ? I have all of Gertjans 127.0.0.1 entries in my /etc/hosts (office33), postfix works very well. Your 127.0.0.2 entry does not come with the default postfix install.
I don't know if this happens on 15.1, and I have no intention to modify my test setup sufficiently to verify it. At the time of the bugzilla, bot sides said "not my issue" and that they had no intention to do anything ever. So, why should it have changed now?
Well, as dnsmasq is running on another computer, how do I tell it to write an entry for this machine every time DHCP changes the address?
Google "dnsmasq dynamic dns updates". You'll find e.g.
Oh, I know very well how to combine "in Linux" dnsmasq with a proper dhcp server. But remember, in this case, I can not ensure control of the dhcp server. I may be a guest at somebody else's place, I may be using Android tethering... (actual situations in which my laptop gets into). So, knowing that the dhcp is in the router or the phone and that I may not have control of it, how do I make dnsmasq adjust to my current local IP, obtained dynamically, on a different machine? Just a theoretical question :-) If pressed, I can figure how to do it, via passwordless ssh sessions and scripts I'd have to develop. But maybe there already exists a command to do it that I'm not aware of. I already have my own scripts to do that with NM and dnsmasq running in the same machine. If I don't do that, postfix for sure fails in 15.0. I don't remember if dovecot failed, and leafnode also had problems. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
Carlos E. R. wrote:
On 07/05/2019 13.39, Per Jessen wrote:
Carlos E. R. wrote:
.... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2
On 15.1 ? I have all of Gertjans 127.0.0.1 entries in my /etc/hosts (office33), postfix works very well. Your 127.0.0.2 entry does not come with the default postfix install.
I don't know if this happens on 15.1, and I have no intention to modify my test setup sufficiently to verify it. At the time of the bugzilla, bot sides said "not my issue" and that they had no intention to do anything ever. So, why should it have changed now?
The real question is (probably) if YaST in Leap15.1 will still configure that 127.0.0.2 entry.
Well, as dnsmasq is running on another computer, how do I tell it to write an entry for this machine every time DHCP changes the address?
Google "dnsmasq dynamic dns updates". You'll find e.g.
Oh, I know very well how to combine "in Linux" dnsmasq with a proper dhcp server. But remember, in this case, I can not ensure control of the dhcp server. I may be a guest at somebody else's place, I may be using Android tethering... (actual situations in which my laptop gets into).
We are probably all in similar situations every now and then. I know I am. I guess you're using your portable machine for something else than I do.
I already have my own scripts to do that with NM and dnsmasq running in the same machine. If I don't do that, postfix for sure fails in 15.0. I don't remember if dovecot failed, and leafnode also had problems.
I don't use the latter two on any laptop, but postfix works fine. (for delivering outbound mails only). -- Per Jessen, Zürich (9.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, May 8, 2019 at 10:29 AM Per Jessen <per@computer.org> wrote:
The real question is (probably) if YaST in Leap15.1 will still configure that 127.0.0.2 entry.
Yes if "Assign hostname to loopback" is checked. It is quite possible that default for this checkbox changed at some point. I am fairly sure it was default in the past, but my 15.0 installation did not have this entry until I played in response to this thread. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
On Wed, May 8, 2019 at 10:29 AM Per Jessen <per@computer.org> wrote:
The real question is (probably) if YaST in Leap15.1 will still configure that 127.0.0.2 entry.
Yes if "Assign hostname to loopback" is checked. It is quite possible that default for this checkbox changed at some point. I am fairly sure it was default in the past, but my 15.0 installation did not have this entry until I played in response to this thread.
ah, nice one, I don't think I've ever used that option. I also tried it just now, but this entry: 127.0.0.2 gaston.local.net gaston will not cause any problems (for postfix). -- Per Jessen, Zürich (10.7°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 10.43, Per Jessen wrote:
Andrei Borzenkov wrote:
On Wed, May 8, 2019 at 10:29 AM Per Jessen <per@computer.org> wrote:
The real question is (probably) if YaST in Leap15.1 will still configure that 127.0.0.2 entry.
Yes if "Assign hostname to loopback" is checked. It is quite possible that default for this checkbox changed at some point. I am fairly sure it was default in the past, but my 15.0 installation did not have this entry until I played in response to this thread.
ah, nice one, I don't think I've ever used that option. I also tried it just now, but this entry:
127.0.0.2 gaston.local.net gaston
will not cause any problems (for postfix).
Try restarting it. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 10.43, Per Jessen wrote:
Andrei Borzenkov wrote:
On Wed, May 8, 2019 at 10:29 AM Per Jessen <per@computer.org> wrote:
The real question is (probably) if YaST in Leap15.1 will still configure that 127.0.0.2 entry.
Yes if "Assign hostname to loopback" is checked. It is quite possible that default for this checkbox changed at some point. I am fairly sure it was default in the past, but my 15.0 installation did not have this entry until I played in response to this thread.
ah, nice one, I don't think I've ever used that option. I also tried it just now, but this entry:
127.0.0.2 gaston.local.net gaston
will not cause any problems (for postfix).
Try restarting it.
Please give me some credit, Carlos. Obviously I restarted it and obviously it worked fine. -- Per Jessen, Zürich (11.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 13.31, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 10.43, Per Jessen wrote:
Andrei Borzenkov wrote:
On Wed, May 8, 2019 at 10:29 AM Per Jessen <per@computer.org> wrote:
The real question is (probably) if YaST in Leap15.1 will still configure that 127.0.0.2 entry.
Yes if "Assign hostname to loopback" is checked. It is quite possible that default for this checkbox changed at some point. I am fairly sure it was default in the past, but my 15.0 installation did not have this entry until I played in response to this thread.
ah, nice one, I don't think I've ever used that option. I also tried it just now, but this entry:
127.0.0.2 gaston.local.net gaston
will not cause any problems (for postfix).
Try restarting it.
Please give me some credit, Carlos. Obviously I restarted it and obviously it worked fine.
Sorry, I didn't guess you did :-) -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 09.29, Per Jessen wrote:
Carlos E. R. wrote:
.... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2
...
Oh, I know very well how to combine "in Linux" dnsmasq with a proper dhcp server. But remember, in this case, I can not ensure control of the dhcp server. I may be a guest at somebody else's place, I may be using Android tethering... (actual situations in which my laptop gets into).
We are probably all in similar situations every now and then. I know I am. I guess you're using your portable machine for something else than I do.
Not many people use postfix nowdays to send mail outside, instead of directly from Thunderbird or whatever. It is possible that some other setting is needed in postfix to trigger the problem, that having 127.0.0.2 name.domain name is not enough. Another question: how can YaST write that entry if it doesn't know the domain name? When posfix is configured using YaST, how is the domain name written to the configuration? etc. Just wondering. :-? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 09.29, Per Jessen wrote:
Carlos E. R. wrote:
[snip]
Oh, I know very well how to combine "in Linux" dnsmasq with a proper dhcp server. But remember, in this case, I can not ensure control of the dhcp server. I may be a guest at somebody else's place, I may be using Android tethering... (actual situations in which my laptop gets into).
We are probably all in similar situations every now and then. I know I am. I guess you're using your portable machine for something else than I do.
Not many people use postfix nowdays to send mail outside, instead of directly from Thunderbird or whatever.
Anyone who runs cron or mdadm will be using postfix to send mails outside. Even if no cron job and no other daemon will use sendmail to drop mails into the queue, postfix is still started, it's the default.
Another question: how can YaST write that entry if it doesn't know the domain name?
Does YaST write that entry, in 15.1 ? In 15.1, I can't find that option Andrei mentioned "Assign hostname to loopback", so it probably doesn't. On 15.0, when I ticked that box, I see 127.0.0.2 gaston.local.net gaston added to /etc/hosts. Also, I still don't see how that 127.0.0.2 entry will make postfix fail. postfix, by default, only listens on "localhost". -- Per Jessen, Zürich (10.7°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, May 8, 2019 at 11:41 AM Per Jessen <per@computer.org> wrote:
Another question: how can YaST write that entry if it doesn't know the domain name?
Does YaST write that entry, in 15.1 ? In 15.1, I can't find that option Andrei mentioned "Assign hostname to loopback", so it probably doesn't.
Indeed, looking in current yast-network sources this option is removed. Anyway, to round this up. Mon Nov 26 11:57:35 UTC 2018 - mfilka@suse.com - bnc#934055, bnc#972463 - cleanup in Hostname / DNS tab - removed obsolete or unsupported options. - 4.1.19 https://github.com/yast/yast-network/commit/f1968c4e44bafbe8941ce8edd8cf5802... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 10.41, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 09.29, Per Jessen wrote:
Carlos E. R. wrote:
[snip]
Oh, I know very well how to combine "in Linux" dnsmasq with a proper dhcp server. But remember, in this case, I can not ensure control of the dhcp server. I may be a guest at somebody else's place, I may be using Android tethering... (actual situations in which my laptop gets into).
We are probably all in similar situations every now and then. I know I am. I guess you're using your portable machine for something else than I do.
Not many people use postfix nowdays to send mail outside, instead of directly from Thunderbird or whatever.
Anyone who runs cron or mdadm will be using postfix to send mails outside.
Certainly. But that's not the majority. There is a demand/request for removing postfix from the default install.
Even if no cron job and no other daemon will use sendmail to drop mails into the queue, postfix is still started, it's the default.
True, but ignored. There are people that don't know it is there and are surprised when they find out. Then some want to remove it.
Another question: how can YaST write that entry if it doesn't know the domain name?
Does YaST write that entry, in 15.1 ? In 15.1, I can't find that option Andrei mentioned "Assign hostname to loopback", so it probably doesn't.
It has disappeared, I notice now. Yesterday I did not know in what panel it was.
On 15.0, when I ticked that box, I see
127.0.0.2 gaston.local.net gaston
added to /etc/hosts.
Right.
Also, I still don't see how that 127.0.0.2 entry will make postfix fail. postfix, by default, only listens on "localhost".
Well, it does. Perhaps it needs some other setting that you don't use and I don't know which. Maybe the one that defines the interface or the name or domain to use. Or maybe you have to restart it. Maybe if it "knows" the machine name is gaston.local.net then it tries to locate the interface; hosts says it is 127.0.0.2, and then fails to bind to that address, it has no interface. Something like that. I do not want to spend time configuring postfix in this test machine, it is complicated - one of those Spanish things James Knott says :-) - that our ISPs do not provide smarthosts. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 10.41, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 09.29, Per Jessen wrote:
Carlos E. R. wrote:
[snip]
Oh, I know very well how to combine "in Linux" dnsmasq with a proper dhcp server. But remember, in this case, I can not ensure control of the dhcp server. I may be a guest at somebody else's place, I may be using Android tethering... (actual situations in which my laptop gets into).
We are probably all in similar situations every now and then. I know I am. I guess you're using your portable machine for something else than I do.
Not many people use postfix nowdays to send mail outside, instead of directly from Thunderbird or whatever.
Anyone who runs cron or mdadm will be using postfix to send mails outside.
Certainly. But that's not the majority. There is a demand/request for removing postfix from the default install.
That disappeared long ago. Precisely because of daemons such as crond, mdadmd, smartd needing a place to report their results. Makes me wonder - how do systemd timers handle the output? Just wondering out loud, I hadn't thought about that one before.
Even if no cron job and no other daemon will use sendmail to drop mails into the queue, postfix is still started, it's the default.
True, but ignored. There are people that don't know it is there and are surprised when they find out. Then some want to remove it.
I think you missed the point - postfix is started and runs, with no problems, in the default config. If people don't know about it, that's their problem :-)
Also, I still don't see how that 127.0.0.2 entry will make postfix fail. postfix, by default, only listens on "localhost".
Well, it does.
I submit - in the default config it does not. When you then change the config, it's entirely up to you.
Maybe if it "knows" the machine name is gaston.local.net then it tries to locate the interface; hosts says it is 127.0.0.2, and then fails to bind to that address, it has no interface. Something like that.
There is no black magic here, postfix does exactly as it is told. In the case of 'gaston', postfix never touches eth0, it only listens on loopback. Of course, if the config is changed to include listening on 'gaston.local.net' = 127.0.0.2, then postfix will fail. -- Per Jessen, Zürich (12.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, May 8, 2019 at 2:30 PM Per Jessen <per@computer.org> wrote:
That disappeared long ago. Precisely because of daemons such as crond, mdadmd, smartd needing a place to report their results. Makes me wonder - how do systemd timers handle the output? Just wondering out loud, I hadn't thought about that one before.
systemd timer do not do much - they just start other units (most pften services) so they do not have much to report. When they do, it goes into journal (or whatever logging method systemd supports). Same applies to services started by timer. They are just systemd units. Either they use logging options supported by systemd (mot likely journald by default) or they implement something different themselves. Systemd does not support e-mailing service output. Personally I am not sure that filling up /var/mail/root on every system by default is actually such a good idea. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
On Wed, May 8, 2019 at 2:30 PM Per Jessen <per@computer.org> wrote:
That disappeared long ago. Precisely because of daemons such as crond, mdadmd, smartd needing a place to report their results. Makes me wonder - how do systemd timers handle the output? Just wondering out loud, I hadn't thought about that one before.
systemd timer do not do much - they just start other units (most pften services) so they do not have much to report. When they do, it goes into journal (or whatever logging method systemd supports).
Same applies to services started by timer. They are just systemd units. Either they use logging options supported by systemd (mot likely journald by default) or they implement something different themselves. Systemd does not support e-mailing service output.
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
Personally I am not sure that filling up /var/mail/root on every system by default is actually such a good idea.
Agree, everyone of my systems sends root email to a central account, but cron output and reports from madmd and smartd are sent to separate accounts. Ah well, note to self - have to study this in more detail. /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, May 8, 2019 at 2:45 PM Per Jessen <per@computer.org> wrote:
Andrei Borzenkov wrote:
On Wed, May 8, 2019 at 2:30 PM Per Jessen <per@computer.org> wrote:
That disappeared long ago. Precisely because of daemons such as crond, mdadmd, smartd needing a place to report their results. Makes me wonder - how do systemd timers handle the output? Just wondering out loud, I hadn't thought about that one before.
systemd timer do not do much - they just start other units (most pften services) so they do not have much to report. When they do, it goes into journal (or whatever logging method systemd supports).
Same applies to services started by timer. They are just systemd units. Either they use logging options supported by systemd (mot likely journald by default) or they implement something different themselves. Systemd does not support e-mailing service output.
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
Not to my best knowledge. MAILTO was implemented by crond which got job output and e-mailed it. Now it is journald that gets output (if anything) and journald does not send any e-mail. Crude workaround is to use something like ExecStart=/bin/sh -c 'program args ... | mail your-mail-address' Where your-mail-address could be set in some configuration file. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 13.45, Per Jessen wrote:
Andrei Borzenkov wrote:
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
cronjobs in 15.0, certainly. But I can test that. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 14.11, Carlos E. R. wrote:
On 08/05/2019 13.45, Per Jessen wrote:
Andrei Borzenkov wrote:
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
cronjobs in 15.0, certainly. But I can test that.
It works just fine. I created a job with "crontab -e": SHELL=/bin/bash MAILTO="cer" * * * * * /usr/share/backgrounds/tierra/generar The script "generar" is missing, so it will fail. Log: 2019-05-08T14:12:52.713612+02:00 Elesar crontab[23454]: (cer) BEGIN EDIT (cer) 2019-05-08T14:18:09.364997+02:00 Elesar crontab[23454]: (cer) REPLACE (cer) 2019-05-08T14:18:09.365306+02:00 Elesar crontab[23454]: (cer) END EDIT (cer) 2019-05-08T14:19:01.584676+02:00 Elesar systemd[1]: Started Session 3 of user cer. 2019-05-08T14:19:01.587662+02:00 Elesar cron[23666]: pam_unix(crond:session): session opened for user cer by (uid=0) 2019-05-08T14:19:01.588673+02:00 Elesar CRON[23667]: (cer) CMD (/usr/share/backgrounds/tierra/generar) 2019-05-08T14:19:01.607243+02:00 Elesar CRON[23666]: pam_unix(crond:session): session closed for user cer mail log: 2019-05-08T14:19:01.611961+02:00 Elesar postfix/pickup[21783]: 955AD43AAD: uid=1000 from=<cer> 2019-05-08T14:19:01.621792+02:00 Elesar postfix/cleanup[23670]: 955AD43AAD: message-id=<20190508121901.955AD43AAD@localhost> 2019-05-08T14:19:01.624053+02:00 Elesar postfix/qmgr[2322]: 955AD43AAD: from=<cer@localhost>, size=850, nrcpt=1 (queue active) 2019-05-08T14:19:01.631806+02:00 Elesar postfix/local[23672]: 955AD43AAD: to=<cer@localhost>, orig_to=<cer>, relay=local, delay=0.03, delays=0.02/0.01/0/0, dsn=2.0.0, status=sent (delivered to mailbox) 2019-05-08T14:19:01.632484+02:00 Elesar postfix/qmgr[2322]: 955AD43AAD: removed mail itself: Date: Wed, 8 May 2019 14:19:01 +0200 (CEST) From: "(Cron Daemon)" <cer@localhost> To: cer@localhost Subject: Cron <cer@Elesar> /usr/share/backgrounds/tierra/generar /bin/bash: /usr/share/backgrounds/tierra/generar: No such file or directory I can try if mail to a different user works. (Curio: the mail header says @localhost, not @Elesar, as I would prefer, but the header says @Elesar) -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 13.45, Per Jessen wrote:
Andrei Borzenkov wrote:
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
cronjobs in 15.0, certainly. But I can test that.
The important bit was if systemd timers, now slowly replacing cron jobs, supported the old behaviour. -- Per Jessen, Zürich (11.4°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 15.37, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.45, Per Jessen wrote:
Andrei Borzenkov wrote:
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
cronjobs in 15.0, certainly. But I can test that.
The important bit was if systemd timers, now slowly replacing cron jobs, supported the old behaviour.
Is the cron daemon be going to be removed, or it is just that jobs are being migrated? In the second case, the system can use timers and I'll keep using cron without worries. In the first case, more fodder for paranoids. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 15.37, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.45, Per Jessen wrote:
Andrei Borzenkov wrote:
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
cronjobs in 15.0, certainly. But I can test that.
The important bit was if systemd timers, now slowly replacing cron jobs, supported the old behaviour.
Is the cron daemon be going to be removed, or it is just that jobs are being migrated?
Currently I see various jobs being migrated to systemd timers.
In the second case, the system can use timers and I'll keep using cron without worries.
Well, I would like to know what the system does too, especially when it doesn't work. -- Per Jessen, Zürich (9.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 20.15, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 15.37, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.45, Per Jessen wrote:
Andrei Borzenkov wrote:
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
cronjobs in 15.0, certainly. But I can test that.
The important bit was if systemd timers, now slowly replacing cron jobs, supported the old behaviour.
Is the cron daemon be going to be removed, or it is just that jobs are being migrated?
Currently I see various jobs being migrated to systemd timers.
In the second case, the system can use timers and I'll keep using cron without worries.
Well, I would like to know what the system does too, especially when it doesn't work.
Certainly. We'll have to learn both systems. Well, cron we already know. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 20.15, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 15.37, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.45, Per Jessen wrote:
Andrei Borzenkov wrote:
Would you happen to know if the old behaviour of cronjobs/timers sending an email to MAILTO is still supported?
cronjobs in 15.0, certainly. But I can test that.
The important bit was if systemd timers, now slowly replacing cron jobs, supported the old behaviour.
Is the cron daemon be going to be removed, or it is just that jobs are being migrated?
Currently I see various jobs being migrated to systemd timers.
In the second case, the system can use timers and I'll keep using cron without worries.
Well, I would like to know what the system does too, especially when it doesn't work.
Certainly. We'll have to learn both systems. Well, cron we already know.
We have every cron output sent to a central location where some automagic triage is done. If deemed necessary, it is then forwarded to a queue where someone who will look into it. I'm not so keen on seeing this output written to the log instead. -- Per Jessen, Zürich (9.5°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 20.36, Per Jessen wrote:
Carlos E. R. wrote:
We have every cron output sent to a central location where some automagic triage is done. If deemed necessary, it is then forwarded to a queue where someone who will look into it. I'm not so keen on seeing this output written to the log instead.
Oh, yes, there is that. At one time, I wrote a *syslog hook that triggered a script when a certain entry happened. Still, you have to create all that handling. Needs time and effort. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 20.36, Per Jessen wrote:
Carlos E. R. wrote:
We have every cron output sent to a central location where some automagic triage is done. If deemed necessary, it is then forwarded to a queue where someone who will look into it. I'm not so keen on seeing this output written to the log instead.
Oh, yes, there is that.
At one time, I wrote a *syslog hook that triggered a script when a certain entry happened.
I think we have quite a few of those - with syslog-ng, it's really straight forward. The easier it is, the more it used :-) -- Per Jessen, Zürich (10.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/05/2019 11.01, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 20.36, Per Jessen wrote:
Carlos E. R. wrote:
We have every cron output sent to a central location where some automagic triage is done. If deemed necessary, it is then forwarded to a queue where someone who will look into it. I'm not so keen on seeing this output written to the log instead.
Oh, yes, there is that.
At one time, I wrote a *syslog hook that triggered a script when a certain entry happened.
I think we have quite a few of those - with syslog-ng, it's really straight forward. The easier it is, the more it used :-)
Unfortunately, I found that rsyslog coordinates better with the journal than the rest. I think we commented on that one day. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On Wed, 08 May 2019 20:36:10 +0200 Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
On 08/05/2019 20.15, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 15.37, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.45, Per Jessen wrote: > Andrei Borzenkov wrote:
> Would you happen to know if the old behaviour of > cronjobs/timers sending an email to MAILTO is still > supported?
cronjobs in 15.0, certainly. But I can test that.
The important bit was if systemd timers, now slowly replacing cron jobs, supported the old behaviour.
Is the cron daemon be going to be removed, or it is just that jobs are being migrated?
Currently I see various jobs being migrated to systemd timers.
In the second case, the system can use timers and I'll keep using cron without worries.
Well, I would like to know what the system does too, especially when it doesn't work.
Certainly. We'll have to learn both systems. Well, cron we already know.
We have every cron output sent to a central location where some automagic triage is done. If deemed necessary, it is then forwarded to a queue where someone who will look into it. I'm not so keen on seeing this output written to the log instead.
I think journald can forward journal events to other places and subsequently process them (see https://www.freedesktop.org/software/systemd/man/systemd-journal-remote.serv... for some of it) so you would just need to read the forwarded logs on the central machine and do your normal processing, I think? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
We have every cron output sent to a central location where some automagic triage is done. If deemed necessary, it is then forwarded to a queue where someone who will look into it. I'm not so keen on seeing this output written to the log instead.
I think journald can forward journal events to other places and subsequently process them (see https://www.freedesktop.org/software/systemd/man/systemd-journal-remote.serv... for some of it) so you would just need to read the forwarded logs on the central machine and do your normal processing, I think?
I'll have to try it out, it's on my list. Sofar I think the only one that's been of interest was logrotate and we just reverted that to a cronjob. -- Per Jessen, Zürich (10.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 13.29, Per Jessen wrote:
Carlos E. R. wrote:
...
Certainly. But that's not the majority. There is a demand/request for removing postfix from the default install.
That disappeared long ago. Precisely because of daemons such as crond, mdadmd, smartd needing a place to report their results. Makes me wonder - how do systemd timers handle the output? Just wondering out loud, I hadn't thought about that one before.
I don't know, either.
Even if no cron job and no other daemon will use sendmail to drop mails into the queue, postfix is still started, it's the default.
True, but ignored. There are people that don't know it is there and are surprised when they find out. Then some want to remove it.
I think you missed the point - postfix is started and runs, with no problems, in the default config. If people don't know about it, that's their problem :-)
Yeah, I know it runs fine by default.
Also, I still don't see how that 127.0.0.2 entry will make postfix fail. postfix, by default, only listens on "localhost".
Well, it does.
I submit - in the default config it does not. When you then change the config, it's entirely up to you.
Maybe if it "knows" the machine name is gaston.local.net then it tries to locate the interface; hosts says it is 127.0.0.2, and then fails to bind to that address, it has no interface. Something like that.
There is no black magic here, postfix does exactly as it is told. In the case of 'gaston', postfix never touches eth0, it only listens on loopback. Of course, if the config is changed to include listening on 'gaston.local.net' = 127.0.0.2, then postfix will fail.
But all my LAN machines with openSUSE (except some test partitions) have a postfix that listens on the eth0 or wifi port and accept/send mails to other machines in the LAN. I have to change the default config for that - and typically, I use the YaST mail module for this change. Now that in 15.1 the 127.0.0.2 line is not created, I don't expect that problem. There might be problems with some other applications (I don't remember which) that required that entry. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 05:30 AM, Dr. Werner Fink wrote:
The DNS domainname can not set local but only provided by the (remote) name server providing the database of the DNS.
These days it's common to run a local DNS backed up by a public DNS for hosts outside of the LAN. I run pfSense and use it's DNS for local host names and I also have my own public domain name, which anyone in the world can reach. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 12:09 AM, Andrei Borzenkov wrote:
"Domain Name" field in YaST has very little to do with FQDN.
It adds the domain name to resolv.conf. If the domain name is not in that file, then yo u must use the FQDN to access anything on the LAN. Here's some info from the resolv.conf man page: "domain Local domain name. Most queries for names within this domain can use short names relative to the local domain. If set to '.', the root domain is considered. If no domain entry is present, the domain is determined from the local hostname returned by gethostname(2); the domain part is taken to be everything after the first '.'. Finally, if the hostname does not contain a domain part, the root domain is assumed. search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names. Resolver queries having fewer than ndots dots (default is 1) in them will be attempted using each component of the search path in turn until a match is found. For environments with multiple subdomains please read options ndots:n below to avoid man-in-the-middle attacks and unnecessary traffic for the root-dns-servers. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains." Notice what it says about the domain name and search domains. You need the local domain to be listed in there somewhere. Yesterday, I removed the domain name and could no longer ping with just the host name. I had to use the FQDN. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 01:28 PM, Carlos E. R. wrote:
No, I don't. See photo.
It should be there. I guess yours is defective. Must be one of those weird Spanish things. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 19.59, James Knott wrote:
On 05/06/2019 01:28 PM, Carlos E. R. wrote:
No, I don't. See photo.
It should be there. I guess yours is defective. Must be one of those weird Spanish things. ;-)
Are you using Leap 15.1 Beta? On my laptop, which is using Leap 15.0, YaST has that domain box. So, is this a bug in 15.1, or is it intentional? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
06.05.2019 21:23, Carlos E. R. пишет:
On 06/05/2019 19.59, James Knott wrote:
On 05/06/2019 01:28 PM, Carlos E. R. wrote:
No, I don't. See photo.
It should be there. I guess yours is defective. Must be one of those weird Spanish things. ;-)
Are you using Leap 15.1 Beta?
On my laptop, which is using Leap 15.0, YaST has that domain box.
So, is this a bug in 15.1, or is it intentional?
Again - what exactly constitutes "bug"? What worked on 15.0 but does not work on 15.1 because this field is not present? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 20.28, Andrei Borzenkov wrote:
06.05.2019 21:23, Carlos E. R. пишет:
On 06/05/2019 19.59, James Knott wrote:
On 05/06/2019 01:28 PM, Carlos E. R. wrote:
No, I don't. See photo.
It should be there. I guess yours is defective. Must be one of those weird Spanish things. ;-)
Are you using Leap 15.1 Beta?
On my laptop, which is using Leap 15.0, YaST has that domain box.
So, is this a bug in 15.1, or is it intentional?
Again - what exactly constitutes "bug"? What worked on 15.0 but does not work on 15.1 because this field is not present?
The disappearance of the domain name box in yast, what else? With that box missing, what is the correct manner of setting the domain name, so that command "hostname -f" works? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
06.05.2019 21:30, Carlos E. R. пишет:
On 06/05/2019 20.28, Andrei Borzenkov wrote:
06.05.2019 21:23, Carlos E. R. пишет:
On 06/05/2019 19.59, James Knott wrote:
On 05/06/2019 01:28 PM, Carlos E. R. wrote:
No, I don't. See photo.
It should be there. I guess yours is defective. Must be one of those weird Spanish things. ;-)
Are you using Leap 15.1 Beta?
On my laptop, which is using Leap 15.0, YaST has that domain box.
So, is this a bug in 15.1, or is it intentional?
Again - what exactly constitutes "bug"? What worked on 15.0 but does not work on 15.1 because this field is not present?
The disappearance of the domain name box in yast, what else?
Removal of input field that apparently served little purpose is a bug?
With that box missing, what is the correct manner of setting the domain name, so that command "hostname -f" works?
This field had very little to do with "hostname -f". "hostname -f" returns result of name resolution. So define your FQDN in /etc/hosts or on your DNS server. That happened when "Assign hostname to loopback" was checked - YaST added entry to /etc/hosts with FQDN (hostname.domain) so "hostname -f" worked. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 02:45 PM, Andrei Borzenkov wrote:
Removal of input field that apparently served little purpose is a bug?
If I have the domain name in resolv.conf and ping my firewall, I get: # ping firewall PING firewall(firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3)) 56 data bytes 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=1 ttl=64 time=0.254 ms 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=2 ttl=64 time=0.349 ms 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=3 ttl=64 time=0.282 ms If I remove the domain name: # ping firewall ping: firewall: Name or service not known So, the local domain must be specified for local domain searches to work on host name only. For as long as I've been working with TCP/IP, that was done with the domain name box. Now, the work around is to use domain search. Is this now the "official" way? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 20.45, Andrei Borzenkov wrote:
06.05.2019 21:30, Carlos E. R. пишет:
On 06/05/2019 20.28, Andrei Borzenkov wrote:
06.05.2019 21:23, Carlos E. R. пишет:
On 06/05/2019 19.59, James Knott wrote:
On 05/06/2019 01:28 PM, Carlos E. R. wrote:
No, I don't. See photo.
It should be there. I guess yours is defective. Must be one of those weird Spanish things. ;-)
Are you using Leap 15.1 Beta?
On my laptop, which is using Leap 15.0, YaST has that domain box.
So, is this a bug in 15.1, or is it intentional?
Again - what exactly constitutes "bug"? What worked on 15.0 but does not work on 15.1 because this field is not present?
The disappearance of the domain name box in yast, what else?
Removal of input field that apparently served little purpose is a bug?
News to me.
With that box missing, what is the correct manner of setting the domain name, so that command "hostname -f" works?
This field had very little to do with "hostname -f". "hostname -f" returns result of name resolution. So define your FQDN in /etc/hosts or on your DNS server. That happened when "Assign hostname to loopback" was checked - YaST added entry to /etc/hosts with FQDN (hostname.domain) so "hostname -f" worked.
The IP is dynamic (not NM), so I can not add the line to /etc/hosts myself (not talking of loopback). Ie, if my current IP is 192.168.1.132, I should get: 192.168.1.132 Elesar.valinor or 192.168.1.133 Elesar.valinor the next day: 192.168.1.134 Elesar.valinor On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP. But there must be a better way. If you are going to say that it is the job of the DHCP server, I don't agree. It can be an android phone, so not controllable. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
06.05.2019 21:59, Carlos E. R. пишет:
On 06/05/2019 20.45, Andrei Borzenkov wrote:
06.05.2019 21:30, Carlos E. R. пишет:
On 06/05/2019 20.28, Andrei Borzenkov wrote:
06.05.2019 21:23, Carlos E. R. пишет:
On 06/05/2019 19.59, James Knott wrote:
On 05/06/2019 01:28 PM, Carlos E. R. wrote: > No, I don't. See photo.
It should be there. I guess yours is defective. Must be one of those weird Spanish things. ;-)
Are you using Leap 15.1 Beta?
On my laptop, which is using Leap 15.0, YaST has that domain box.
So, is this a bug in 15.1, or is it intentional?
Again - what exactly constitutes "bug"? What worked on 15.0 but does not work on 15.1 because this field is not present?
The disappearance of the domain name box in yast, what else?
Removal of input field that apparently served little purpose is a bug?
News to me.
With that box missing, what is the correct manner of setting the domain name, so that command "hostname -f" works?
This field had very little to do with "hostname -f". "hostname -f" returns result of name resolution. So define your FQDN in /etc/hosts or on your DNS server. That happened when "Assign hostname to loopback" was checked - YaST added entry to /etc/hosts with FQDN (hostname.domain) so "hostname -f" worked.
The IP is dynamic (not NM), so I can not add the line to /etc/hosts myself (not talking of loopback).
Your requirement was that "hostname -f" works and checking "Assign hostname to loopback" makes it work.
Ie, if my current IP is 192.168.1.132, I should get:
192.168.1.132 Elesar.valinor
or
192.168.1.133 Elesar.valinor
the next day:
192.168.1.134 Elesar.valinor
So configure IP reservation on your DHCP server or use static address if it matter to you.
On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP.> But there must be a better way.
If you are going to say that it is the job of the DHCP server,
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I don't agree. It can be an android phone, so not controllable.
How exactly changes in YaST suddenly become relevant to Android phones? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 21.14, Andrei Borzenkov wrote:
06.05.2019 21:59, Carlos E. R. пишет:
On 06/05/2019 20.45, Andrei Borzenkov wrote:
06.05.2019 21:30, Carlos E. R. пишет:
On 06/05/2019 20.28, Andrei Borzenkov wrote:
06.05.2019 21:23, Carlos E. R. пишет:
On 06/05/2019 19.59, James Knott wrote: > On 05/06/2019 01:28 PM, Carlos E. R. wrote: >> No, I don't. See photo. > > It should be there. I guess yours is defective. Must be one of those > weird Spanish things. ;-) > >
Are you using Leap 15.1 Beta?
On my laptop, which is using Leap 15.0, YaST has that domain box.
So, is this a bug in 15.1, or is it intentional?
Again - what exactly constitutes "bug"? What worked on 15.0 but does not work on 15.1 because this field is not present?
The disappearance of the domain name box in yast, what else?
Removal of input field that apparently served little purpose is a bug?
News to me.
With that box missing, what is the correct manner of setting the domain name, so that command "hostname -f" works?
This field had very little to do with "hostname -f". "hostname -f" returns result of name resolution. So define your FQDN in /etc/hosts or on your DNS server. That happened when "Assign hostname to loopback" was checked - YaST added entry to /etc/hosts with FQDN (hostname.domain) so "hostname -f" worked.
The IP is dynamic (not NM), so I can not add the line to /etc/hosts myself (not talking of loopback).
Your requirement was that "hostname -f" works and checking "Assign hostname to loopback" makes it work.
No, that way breaks postfix and dovecot. There is an old bugzilla about it.
Ie, if my current IP is 192.168.1.132, I should get:
192.168.1.132 Elesar.valinor
or
192.168.1.133 Elesar.valinor
the next day:
192.168.1.134 Elesar.valinor
So configure IP reservation on your DHCP server or use static address if it matter to you.
Why should I? And what would I do when I tether to my android phone?
On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP.> But there must be a better way.
If you are going to say that it is the job of the DHCP server,
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple! You are basically saying "nowhere".
I don't agree. It can be an android phone, so not controllable.
How exactly changes in YaST suddenly become relevant to Android phones?
You are being intentionally obtuse. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 06/05/2019 21.14, Andrei Borzenkov wrote:
06.05.2019 21:59, Carlos E. R. пишет:
On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP.> But there must be a better way.
If you are going to say that it is the job of the DHCP server,
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
I think Andrei is saying it isn't necessary and asks you to show which problem it creates for you. -- Per Jessen, Zürich (5.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 22.55, Per Jessen wrote:
Carlos E. R. wrote:
On 06/05/2019 21.14, Andrei Borzenkov wrote:
06.05.2019 21:59, Carlos E. R. пишет:
On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP.> But there must be a better way.
If you are going to say that it is the job of the DHCP server,
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
I think Andrei is saying it isn't necessary and asks you to show which problem it creates for you.
In this machine, which is only a test machine, that "domainname" does not work. That is, if you wish, an aesthetic problem. But on other machines, postfix does not start if the host and domain names do not work. Leafnode, as just mentioned by Robert, also fails. And maybe, I don't remember, dovecot also has problems. Setting the FQDN to 127.0.0.1 also breaks postfix, I have a bugzilla on that for years. You read it, we spoke about it. Postfix people said it was not their problem, just remove the line from the hosts file. *SUSE people say postfix should "correct" their code. So, as there is no way in YaST to set the domain name we are left to our own. On the machines that actually need it and are on dynamic IP (and I don't control the IP) I use a script hook on NM to write the FQDN to the hosts file dynamically. That's a hack. It should be able to set the FQDN in YaST (or NM), and it should just work. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
07.05.2019 0:06, Carlos E. R. пишет:
On 06/05/2019 22.55, Per Jessen wrote:
Carlos E. R. wrote:
On 06/05/2019 21.14, Andrei Borzenkov wrote:
06.05.2019 21:59, Carlos E. R. пишет:
On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP.> But there must be a better way.
If you are going to say that it is the job of the DHCP server,
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
I think Andrei is saying it isn't necessary and asks you to show which problem it creates for you.
In this machine, which is only a test machine, that "domainname" does not work. That is, if you wish, an aesthetic problem.
How is it related to "Domain Name" field? I have here system with 15.0 and set "Domain Name" in YaST and "domainname" does not work.
But on other machines, postfix does not start if the host and domain names do not work. Leafnode, as just mentioned by Robert, also fails. And maybe, I don't remember, dovecot also has problems.
You still failed to show any evidence that this is due to missing "Domain Name" field in YaST.
Setting the FQDN to 127.0.0.1 also breaks postfix, I have a bugzilla on that for years. You read it, we spoke about it. Postfix people said it was not their problem, just remove the line from the hosts file. *SUSE people say postfix should "correct" their code.
So, as there is no way in YaST to set the domain name we are left to our own.
You yourself admitted earlier that you do not even know what entering "Domain Name" in YaST actually did.
On the machines that actually need it and are on dynamic IP (and I don't control the IP) I use a script hook on NM to write the FQDN to the hosts file dynamically.
That's a hack.
So you claim that if you enter "Domain Name" in YaST and are on system with dynamic IP something will enter FQDN matching current IP in hosts file automatically for you. Is it correct? Otherwise how is it all relevant to your original question?
It should be able to set the FQDN in YaST (or NM), and it should just work.
Show evidence that with "Domain Name" field in YaST system worked as you want and without this field it stopped working as you want. Otherwise how is it relevant to your original question? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 06.21, Andrei Borzenkov wrote:
07.05.2019 0:06, Carlos E. R. пишет:
On 06/05/2019 22.55, Per Jessen wrote:
Carlos E. R. wrote:
On 06/05/2019 21.14, Andrei Borzenkov wrote:
06.05.2019 21:59, Carlos E. R. пишет:
On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP.> But there must be a better way.
If you are going to say that it is the job of the DHCP server,
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
I think Andrei is saying it isn't necessary and asks you to show which problem it creates for you.
In this machine, which is only a test machine, that "domainname" does not work. That is, if you wish, an aesthetic problem.
How is it related to "Domain Name" field? I have here system with 15.0 and set "Domain Name" in YaST and "domainname" does not work.
I don't know if it is related or not. YaST in 15.0 has a box to write the domain name and I assume it works. Now the box has disappeared, and I ask, reasonably, where do I define the domain name now? It is reasonable to assume that a box in network setup that says "name" sets the name and a box named "domain name" sets the domain name, no? cer@minas-tirith:~> cat /etc/hostname minas-tirith.valinor cer@minas-tirith:~> domainname (none) cer@minas-tirith:~> hostname -f minas-tirith.valinor cer@minas-tirith:~> cat /etc/os-release NAME="openSUSE Leap" VERSION="15.0" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.0" PRETTY_NAME="openSUSE Leap 15.0" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.0" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" cer@minas-tirith:~>
But on other machines, postfix does not start if the host and domain names do not work. Leafnode, as just mentioned by Robert, also fails. And maybe, I don't remember, dovecot also has problems.
You still failed to show any evidence that this is due to missing "Domain Name" field in YaST.
I said no such thing. I said it is due to the lack of domain name in the system. That "hostname -f" fails.
Setting the FQDN to 127.0.0.1 also breaks postfix, I have a bugzilla on that for years. You read it, we spoke about it. Postfix people said it was not their problem, just remove the line from the hosts file. *SUSE people say postfix should "correct" their code.
So, as there is no way in YaST to set the domain name we are left to our own.
You yourself admitted earlier that you do not even know what entering "Domain Name" in YaST actually did.
Why should I know? I assumes it sets the domain name doing whatever is necessary.
On the machines that actually need it and are on dynamic IP (and I don't control the IP) I use a script hook on NM to write the FQDN to the hosts file dynamically.
That's a hack.
So you claim that if you enter "Domain Name" in YaST and are on system with dynamic IP something will enter FQDN matching current IP in hosts file automatically for you. Is it correct? Otherwise how is it all relevant to your original question?
No, I don't claim all that, seeing the responses. I hoped it did. My question still remains: Where do I set the domain name so that it works? I have my guess, maybe I'm wrong. But see, in this machine the fqdn works.
It should be able to set the FQDN in YaST (or NM), and it should just work.
Show evidence that with "Domain Name" field in YaST system worked as you want and without this field it stopped working as you want. Otherwise how is it relevant to your original question?
I have not claimed such thing. YaST did claim so. Why else would it have that box? -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
* Carlos E. R. <robin.listas@telefonica.net> [05-07-19 17:35]:
On 07/05/2019 06.21, Andrei Borzenkov wrote: [...]
How is it related to "Domain Name" field? I have here system with 15.0 and set "Domain Name" in YaST and "domainname" does not work.
I don't know if it is related or not. YaST in 15.0 has a box to write the domain name and I assume it works. Now the box has disappeared, and I ask, reasonably, where do I define the domain name now?
It is reasonable to assume that a box in network setup that says "name" sets the name and a box named "domain name" sets the domain name, no?
fwiw, tw/yast has no place that I see to set "domainname", only hostname. and I cannot remember when it lost that setting. 42.2 does have a place to set domainname -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@jknott.net> [05-07-19 20:25]:
On 05/07/2019 07:39 PM, Patrick Shanahan wrote:
42.2 does have a place to set domainname
Does it work?
don't really know, domain is correct and I don't recall setting it. but domain is correct on all my local boxes and most are tw which does not offer a yast setting for domain. subject 42.2 box is my server and mail/ssh/http(s) all work fine. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 05:35 PM, Carlos E. R. wrote:
I don't know if it is related or not. YaST in 15.0 has a box to write the domain name and I assume it works.
No it doesn't. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 02.13, James Knott wrote:
On 05/07/2019 05:35 PM, Carlos E. R. wrote:
I don't know if it is related or not. YaST in 15.0 has a box to write the domain name and I assume it works.
No it doesn't.
Maybe they removed the entry because it does not work, and is impossible to make it work. Did it work in the past? I can't test, my vmware doesn't run. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, May 8, 2019 3:26:45 AM CDT Carlos E. R. wrote:
On 08/05/2019 02.13, James Knott wrote:
On 05/07/2019 05:35 PM, Carlos E. R. wrote:
I don't know if it is related or not. YaST in 15.0 has a box to write the domain name and I assume it works.
No it doesn't.
Maybe they removed the entry because it does not work, and is impossible to make it work. Did it work in the past? I can't test, my vmware doesn't run.
Someone suggested that if you write it in search domain, then save and restart, you will then see it in domain name (and in /etc/hosts). I think that's what I did though I don't remember. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 06/05/2019 22.55, Per Jessen wrote:
Carlos E. R. wrote:
On 06/05/2019 21.14, Andrei Borzenkov wrote:
06.05.2019 21:59, Carlos E. R. пишет:
On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP.> But there must be a better way.
If you are going to say that it is the job of the DHCP server,
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
I think Andrei is saying it isn't necessary and asks you to show which problem it creates for you.
In this machine, which is only a test machine, that "domainname" does not work. That is, if you wish, an aesthetic problem.
If I read the man page correctly, "domainname" will print the NIS domain? Did you mean to write "hostname -f" ?
But on other machines, postfix does not start if the host and domain names do not work.
Well, here we should probably restrict ourselves to what happens on Leap15.1. postfix is no doubt running fine, it is started by default.
So, as there is no way in YaST to set the domain name we are left to our own.
I still don't see any description of the actual problem you are seeing. Preferably with error messages etc. -- Per Jessen, Zürich (5.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 08.31, Per Jessen wrote:
Carlos E. R. wrote:
On 06/05/2019 22.55, Per Jessen wrote:
Carlos E. R. wrote:
On 06/05/2019 21.14, Andrei Borzenkov wrote:
06.05.2019 21:59, Carlos E. R. пишет:
On another machine I have my own script hanging from NM that edits /etc/hosts dynamically to write the correct full name and current IP.> But there must be a better way.
If you are going to say that it is the job of the DHCP server,
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
I think Andrei is saying it isn't necessary and asks you to show which problem it creates for you.
In this machine, which is only a test machine, that "domainname" does not work. That is, if you wish, an aesthetic problem.
If I read the man page correctly, "domainname" will print the NIS domain? Did you mean to write "hostname -f" ?
NIS domain? I missed that, sorry (the command has the wrong name, IMHO). Yes, I mean "hostname -f".
But on other machines, postfix does not start if the host and domain names do not work.
Well, here we should probably restrict ourselves to what happens on Leap15.1. postfix is no doubt running fine, it is started by default.
Maybe, but I'm not testing it now. It is quite complicated to do, I'm examining previous steps that I would need to set it up. Setting the domain name is one step, I found a hurdle, and asked. Simple! I don't understand the brouhaha and some people getting angry, as if hitting a bees nest :-(
So, as there is no way in YaST to set the domain name we are left to our own.
I still don't see any description of the actual problem you are seeing. Preferably with error messages etc.
First post in the thread: +++............ Hi, Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y Elesar:~ # hostname -A Elesar:~ # hostname Elesar Elesar:~ # So, I start and look into Network Settings, and in hostname I try to write a domain name after a dot - it does not allow me to set a domain name. Where is one supposed to write the domain name? ............++- I think it is pretty simple! :-) Maybe the answer is "you can not set the domain name of the machine. You have to set it up in the DNS. The query about your own IP answers the fqdn". But that answer does not consider multiple domains, so... :-? That would leave me very confused. But then I would ask: "what was then the purpose of the missing domain name entry box that previous yast versions had? If it was not to set the domain name of the machine, then what was its purpose?" It has been there for decades. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
Carlos E. R. wrote:
On 07/05/2019 08.31, Per Jessen wrote:
Carlos E. R. wrote:
But on other machines, postfix does not start if the host and domain names do not work.
Well, here we should probably restrict ourselves to what happens on Leap15.1. postfix is no doubt running fine, it is started by default.
Maybe, but I'm not testing it now. It is quite complicated to do, I'm examining previous steps that I would need to set it up. Setting the domain name is one step, I found a hurdle, and asked. Simple! I don't understand the brouhaha and some people getting angry, as if hitting a bees nest :-(
My interpretation - you found a missing field in the YaST network config, others explained it was not needed, you weren't convinced, then I suggested you describe the problem you're seeing.
I still don't see any description of the actual problem you are seeing. Preferably with error messages etc.
First post in the thread:
+++............ Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y Elesar:~ # hostname -A Elesar:~ # hostname Elesar Elesar:~ #
Okay, my mistake, I didn't take that to be all there is. FWIW, I see no such issue here. (different situation though, working dns). office33:/var/lib/tempmon # hostname -f office33.example.com office33:/var/lib/tempmon # cat /etc/HOSTNAME office33:/var/lib/tempmon # "hostname -f" does an address lookup - getaddrinfo() - which will most likely be satisfied by nscd. On my system above, I suspect it looks at the search option in /etc/resolv.conf, then does a lookup of "office33.example.com" which is fine. On your system this does not work, as you have no local dns?
So, I start and look into Network Settings, and in hostname I try to write a domain name after a dot - it does not allow me to set a domain name.
Right, that's the normal behaviour.
Where is one supposed to write the domain name? ............++- I think it is pretty simple! :-)
Time for bugzilla then :-)
Maybe the answer is "you can not set the domain name of the machine. You have to set it up in the DNS. The query about your own IP answers the fqdn". But that answer does not consider multiple domains, so... :-?
A machine will always only have one name, but may be reached by multiple other names. I don't think it would be right for our network config to assume the presence of a local DNS. Maybe the question ought to be "with no local DNS, why do you need a local domain name?"
But then I would ask: "what was then the purpose of the missing domain name entry box that previous yast versions had? If it was not to set the domain name of the machine, then what was its purpose?" It has been there for decades.
It's a moot point now, but looking at some of my elderly machines, the domain name was written to /etc/HOSTNAME - I see e.g. "linux.suse" or "linux-0ya0.site" on some of them. -- Per Jessen, Zürich (9.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 09.06, Per Jessen wrote:
Carlos E. R. wrote:
I still don't see any description of the actual problem you are seeing. Preferably with error messages etc.
First post in the thread:
(the rest were explanations to questions asked by others)
+++............ Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y Elesar:~ # hostname -A Elesar:~ # hostname Elesar Elesar:~ #
Okay, my mistake, I didn't take that to be all there is. FWIW, I see no such issue here. (different situation though, working dns).
I have a working local dns, with dnsmaq in another computer. Elesar:/etc # grep bilbo /etc/hosts Elesar:/etc # host bilbo bilbo has address 192.168.1.3 Elesar:/etc # Elesar:/etc # hostname -f hostname: Name or service not known Elesar:/etc #
office33:/var/lib/tempmon # hostname -f office33.example.com office33:/var/lib/tempmon # cat /etc/HOSTNAME office33:/var/lib/tempmon #
"hostname -f" does an address lookup - getaddrinfo() - which will most likely be satisfied by nscd. On my system above, I suspect it looks at the search option in /etc/resolv.conf, then does a lookup of "office33.example.com" which is fine. On your system this does not work, as you have no local dns?
But I have a dns in the LAN, just not in this machine. And currently, for testing, I have commented out the search line in resolv.conf, with no difference.
So, I start and look into Network Settings, and in hostname I try to write a domain name after a dot - it does not allow me to set a domain name.
Right, that's the normal behaviour.
Well, I thought that if there was no separate box for the domain I would have to write it to the name box.
Where is one supposed to write the domain name? ............++- I think it is pretty simple! :-)
Time for bugzilla then :-)
Ho ho ho! I'm afraid of doing that, seeing some of the responses.
Maybe the answer is "you can not set the domain name of the machine. You have to set it up in the DNS. The query about your own IP answers the fqdn". But that answer does not consider multiple domains, so... :-?
Ah, I remember: the local dns has no answer for my IP. Elesar:/etc # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 ... Elesar:/etc # host 192.168.1.134 Host 134.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN) Elesar:/etc # The IP is dynamic. I could just write numbered entries for the dhcp range, of course. No way to sync with the dhcp server at the router, obviously. Not expensive enough for such a feature (unless there is someway I don't know about).
A machine will always only have one name, but may be reached by multiple other names.
Ok.
I don't think it would be right for our network config to assume the presence of a local DNS. Maybe the question ought to be "with no local DNS, why do you need a local domain name?"
Completeness? :-) I don't see why I would not need a domain name, though? I had always one. Ah, yes: tools like postfix or leafnode demand it. Specifically leafnode insists on fqdn working.
But then I would ask: "what was then the purpose of the missing domain name entry box that previous yast versions had? If it was not to set the domain name of the machine, then what was its purpose?" It has been there for decades.
It's a moot point now, but looking at some of my elderly machines, the domain name was written to /etc/HOSTNAME - I see e.g. "linux.suse" or "linux-0ya0.site" on some of them.
Right, that is what I do. however, Dr. Werner Fink said in this thread yesterday: ]> Nota Bene: the usage of the domain part of a FQDN in /etc/hostname is ]> plain wrong -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 09.06, Per Jessen wrote:
+++............ Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y Elesar:~ # hostname -A Elesar:~ # hostname Elesar Elesar:~ #
Okay, my mistake, I didn't take that to be all there is. FWIW, I see no such issue here. (different situation though, working dns).
I have a working local dns, with dnsmaq in another computer. But I have a dns in the LAN, just not in this machine.
But it is not being updated when your dhcp dishes out addresses, I presume. If it were me, I think I would put an 'nsupdate' call in my NetworkManager or wicked scripts/hooks.
Maybe the answer is "you can not set the domain name of the machine. You have to set it up in the DNS. The query about your own IP answers the fqdn". But that answer does not consider multiple domains, so... :-?
Ah, I remember: the local dns has no answer for my IP.
Yes, that would certainly explain your situation.
The IP is dynamic. I could just write numbered entries for the dhcp range, of course. No way to sync with the dhcp server at the router, obviously. Not expensive enough for such a feature (unless there is someway I don't know about).
It _might_ just have such ddns options, but I wouldn't bet on it either. Anyway, use nsupdate.
I don't think it would be right for our network config to assume the presence of a local DNS. Maybe the question ought to be "with no local DNS, why do you need a local domain name?"
Completeness? :-)
I don't see why I would not need a domain name, though? I had always one. Ah, yes: tools like postfix or leafnode demand it. Specifically leafnode insists on fqdn working.
It probably depends on what you do with postfix, but for the default setup, that would mean everyone here having the same issue, starting with 15.0. I don't know anything about leafnode, for fetching newsgroups from an external server, it probably makes sense to have an fqdn (even it's private). -- Per Jessen, Zürich (12.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 13.07, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 09.06, Per Jessen wrote:
+++............ Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y Elesar:~ # hostname -A Elesar:~ # hostname Elesar Elesar:~ #
Okay, my mistake, I didn't take that to be all there is. FWIW, I see no such issue here. (different situation though, working dns).
I have a working local dns, with dnsmaq in another computer. But I have a dns in the LAN, just not in this machine.
But it is not being updated when your dhcp dishes out addresses, I presume.
Correct.
If it were me, I think I would put an 'nsupdate' call in my NetworkManager or wicked scripts/hooks.
Ok, I can look into that. This setup is using wicked. Any RTFM guide for dummies about wicked hooks? :-)
Maybe the answer is "you can not set the domain name of the machine. You have to set it up in the DNS. The query about your own IP answers the fqdn". But that answer does not consider multiple domains, so... :-?
Ah, I remember: the local dns has no answer for my IP.
Yes, that would certainly explain your situation.
The IP is dynamic. I could just write numbered entries for the dhcp range, of course. No way to sync with the dhcp server at the router, obviously. Not expensive enough for such a feature (unless there is someway I don't know about).
It _might_ just have such ddns options, but I wouldn't bet on it either.
For the external IP only. DynDNS.org, TZO, or No-IP, not any other. Certainly not "write your own".
Anyway, use nsupdate.
I'll have a look. [...] I have a doubt this can work with dnsmasq? It is not a full fledged DNS server. [...] Google says it is not possible. Google dnsmasq and nsupdate domain name system - Pull DNS entries from Dnsmasq to other DNS ... https://serverfault.com/.../pull-dns-entries-from-dnsmasq-to-other-... 25 jul. 2018 - Use this script to do an nsupdate on the main DNS server. The main server can't be dnsmasq because dnsmasq doesn't support this kind of ... http://lightofdawn.org/wiki/wiki.cgi/-wiki/LocalDynamicDns They use netcat to drop a file into a directory that dnsmasq reads with the entry for "this" machine, and then tell dnsmaq to reload. Seems a hack. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 13.07, Per Jessen wrote:
If it were me, I think I would put an 'nsupdate' call in my NetworkManager or wicked scripts/hooks.
Ok, I can look into that. This setup is using wicked. Any RTFM guide for dummies about wicked hooks? :-)
It's very much what it has been for years - put a script in /etc/sysconfig/netwoirk/if-{up,down}.d/
Anyway, use nsupdate.
I'll have a look. [...] I have a doubt this can work with dnsmasq? It is not a full fledged DNS server. [...] Google says it is not possible.
Oh, that's a pity. Seems like something obvious for dnsmasq to support. Well then, back to plain old bind :-) -- Per Jessen, Zürich (11.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 13.36, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.07, Per Jessen wrote:
If it were me, I think I would put an 'nsupdate' call in my NetworkManager or wicked scripts/hooks.
Ok, I can look into that. This setup is using wicked. Any RTFM guide for dummies about wicked hooks? :-)
It's very much what it has been for years - put a script in /etc/sysconfig/netwoirk/if-{up,down}.d/
Ah. But I have never tried with wicked, only with NM. Wicked is relatively "new".
Anyway, use nsupdate.
I'll have a look. [...] I have a doubt this can work with dnsmasq? It is not a full fledged DNS server. [...] Google says it is not possible.
Oh, that's a pity. Seems like something obvious for dnsmasq to support. Well then, back to plain old bind :-)
Nonono. I'm not going back to bind, that's another can of worms :-) The main partition in this machine does have a working bind. But the LAN server uses dnsmasq and I'm otherwise very happy with it. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 13.36, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.07, Per Jessen wrote:
If it were me, I think I would put an 'nsupdate' call in my NetworkManager or wicked scripts/hooks.
Ok, I can look into that. This setup is using wicked. Any RTFM guide for dummies about wicked hooks? :-)
It's very much what it has been for years - put a script in /etc/sysconfig/netwoirk/if-{up,down}.d/
Ah. But I have never tried with wicked, only with NM. Wicked is relatively "new".
The mechanisms haven't changed though - /etc/sysconfig/network/if-{up,down}.d/ Same as in 10.3. -- Per Jessen, Zürich (11.5°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 15.32, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.36, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.07, Per Jessen wrote:
If it were me, I think I would put an 'nsupdate' call in my NetworkManager or wicked scripts/hooks.
Ok, I can look into that. This setup is using wicked. Any RTFM guide for dummies about wicked hooks? :-)
It's very much what it has been for years - put a script in /etc/sysconfig/netwoirk/if-{up,down}.d/
Ah. But I have never tried with wicked, only with NM. Wicked is relatively "new".
The mechanisms haven't changed though -
/etc/sysconfig/network/if-{up,down}.d/
Same as in 10.3.
It will have a syntax. The script will get parameters on the command line and environment, which I need. What is the man page? It is not "man wicked" -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 15.32, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.36, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 13.07, Per Jessen wrote:
If it were me, I think I would put an 'nsupdate' call in my NetworkManager or wicked scripts/hooks.
Ok, I can look into that. This setup is using wicked. Any RTFM guide for dummies about wicked hooks? :-)
It's very much what it has been for years - put a script in /etc/sysconfig/netwoirk/if-{up,down}.d/
Ah. But I have never tried with wicked, only with NM. Wicked is relatively "new".
The mechanisms haven't changed though -
/etc/sysconfig/network/if-{up,down}.d/
Same as in 10.3.
It will have a syntax.
Whatever shell you choose to execute it with. (hash-bang)
The script will get parameters on the command line and environment, which I need. What is the man page? It is not "man wicked"
Dunno - put a script in and dump the environment and the arguments. If you google it, you'll probably find the information too. -- Per Jessen, Zürich (9.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 20.14, Per Jessen wrote:
Carlos E. R. wrote:
...
The mechanisms haven't changed though -
/etc/sysconfig/network/if-{up,down}.d/
Same as in 10.3.
It will have a syntax.
Whatever shell you choose to execute it with. (hash-bang)
Yeah, of course. I did not mean that :-) Language issue.
The script will get parameters on the command line and environment, which I need. What is the man page? It is not "man wicked"
Dunno - put a script in and dump the environment and the arguments. If you google it, you'll probably find the information too.
Oh, I hoped you knew. Ok, one item more to my to-do list. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [05-08-19 14:31]:
On 08/05/2019 20.14, Per Jessen wrote:
Carlos E. R. wrote:
...
The mechanisms haven't changed though -
/etc/sysconfig/network/if-{up,down}.d/
Same as in 10.3.
It will have a syntax.
Whatever shell you choose to execute it with. (hash-bang)
Yeah, of course. I did not mean that :-) Language issue.
The script will get parameters on the command line and environment, which I need. What is the man page? It is not "man wicked"
Dunno - put a script in and dump the environment and the arguments. If you google it, you'll probably find the information too.
Oh, I hoped you knew. Ok, one item more to my to-do list.
man wickedd ?? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/05/2019 01.45, Patrick Shanahan wrote:
* Carlos E. R. <> [05-08-19 14:31]:
On 08/05/2019 20.14, Per Jessen wrote:
Carlos E. R. wrote:
The script will get parameters on the command line and environment, which I need. What is the man page? It is not "man wicked"
Dunno - put a script in and dump the environment and the arguments. If you google it, you'll probably find the information too.
Oh, I hoped you knew. Ok, one item more to my to-do list.
man wickedd ??
Unfortunately, no. I did apropos wicked and nothing seemed appropriate, but maybe I missed something, I only had a quick look and search. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 9 May 2019 02:10:46 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 09/05/2019 01.45, Patrick Shanahan wrote:
* Carlos E. R. <> [05-08-19 14:31]:
On 08/05/2019 20.14, Per Jessen wrote:
Carlos E. R. wrote:
The script will get parameters on the command line and environment, which I need. What is the man page? It is not "man wicked"
Dunno - put a script in and dump the environment and the arguments. If you google it, you'll probably find the information too.
Oh, I hoped you knew. Ok, one item more to my to-do list.
man wickedd ??
Unfortunately, no. I did apropos wicked and nothing seemed appropriate, but maybe I missed something, I only had a quick look and search.
Maybe these: https://en.opensuse.org/Portal:Wicked https://github.com/openSUSE/wicked and in particular https://github.com/openSUSE/wicked/blob/master/doc/WhyWicked.txt https://github.com/openSUSE/wicked/tree/master/man or indeed man wickedd on the command line rather than on the web? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/05/2019 02.23, Dave Howorth wrote:
On Thu, 9 May 2019 02:10:46 +0200 "Carlos E. R." <> wrote:
On 09/05/2019 01.45, Patrick Shanahan wrote:
* Carlos E. R. <> [05-08-19 14:31]:
On 08/05/2019 20.14, Per Jessen wrote:
Carlos E. R. wrote:
The script will get parameters on the command line and environment, which I need. What is the man page? It is not "man wicked"
Dunno - put a script in and dump the environment and the arguments. If you google it, you'll probably find the information too.
Oh, I hoped you knew. Ok, one item more to my to-do list.
man wickedd ??
Unfortunately, no. I did apropos wicked and nothing seemed appropriate, but maybe I missed something, I only had a quick look and search.
Maybe these:
No...
Not that I see.
and in particular
https://github.com/openSUSE/wicked/blob/master/doc/WhyWicked.txt
No, because it says: +++........... Trigger Scripts =============== These hooks don't exist yet, but will be implemented soonishly. ...........++- So either the file is obsolete or still not implemented.
Maybe. Here there are manuals that I did not locate because they don't have "wicked" in the name. But I don't see one about "trigger" or some other obvious name.
or indeed man wickedd on the command line rather than on the web?
Man wickedd doesn't mention if-up/dn scripts. But thanks, you found things :-D -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 9 May 2019 09:23:17 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
But thanks, you found things :-D
Probably time to ask on the wicked-devel list then... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/05/2019 09.58, Dave Howorth wrote:
On Thu, 9 May 2019 09:23:17 +0200 "Carlos E. R." <> wrote:
But thanks, you found things :-D
Probably time to ask on the wicked-devel list then...
Not yet, I still have to search a bit more :-) -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On Tue, 7 May 2019 23:50:08 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
Where is one supposed to write the domain name?
That would leave me very confused.
This thread must be one of the longest in history. I have very little idea of the issues involved. Do any of the participants feel that they understand the issues? In no particular order (INPO):Carlos, Per, Andrei, Patrick, James, Anton, Gertjan, Robert Is anybody aware of whether there is accurate documentation for 15.1? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
On Tue, 7 May 2019 23:50:08 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
Where is one supposed to write the domain name?
That would leave me very confused.
This thread must be one of the longest in history.
I have very little idea of the issues involved.
Do any of the participants feel that they understand the issues? In no particular order (INPO):Carlos, Per, Andrei, Patrick, James, Anton, Gertjan, Robert
Permit me to make a wild guess - The issue is the removal of the entry field for a domain name in the YaST network configuration. We have yet to determine why or if that is actually a problem. (I think). -- Per Jessen, Zürich (12.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, May 8, 2019 at 2:18 PM Per Jessen <per@computer.org> wrote:
The issue is the removal of the entry field for a domain name in the YaST network configuration. We have yet to determine why
https://lists.opensuse.org/opensuse/2019-05/msg00300.html
or if that is actually a problem. (I think).
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 07:18 AM, Per Jessen wrote:
Permit me to make a wild guess -
The issue is the removal of the entry field for a domain name in the YaST network configuration. We have yet to determine why or if that is actually a problem. (I think).
The result of not having the domain name somewhere in resolv.conf means you can't use just a host name to reach another device. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 05/08/2019 07:18 AM, Per Jessen wrote:
Permit me to make a wild guess -
The issue is the removal of the entry field for a domain name in the YaST network configuration. We have yet to determine why or if that is actually a problem. (I think).
The result of not having the domain name somewhere in resolv.conf means you can't use just a host name to reach another device.
Right. Whether it is in "domain' or "search". At least it ought to go in the release notes. -- Per Jessen, Zürich (10.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 20.09, Per Jessen wrote:
James Knott wrote:
On 05/08/2019 07:18 AM, Per Jessen wrote:
Permit me to make a wild guess -
The issue is the removal of the entry field for a domain name in the YaST network configuration. We have yet to determine why or if that is actually a problem. (I think).
The result of not having the domain name somewhere in resolv.conf means you can't use just a host name to reach another device.
Right. Whether it is in "domain' or "search".
At least it ought to go in the release notes.
YaST could add a domain entry in there saying that it simply goes to the resolv file, nothing else. And put it near the "search" input box, not above. Writing it ourselves in the resolv file means that the automatic writing of the file is disabled. Somewhere else we can add the "domain" entry? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 20.09, Per Jessen wrote:
James Knott wrote:
On 05/08/2019 07:18 AM, Per Jessen wrote:
Permit me to make a wild guess -
The issue is the removal of the entry field for a domain name in the YaST network configuration. We have yet to determine why or if that is actually a problem. (I think).
The result of not having the domain name somewhere in resolv.conf means you can't use just a host name to reach another device.
Right. Whether it is in "domain' or "search".
At least it ought to go in the release notes.
YaST could add a domain entry in there saying that it simply goes to the resolv file, nothing else. And put it near the "search" input box, not above.
Writing it ourselves in the resolv file means that the automatic writing of the file is disabled. Somewhere else we can add the "domain" entry?
Yes, just add it as a search domain. That is essentially the same function as using "domain". -- Per Jessen, Zürich (9.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 02:37 PM, Per Jessen wrote:
Writing it ourselves in the resolv file means that the automatic writing of the file is disabled. Somewhere else we can add the "domain" entry? Yes, just add it as a search domain. That is essentially the same function as using "domain".
Other than the differences listed in the man page. I don't know if anything makes a distinction between the domain and search parts of resolv.conf. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 20.37, Per Jessen wrote:
Carlos E. R. wrote:
Right. Whether it is in "domain' or "search".
At least it ought to go in the release notes.
YaST could add a domain entry in there saying that it simply goes to the resolv file, nothing else. And put it near the "search" input box, not above.
Writing it ourselves in the resolv file means that the automatic writing of the file is disabled. Somewhere else we can add the "domain" entry?
Yes, just add it as a search domain. That is essentially the same function as using "domain".
Not really... :-? domain Local domain name. Most queries for names within this domain can use short names relative to the local domain. If set to '.', the root domain is considered. If no domain entry is present, the domain is determined from the local hostname returned by gethostname(2); the domain part is taken to be everything after the first '.'. Finally, if the hostname does not contain a domain part, the root domain is assumed. search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names. Resolver queries having fewer than ndots dots (default is 1) in them will be attempted using each component of the search path in turn until a match is found. For environments with multiple subdomains please read options ndots:n below to avoid man-in-the-middle attacks and unnecessary traffic for the root-dnsservers. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains. The search list is currently limited to six domains with a total of 256 characters. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 20.37, Per Jessen wrote:
Carlos E. R. wrote:
Right. Whether it is in "domain' or "search".
At least it ought to go in the release notes.
YaST could add a domain entry in there saying that it simply goes to the resolv file, nothing else. And put it near the "search" input box, not above.
Writing it ourselves in the resolv file means that the automatic writing of the file is disabled. Somewhere else we can add the "domain" entry?
Yes, just add it as a search domain. That is essentially the same function as using "domain".
Not really... :-?
Yes really. Why don't you try it? None of my systems use that domain option in resolv.conf and after changing the domain-name option in dhcpd.conf to "gobble.degook", the eagerly awaited havoc has yet to show. -- Per Jessen, Zürich (8.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 21.00, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 20.37, Per Jessen wrote:
Carlos E. R. wrote:
Right. Whether it is in "domain' or "search".
At least it ought to go in the release notes.
YaST could add a domain entry in there saying that it simply goes to the resolv file, nothing else. And put it near the "search" input box, not above.
Writing it ourselves in the resolv file means that the automatic writing of the file is disabled. Somewhere else we can add the "domain" entry?
Yes, just add it as a search domain. That is essentially the same function as using "domain".
Not really... :-?
Yes really. Why don't you try it? None of my systems use that domain option in resolv.conf and after changing the domain-name option in dhcpd.conf to "gobble.degook", the eagerly awaited havoc has yet to show.
I have changed two resolv.conf from using search to using domain, I see it as more useful. And I have found that the key to having fqdn is /etc/hosts with the correct current IP - which is a problem if it is dynamic. As to the domain change in dhcp, it is possible that the option to take that name when configuring network is disabled. It is disabled by default in YaST. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 08/05/2019 21.00, Per Jessen wrote:
Carlos E. R. wrote:
On 08/05/2019 20.37, Per Jessen wrote:
Carlos E. R. wrote:
Right. Whether it is in "domain' or "search".
At least it ought to go in the release notes.
YaST could add a domain entry in there saying that it simply goes to the resolv file, nothing else. And put it near the "search" input box, not above.
Writing it ourselves in the resolv file means that the automatic writing of the file is disabled. Somewhere else we can add the "domain" entry?
Yes, just add it as a search domain. That is essentially the same function as using "domain".
Not really... :-?
Yes really. Why don't you try it? None of my systems use that domain option in resolv.conf and after changing the domain-name option in dhcpd.conf to "gobble.degook", the eagerly awaited havoc has yet to show.
I have changed two resolv.conf from using search to using domain, I see it as more useful.
Please elaborate - exactly what difference does it make? If I am missing out, I"d like to know what I am missing.
As to the domain change in dhcp, it is possible that the option to take that name when configuring network is disabled.
See what I posted from the ISC man page earlier. It is simply not an option, just text. -- Per Jessen, Zürich (8.5°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 03:44 PM, Per Jessen wrote:
As to the domain change in dhcp, it is possible that the option to take that name when configuring network is disabled. See what I posted from the ISC man page earlier. It is simply not an option, just text.
The only difference I can think of is where something needs the domain name and looks for the domain in resolv.conf. It would not be wanting to use the additional domains listed in search. For just host name lookup either domain or search works fine. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 21.44, Per Jessen wrote:
Carlos E. R. wrote:
...
I have changed two resolv.conf from using search to using domain, I see it as more useful.
Please elaborate - exactly what difference does it make? If I am missing out, I"d like to know what I am missing.
With "search", I had instances in the past that the short name does not work.
From what I understand from what I read, "search" acts first reading "domain" line, then adds whatever it reads from "search".
As to the domain change in dhcp, it is possible that the option to take that name when configuring network is disabled.
See what I posted from the ISC man page earlier. It is simply not an option, just text.
No, I mean here, in YaST: YaST2 - lan @ Elesar Network Settings ┌Global Options──Overview──Hostname/DNS──Routing──────────────┐ │Hostname │ │Elesar▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │Set Hostname via DHCP no▒▒▒▒▒▒▒▒▒↓ │ │ │ ********** Although that's the name, I have no idea about the domain. Maybe it reads both if it reads anything. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
08.05.2019 23:25, Carlos E. R. пишет:
On 08/05/2019 21.44, Per Jessen wrote:
Carlos E. R. wrote:
...
I have changed two resolv.conf from using search to using domain, I see it as more useful.
Please elaborate - exactly what difference does it make? If I am missing out, I"d like to know what I am missing.
With "search", I had instances in the past that the short name does not work.
From what I understand from what I read, "search" acts first reading "domain" line, then adds whatever it reads from "search".
"domain" and "search" are mutually exclusive. This is even documented in manual page that you so copiously quoted. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 22.31, Andrei Borzenkov wrote:
08.05.2019 23:25, Carlos E. R. пишет:
On 08/05/2019 21.44, Per Jessen wrote:
Carlos E. R. wrote:
...
I have changed two resolv.conf from using search to using domain, I see it as more useful.
Please elaborate - exactly what difference does it make? If I am missing out, I"d like to know what I am missing.
With "search", I had instances in the past that the short name does not work.
From what I understand from what I read, "search" acts first reading "domain" line, then adds whatever it reads from "search".
"domain" and "search" are mutually exclusive. This is even documented in manual page that you so copiously quoted.
Sorry, I do not see it :-? Actually, I understand the contrary. search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it contains only the local domain name. So I understand that "search" first reads "domain". I wrote now: ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf. domain valinor search home nameserver 192.168.1.16 nameserver 80.58.61.250 nameserver 80.58.61.254 Elesar:~ # host router router has address 192.168.1.1 Elesar:~ # host router2 router2.home has address 192.168.2.1 Elesar:~ # It is working... I see no warning in the log. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 04:47 PM, Carlos E. R. wrote:
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
I just did that and now my domain name appears in the box, even though it's listed under search in resolv.conf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 03:00 PM, Per Jessen wrote:
None of my systems use that domain option in resolv.conf and after changing the domain-name option in dhcpd.conf to "gobble.degook", the eagerly awaited havoc has yet to sh #%##%#^#$%%
NO CARRIER ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 05/08/2019 03:00 PM, Per Jessen wrote:
None of my systems use that domain option in resolv.conf and after changing the domain-name option in dhcpd.conf to "gobble.degook", the eagerly awaited havoc has yet to sh #%##%#^#$%%
NO CARRIER
;-)
Haha, nice one James! -- Per Jessen, Zürich (8.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 04:55 PM, Per Jessen wrote:
You are basically saying "nowhere". I think Andrei is saying it isn't necessary and asks you to show which problem it creates for you.
The problem is without a domain name specified somewhere you cannot connect to something via hostname alone. You need the FQDN. I showed that in an earlier message where I removed the domain name from resolv.conf and could no longer ping with just the host name. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 05/06/2019 04:55 PM, Per Jessen wrote:
You are basically saying "nowhere". I think Andrei is saying it isn't necessary and asks you to show which problem it creates for you.
The problem is without a domain name specified somewhere you cannot connect to something via hostname alone. You need the FQDN.
Well, not really. I added the following line to /etc/hosts on my leap151 test machine: 2001:db8:4f8:a0:1312::1 jamesknott Then I tried 'ssh jamesknott' - # ssh -p17022 jamesknott The authenticity of host '[jamesknott]:17022 ([2001:db8:a0:1312::1]:17022)' can't be established. RSA key fingerprint is SHA256:EvJa9yGU+MELbbRAv9jaFmh/BB7Oq/mNcL6AcyKaavE. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[jamesknott]:17022 [2001:db8:a0:1312::1]:17022' (RSA) to the list of known hosts. Password: Last login: Tue May 7 07:52:47 2019 from 2001:db8:4c68:1:221:86ff:fe4f:8ac4 Have a lot of fun... I don't understand all this talk - surely the problem is easily reproduced? Maybe I'll try installing from a USB stick, without network. (with network, all the config is provided by dhcp). -- Per Jessen, Zürich (6.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 02:43 AM, Per Jessen wrote:
Well, not really. I added the following line to /etc/hosts on my leap151 test machine:
2001:db8:4f8:a0:1312::1 jamesknott
Then I tried 'ssh jamesknott' -
I thought the purpose of DNS was to eliminate the need for updating the hosts file. Prior to DNS, someone had to maintain a hosts file that was distributed to others and used to replace the old hosts file. Do you really want to go back to the dark ages? I can add host names to my hosts file all I want. Will that help someone at another computer? My test yesterday proved no. Also, here's some info from my hosts file: "# hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server." This indicates the hosts file is not normally used, once a computer has finished booting. I don't see any mention that it should be used because Yast is busted. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 05/07/2019 02:43 AM, Per Jessen wrote:
Well, not really. I added the following line to /etc/hosts on my leap151 test machine:
2001:db8:4f8:a0:1312::1 jamesknott
Then I tried 'ssh jamesknott' -
I thought the purpose of DNS was to eliminate the need for updating the hosts file.
Or - the purpose of /etc/hosts is to enable name resolution when you have no DNS ?
Prior to DNS, someone had to maintain a hosts file that was distributed to others and used to replace the old hosts file. Do you really want to go back to the dark ages?
I was suggesting no such thing - however, that is the situation for some people.
Also, here's some info from my hosts file:
"# hosts This file describes a number of hostname-to-address #mappings for the TCP/IP subsystem. It is mostly #used at boot time, when no name servers are running. #On small systems, this file can be used instead of a #"named" name server."
This indicates the hosts file is not normally used, once a computer has finished booting.
The resolver uses the hosts file if directed to do so, via nsswitch.conf. -- Per Jessen, Zürich (13.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 15.56, Per Jessen wrote:
James Knott wrote:
On 05/07/2019 02:43 AM, Per Jessen wrote:
Well, not really. I added the following line to /etc/hosts on my leap151 test machine:
2001:db8:4f8:a0:1312::1 jamesknott
Then I tried 'ssh jamesknott' -
I thought the purpose of DNS was to eliminate the need for updating the hosts file.
Or - the purpose of /etc/hosts is to enable name resolution when you have no DNS ?
Prior to DNS, someone had to maintain a hosts file that was distributed to others and used to replace the old hosts file. Do you really want to go back to the dark ages?
I was suggesting no such thing - however, that is the situation for some people.
Also, here's some info from my hosts file:
"# hosts This file describes a number of hostname-to-address #mappings for the TCP/IP subsystem. It is mostly #used at boot time, when no name servers are running. #On small systems, this file can be used instead of a #"named" name server."
This indicates the hosts file is not normally used, once a computer has finished booting.
The resolver uses the hosts file if directed to do so, via nsswitch.conf.
And if you have dnsmasq running, it uses the /etc/hosts file for config. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On 2019-05-07 5:52 p.m., Carlos E. R. wrote:
And if you have dnsmasq running, it uses the /etc/hosts file for config.
NOT! It uses /etc/dnsmasq.conf for CONFIG It uses /etc/hosts for DATA. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 23.55, Anton Aylward wrote:
On 2019-05-07 5:52 p.m., Carlos E. R. wrote:
And if you have dnsmasq running, it uses the /etc/hosts file for config.
NOT!
It uses /etc/dnsmasq.conf for CONFIG It uses /etc/hosts for DATA.
Ok, ok :-DD -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere". Yes, you are barking up the wrong tree. You, on 15.1, also have YaST > Network Services > Hostnames. Set as many as you want. It will add the hostname/domain in /etc/hosts. This is what we call an improvement. The old network module only provided one hostname/search domain. With this module you have the tool
Op maandag 6 mei 2019 22:43:47 CEST schreef Carlos E. R.: that allows you to have multiple hostnames / domains on the same IP. But .... you decided to hack NM because you insist on having a dynamic IP address for services that should have a static or fixed DHCP address. IMNSHO The YaST team did a very nice and good job removing the domain stuff from the Network Settings. My 2 cents. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-05-06 04:16 PM, Knurpht-openSUSE wrote:
Op maandag 6 mei 2019 22:43:47 CEST schreef Carlos E. R.:
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST. I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere". Yes, you are barking up the wrong tree. You, on 15.1, also have YaST > Network Services > Hostnames. Set as many as you want. It will add the hostname/domain That assigns a name to an IP, not to an interface or machine. I believe Carlos wants to give each machine a name, then obtain its IP by DHCP.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 7 mei 2019 00:34:01 CEST schreef Darryl Gregorash:
On 2019-05-06 04:16 PM, Knurpht-openSUSE wrote:
Op maandag 6 mei 2019 22:43:47 CEST schreef Carlos E. R.:
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
Yes, you are barking up the wrong tree. You, on 15.1, also have YaST > Network Services > Hostnames. Set as many as you want. It will add the hostname/domain That assigns a name to an IP, not to an interface or machine. I believe Carlos wants to give each machine a name, then obtain its IP by DHCP. If set properly in the hosts file, also hostname -f works as expexted. See knurpht@salt:~> hostname salt knurpht@salt:~> hostname -f salt.knurpht.nl knurpht@salt:~> cat /etc/resolv.conf | grep search search knurpht.nl knurpht@salt:~>
Just to mention: On this machine I have a dozen of domains and a plethora of subdomains. No FQDN or DNS issues at all. Carlos could even add the entire scope of DHCP addresses for the same domainname, it would still work. And AFAIK that is what Carlos wants. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 7 mei 2019 00:34:01 CEST schreef Darryl Gregorash:
On 2019-05-06 04:16 PM, Knurpht-openSUSE wrote:
Yes, you are barking up the wrong tree. You, on 15.1, also have YaST > Network Services > Hostnames. Set as many as you want. It will add the hostname/domain That assigns a name to an IP, not to an interface or machine. I believe Carlos wants to give each machine a name, then obtain its IP by DHCP. If set properly in the hosts file, also hostname -f works as expexted. See Correct; however, it seems to be impossible to set that using YaST. Are we seeing a return to the days when, if you wanted to change some system
On 2019-05-06 04:44 PM, Knurpht-openSUSE wrote: parameter, you had to edit a text file manually? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 7 mei 2019 01:53:45 CEST schreef Darryl Gregorash:
On 2019-05-06 04:44 PM, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 00:34:01 CEST schreef Darryl Gregorash:
On 2019-05-06 04:16 PM, Knurpht-openSUSE wrote:
Yes, you are barking up the wrong tree. You, on 15.1, also have YaST > Network Services > Hostnames. Set as many as you want. It will add the hostname/domain That assigns a name to an IP, not to an interface or machine. I believe Carlos wants to give each machine a name, then obtain its IP by DHCP.
If set properly in the hosts file, also hostname -f works as expexted. See
Correct; however, it seems to be impossible to set that using YaST. Are we seeing a return to the days when, if you wanted to change some system parameter, you had to edit a text file manually? As I was saying, it sets that in the /etc/hosts file. Using YaST > Network Services > Hostnames. Why insist on working on on something that does not work, instead of doing it incl. YaST usage in a way that does work. Things change.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-05-06 06:21 PM, Knurpht-openSUSE wrote:
As I was saying, it sets that in the /etc/hosts file. Using YaST > Network Services > Hostnames. Why insist on working on on something that does not work, instead of doing it incl. YaST usage in a way that does work. Things change.
Because Carlos wants to give each machine a fixed hostname, and assign its IP by DHCP! That should be possible to do without editing a text file by hand. Things like this are what YaST was designed to do, are they not? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 7 mei 2019 03:46:30 CEST schreef Darryl Gregorash:
On 2019-05-06 06:21 PM, Knurpht-openSUSE wrote:
As I was saying, it sets that in the /etc/hosts file. Using YaST > Network Services > Hostnames. Why insist on working on on something that does not work, instead of doing it incl. YaST usage in a way that does work. Things change.
Because Carlos wants to give each machine a fixed hostname, and assign its IP by DHCP! That should be possible to do without editing a text file by hand. Things like this are what YaST was designed to do, are they not? Yes, but like said, things change. I have a cheap > 12 year old router that can bind/reserve a fixed IP address to a machine's ethernet interface ( IIRC on mac address ). Why does it have to be a variable IP address? Even in my UNIX days ( 1990s, AT&T UNIX System V ) I was tought that a reliable server should have the same IP address all the time and not rely on a DHCP pool. I simply don't get the reasoning behind the desire not doing it like that. Specially not since that leads to working situation. I admit not knowing the details about the YaST changes, but I did manage to get a working environment, with ( FYI ) a local DNS server ( pihole ). YaST is not designed to last forever in the same way it started. Networking hasn't. Honestly, I don't see the point.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 10:17 PM, Knurpht-openSUSE wrote:
Honestly, I don't see the point.
Isn't there a DHCP function where the host supplies it's own host name, which then gets passed to a DNS server, along with the IP address? That is precisely where this would be needed. However, my own question was about the domain name. If the domain name isn't specified in resolv.conf a host cannot reach another using only the host name. A FQDN would be needed. So, yes, I consider this a fault, not a feature. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 05/06/2019 10:17 PM, Knurpht-openSUSE wrote:
Honestly, I don't see the point.
Isn't there a DHCP function where the host supplies it's own host name, which then gets passed to a DNS server, along with the IP address? That is precisely where this would be needed.
Yes, dynamic updates.
However, my own question was about the domain name. If the domain name isn't specified in resolv.conf a host cannot reach another using only the host name. A FQDN would be needed. So, yes, I consider this a fault, not a feature.
I guess YaST would previously have added the <domain name> specified as a 'search' option to resolv.conf by default? -- Per Jessen, Zürich (5.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 02:19 AM, Per Jessen wrote:
I guess YaST would previously have added the <domain name> specified as a 'search' option to resolv.conf by default?
It used to have a domain line. When you saved the domain name in that box in Yast, it added the domain line to resolv.conf. That still works for search domains, but not domain name. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 05/07/2019 02:19 AM, Per Jessen wrote:
I guess YaST would previously have added the <domain name> specified as a 'search' option to resolv.conf by default?
It used to have a domain line. When you saved the domain name in that box in Yast, it added the domain line to resolv.conf. That still works for search domains, but not domain name.
According to the man page, the 'domain' option is still there, but I'm not sure how it differs from the search ditto. -- Per Jessen, Zürich (13.7°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 09:52 AM, Per Jessen wrote:
According to the man page, the 'domain' option is still there, but I'm not sure how it differs from the search ditto.
According to the man page, the local domain is supposed to be listed as such. Any additional domains are to be listed in search section. While putting the domain in the Search Domains works, in 15.0, there is a box for the domain name, but it doesn't work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
07.05.2019 17:42, James Knott пишет:
On 05/07/2019 09:52 AM, Per Jessen wrote:
According to the man page, the 'domain' option is still there, but I'm not sure how it differs from the search ditto.
It does not.
According to the man page, the local domain is supposed to be listed as such.
There is no such thing as "local domain" at all. Host does not have any domain.
Any additional domains are to be listed in search section. While putting the domain in the Search Domains works, in 15.0, there is a box for the domain name, but it doesn't work.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 02:15 PM, Andrei Borzenkov wrote:
07.05.2019 17:42, James Knott пишет:
On 05/07/2019 09:52 AM, Per Jessen wrote:
According to the man page, the 'domain' option is still there, but I'm not sure how it differs from the search ditto. It does not.
According to the man page, the local domain is supposed to be listed as such. There is no such thing as "local domain" at all. Host does not have any domain.
From the resolv.conf man page:
domain Local domain name. Most queries for names within this domain can use short names relative to the local domain. If set to '.', the root domain is considered. If no domain entry is present, the domain is determined from the local hostname returned by gethostname(2); the domain part is taken to be everything after the first '.'. Finally, if the hostname does not contain a domain part, the root domain is assumed. That sure looks to me like local domain. Then on search domains, we have: search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names. Yep, there's supposed to be a local domain name. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 05/07/2019 02:15 PM, Andrei Borzenkov wrote:
07.05.2019 17:42, James Knott пишет:
On 05/07/2019 09:52 AM, Per Jessen wrote:
According to the man page, the 'domain' option is still there, but I'm not sure how it differs from the search ditto. It does not.
According to the man page, the local domain is supposed to be listed as such. There is no such thing as "local domain" at all. Host does not have any domain.
From the resolv.conf man page:
domain Local domain name. Most queries for names within this domain can use short names relative to the local domain. If set to '.', the root domain is considered. If no domain entry is present, the domain is determined from the local hostname returned by gethostname(2); the domain part is taken to be everything after the first '.'. Finally, if the hostname does not contain a domain part, the root domain is assumed.
That sure looks to me like local domain. Then on search domains, we have:
search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names.
Yep, there's supposed to be a local domain name.
Maybe that man page was supposed to have been updated long ago. I have no 'domain' statement in any resolv.conf, anywhere. I wonder if there is even a dhcp option for setting it. (if it's important, there ought to be one). -- Per Jessen, Zürich (11.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 02:35 PM, Per Jessen wrote:
Yep, there's supposed to be a local domain name. Maybe that man page was supposed to have been updated long ago. I have no 'domain' statement in any resolv.conf, anywhere. I wonder if there is even a dhcp option for setting it. (if it's important, there ought to be one).
Perhaps not on recent versions of openSUSE. Fire up an older version and look. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 05/07/2019 02:35 PM, Per Jessen wrote:
Yep, there's supposed to be a local domain name. Maybe that man page was supposed to have been updated long ago. I have no 'domain' statement in any resolv.conf, anywhere. I wonder if there is even a dhcp option for setting it. (if it's important, there ought to be one).
Perhaps not on recent versions of openSUSE. Fire up an older version and look.
Oh, I have a few older ones running, going back to 10.3 - no such entry in /etc/resolv.conf. office64 - 10.3 - nothing redwood - 11.4 - nothing thorium - 11.0 - nothing calcium - 13.2 - nothing office20 - 13.2 - nothing. I can look up some more, but given what the ISC says about that option (see previous post), I don't see why it would be used for anything. Anyway, I've removed it from the ipv4 dhcp config, maybe local name resolving will start collapsing soon. -- Per Jessen, Zürich (9.4°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I can look up some more, but given what the ISC says about that option (see previous post), I don't see why it would be used for anything.
Anyway, I've removed it from the ipv4 dhcp config, maybe local name resolving will start collapsing soon.
Better yet - I have added this to /etc/dhcpd.conf : option domain-name "gobble.degook"; I would expect to see some havoc in the course of today. -- Per Jessen, Zürich (9.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-05-07 12:35 PM, Per Jessen wrote:
Maybe that man page was supposed to have been updated long ago. I have no 'domain' statement in any resolv.conf, anywhere. I wonder if there is even a dhcp option for setting it. (if it's important, there ought to be one).
There is a DHCP option; without it, I would not have a FQDN at all. None of that information gets written into any file in /etc anymore (as of Leap 15.0, perhaps even earlier). It is all stored in various places in /var/run/netconfig and /var/run/wicked (especially the latter). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 04:28 PM, Darryl Gregorash wrote:
There is a DHCP option; without it, I would not have a FQDN at all.
None of that information gets written into any file in /etc anymore (as of Leap 15.0, perhaps even earlier). It is all stored in various places in /var/run/netconfig and /var/run/wicked (especially the latter).
But if it's not in /etc/resolv.conf, then you need the FQDN to access anything. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-05-07 03:18 PM, James Knott wrote:
On 05/07/2019 04:28 PM, Darryl Gregorash wrote:
There is a DHCP option; without it, I would not have a FQDN at all.
None of that information gets written into any file in /etc anymore (as of Leap 15.0, perhaps even earlier). It is all stored in various places in /var/run/netconfig and /var/run/wicked (especially the latter). But if it's not in /etc/resolv.conf, then you need the FQDN to access anything.
Well, that's in there somewhere, I just haven't found it yet. According to the files in /var/run/wicked, my hostname is staticXXX-XXX-XXX-XXX and domain name is accesscomm.ca. However... # hostname -A staticXXX-XXX-XXX-XXX.r.rev.accesscomm.ca Where that r.rev comes from I do not know :D -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 06:52 PM, Darryl Gregorash wrote:
But if it's not in /etc/resolv.conf, then you need the FQDN to access anything.
Well, that's in there somewhere, I just haven't found it yet. According to the files in /var/run/wicked, my hostname is staticXXX-XXX-XXX-XXX and domain name is accesscomm.ca. However...
Try pinging another computer on your LAN, using only the host name. Without the domain listed in resolv.conf, it won't work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-05-07 06:20 PM, James Knott wrote:
On 05/07/2019 06:52 PM, Darryl Gregorash wrote:
But if it's not in /etc/resolv.conf, then you need the FQDN to access anything.
Well, that's in there somewhere, I just haven't found it yet. According to the files in /var/run/wicked, my hostname is staticXXX-XXX-XXX-XXX and domain name is accesscomm.ca. However... Try pinging another computer on your LAN, using only the host name. Without the domain listed in resolv.conf, it won't work.
Well, that will be difficult, without a LAN to ping. Sorry for not making that clear. Though all this has made me wonder, what would happen if I slap another network into this machine, fake a LAN, and try to define a domain name for the internal zone? If I had another monitor and keyboard, I'd also be tempted to fire up the old machine, and see if I could replicate what Carlos is trying to achieve. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 09:11 PM, Darryl Gregorash wrote:
Well, that will be difficult, without a LAN to ping. Sorry for not making that clear.
I have at least 9 or 10 devices on my LAN. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 23.18, James Knott wrote:
On 05/07/2019 04:28 PM, Darryl Gregorash wrote:
There is a DHCP option; without it, I would not have a FQDN at all.
None of that information gets written into any file in /etc anymore (as of Leap 15.0, perhaps even earlier). It is all stored in various places in /var/run/netconfig and /var/run/wicked (especially the latter).
But if it's not in /etc/resolv.conf, then you need the FQDN to access anything.
I have done: #search valinor Valinor in /etc/resolv.conf Elesar:/etc # ping isengard PING isengard (192.168.1.16) 56(84) bytes of data. 64 bytes from Isengard.valinor (192.168.1.16): icmp_seq=1 ttl=64 time=0.324 ms 64 bytes from Isengard.valinor (192.168.1.16): icmp_seq=2 ttl=64 time=0.284 ms ^C It is still working. Elesar:/etc # host -v isengard Trying "isengard" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3450 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;isengard. IN A ;; ANSWER SECTION: isengard. 0 IN A 192.168.1.16 Received 42 bytes from 192.168.1.16#53 in 0 ms Trying "isengard" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62574 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;isengard. IN AAAA Received 26 bytes from 192.168.1.16#53 in 0 ms Trying "isengard" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30432 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;isengard. IN MX Received 26 bytes from 192.168.1.16#53 in 15 ms Elesar:/etc # The dns server is dnsmasq on Isengard precisely, and has two entries (I don't know why two) in its /etc/hosts: 192.168.1.16 Isengard.valinor Isengard 192.168.1.16 Isengard.valinor Isengard So perhaps it resolves because the dns server has both short and long names. I have tried other machines, same thing. Or perhaps after deleting the line in /etc/resolv.conf I need to do something. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 04:08 AM, Carlos E. R. wrote:
I have done:
#search valinor Valinor
in /etc/resolv.conf
Elesar:/etc # ping isengard PING isengard (192.168.1.16) 56(84) bytes of data. 64 bytes from Isengard.valinor (192.168.1.16): icmp_seq=1 ttl=64 time=0.324 ms 64 bytes from Isengard.valinor (192.168.1.16): icmp_seq=2 ttl=64 time=0.284 ms ^C
It is still working.
Here's what I get with my local domain in resolv.conf: # ping firewall PING firewall(firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3)) 56 data bytes 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=1 ttl=64 time=0.109 ms 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=2 ttl=64 time=0.273 ms 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=3 ttl=64 time=0.257 ms Now, if I comment out my domain name in resolv.conf: # ping firewall ping: firewall: Name or service not known I don't know why you get something different. I'm running 15.0. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 11:26 AM, James Knott wrote:
I don't know why you get something different. I'm running 15.0.
I just edited resolv.conf to change "search" to "domain" and it still works. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 17.30, James Knott wrote:
On 05/08/2019 11:26 AM, James Knott wrote:
I don't know why you get something different. I'm running 15.0.
I just edited resolv.conf to change "search" to "domain" and it still works.
I don't think I follow? You added a line on resolv.conf with domain jknott.net ? Ah, I see: (man) domain Local domain name. Most queries for names within this domain can use short names relative to the local domain. If set to '.', the root domain is considered. If no domain entry is present, the domain is determined from the local hostname returned by gethostname(2); the domain part is taken to be everything after the first '.'. Finally, if the hostname does not contain a domain part, the root domain is assumed. It says that if not present, it is obtained from gethostname(2). How can that call know the fqdn from DNS using only the "name", not the domain name? For instance, the dns can know about several machines with the same name and different domains. So we have for writing the domain part: domain whateverdomain (in resolv.conf) name.whateverdomain (/etc/hostname) -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* James Knott <james.knott@jknott.net> [05-08-19 11:27]:
On 05/08/2019 04:08 AM, Carlos E. R. wrote:
I have done:
#search valinor Valinor
in /etc/resolv.conf
Elesar:/etc # ping isengard PING isengard (192.168.1.16) 56(84) bytes of data. 64 bytes from Isengard.valinor (192.168.1.16): icmp_seq=1 ttl=64 time=0.324 ms 64 bytes from Isengard.valinor (192.168.1.16): icmp_seq=2 ttl=64 time=0.284 ms ^C
It is still working.
Here's what I get with my local domain in resolv.conf:
# ping firewall PING firewall(firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3)) 56 data bytes 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=1 ttl=64 time=0.109 ms 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=2 ttl=64 time=0.273 ms 64 bytes from firewall.jknott.net (fd48:1a37:2160:0:216:17ff:fea7:f2d3): icmp_seq=3 ttl=64 time=0.257 ms
Now, if I comment out my domain name in resolv.conf:
# ping firewall ping: firewall: Name or service not known
if you define "firewall" as fd48:1a37:2160:0:216:17ff:fea7:f2d3 firewall.jknott.net firewall in /etc/hosts your ping will succeed.
I don't know why you get something different. I'm running 15.0.
Tumbleweed and 42.2 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 11:37 AM, Patrick Shanahan wrote:
if you define "firewall" as fd48:1a37:2160:0:216:17ff:fea7:f2d3 firewall.jknott.net firewall
in /etc/hosts your ping will succe
Why should I do that when I have a dns server? Also, I'd have to do that on every device I might use, including some where I have no access to the hosts file. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 17.26, James Knott wrote:
On 05/08/2019 04:08 AM, Carlos E. R. wrote:
I have done:
...
Now, if I comment out my domain name in resolv.conf:
# ping firewall ping: firewall: Name or service not known
I don't know why you get something different. I'm running 15.0.
Maybe because the DNS is masqdns and the entries there are in /etc/hosts file, which contain both the long and the short names. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 01:08 PM, Carlos E. R. wrote:
I don't know why you get something different. I'm running 15.0. Maybe because the DNS is masqdns and the entries there are in /etc/hosts file, which contain both the long and the short names.
My hosts only had the short name, so I added the FQDN. Same result. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Long post showing what I tried, the process - at the bottom, the finding. Quick answer: the domain name is simply written in /etc/hosts, matching the machine name with an entry in that file. On 08/05/2019 19.33, James Knott wrote:
On 05/08/2019 01:08 PM, Carlos E. R. wrote:
I don't know why you get something different. I'm running 15.0. Maybe because the DNS is masqdns and the entries there are in /etc/hosts file, which contain both the long and the short names.
My hosts only had the short name, so I added the FQDN. Same result.
Oh? Elesar:/etc # grep -d skip -i valinor * HOSTNAME:Elesar.valinor hostname:Elesar.valinor hosts:#192.168.1.133 Elesar.valinor Elsesar hosts:192.168.1.134 Elesar.valinor Elsesar hosts~:192.168.1.133 Elesar.valinor Elsesar hosts~:192.168.1.134 Elesar.valinor Elsesar resolv.conf:#search valinor Valinor resolv.conf.no:search valinor Valinor resolv.conf~:search valinor Valinor Elesar:/etc # Currently, only the "hostname" file has the domain. If I remove the domain, it still works: Elesar:/etc # hostname Elesar lesar:/etc # hostname -f hostname: Name or service not known Elesar:/etc # host router router has address 192.168.1.1 Elesar:/etc # May it be that the DNS machine has a hostname with the domain part? Ah, I think I see it. dnsmasq has a line: local=/valinor/ but the comments do not match my thoughts. I can not paste, but the line means that queries on that domain are not sent upstream. Then how do that machine knows which is the domain name? It must be defined somewhere, it is the LAN DNS server. In that machine, "hostname -f" is working. The answer so far in this thread is that the DNS tells. Ok, but how does my dnsmasq in 15.0 obtain that info from? Look, I removed "valinor" from all files in /etc, even the "local" in dnsmaq, and still "hostname -f" is working. I restore things and they still work. And now, surprise, Elesar:~ # hostname -f Elesar.valinor Elesar:~ # Ah, I know why. Typo in hosts file: hosts:192.168.1.134 Elesar.valinor Elsesar Writing this post I noticed and corrected. How exactly does this machine know the fqdn? Elesar:~ # strace -o hostname.strace hostname -f Elesar.valinor Elesar:~ #
From nscd:
connect(3, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = 0 sendto(3, "\2\0\0\0\16\0\0\0\7\0\0\0Elesar\0", 19, MSG_NOSIGNAL, NULL, 0) = 19 poll([{fd=3, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 1 ([{fd=3, revents=POLLIN|POLLHUP}]) read(3, "\2\0\0\0\1\0\0\0\1\0\0\0\4\0\0\0\17\0\0\0\0\0\0\0", 24) = 24 read(3, "\300\250\1\206\2Elesar.valinor\0", 20) = 20 close(3) = 0 fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 8), ...}) = 0 write(1, "Elesar.valinor\n", 15) = 15 Ok, I'll stop nscd and retry. open("/etc/hosts", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=718, ...}) = 0 read(3, "#\n# hosts This file desc"..., 4096) = 718 read(3, "", 4096) = 0 close(3) = 0 fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 8), ...}) = 0 write(1, "Elesar.valinor\n", 15) = 15 exit_group(0) = ? +++ exited with 0 +++
From the hosts file? Am I reading it right?
It knows already the "name" of the machine, because above that I see: uname({sysname="Linux", nodename="Elesar", ...}) = 0 so it looks for the short Elesar name in the /etc/hosts files and there finds the fullname. That's it. Elesar:~ # dnsdomainname valinor Elesar:~ # Ok! So I got it working. No need for a working DNS? There is no entry in the DNS for this machine. Let's try disabling the DNS in resolv.conf: domain valinor #nameserver 192.168.1.16 nameserver 80.58.61.250 nameserver 80.58.61.254 Elesar:/etc # dnsdomainname valinor Elesar:/etc # host router Host router not found: 3(NXDOMAIN) Elesar:/etc # Bingo! Does the current IP need to match? Yes, it does (I changed it in host file, then dnsdomainname fails). -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2019 02:25 PM, Carlos E. R. wrote:
Currently, only the "hostname" file has the domain. If I remove the domain, it still works:
Again, I have no idea why the difference. I have posted my results a couple of times. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Darryl Gregorash wrote:
On 2019-05-07 12:35 PM, Per Jessen wrote:
Maybe that man page was supposed to have been updated long ago. I have no 'domain' statement in any resolv.conf, anywhere. I wonder if there is even a dhcp option for setting it. (if it's important, there ought to be one).
There is a DHCP option; without it, I would not have a FQDN at all.
In my dhcpd.conf I see e.g. "option domain-name", in my dhcpv6.conf there's no such option. Neither seems to cause anything to be written to /etc/resolv.conf. (even on very old systems, going back to 10.3). According to ISC:
The domain-name data type specifies a domain name, which must not be enclosed in double quotes. This data type is not used for any existing DHCP options. The domain name is stored just as if it were a text option.
I have just now removed that option from the config. Let's see if anything happens :-) -- Per Jessen, Zürich (9.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-05-06 08:17 PM, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 03:46:30 CEST schreef Darryl Gregorash:
As I was saying, it sets that in the /etc/hosts file. Using YaST > Network Services > Hostnames. Why insist on working on on something that does not work, instead of doing it incl. YaST usage in a way that does work. Things change. Because Carlos wants to give each machine a fixed hostname, and assign its IP by DHCP! That should be possible to do without editing a text file by hand. Things like this are what YaST was designed to do, are
On 2019-05-06 06:21 PM, Knurpht-openSUSE wrote: they not? Yes, but like said, things change. I have a cheap > 12 year old router that can bind/reserve a fixed IP address to a machine's ethernet interface ( IIRC on mac address ). Why does it have to be a variable IP address? Even in my Maybe you should ask that question of Carlos; it's his network. My response to this is, that is what Carlos wants to do, and I don't see any reason why he should be disallowed from doing it. UNIX days ( 1990s, AT&T UNIX System V ) I was tought that a reliable server should have the same IP address all the time and not rely on a DHCP pool. I I rather imagine that his server system does have the same IP all the time; it is the rest of his LAN that he wishes to have dynamic IPs. YaST is not designed to last forever in the same way it started. Networking hasn't. What can be configured in the system should be possible to do in YaST, should it not? Honestly, I don't see the point.
I have a vague mental image of some Boeing software developer saying the same thing in response to the question, "How do you turn MCAS off if it starts to misbehave?" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 05.33, Darryl Gregorash wrote:
On 2019-05-06 08:17 PM, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 03:46:30 CEST schreef Darryl Gregorash:
As I was saying, it sets that in the /etc/hosts file. Using YaST > Network Services > Hostnames. Why insist on working on on something that does not work, instead of doing it incl. YaST usage in a way that does work. Things change. Because Carlos wants to give each machine a fixed hostname, and assign its IP by DHCP! That should be possible to do without editing a text file by hand. Things like this are what YaST was designed to do, are
On 2019-05-06 06:21 PM, Knurpht-openSUSE wrote: they not? Yes, but like said, things change. I have a cheap > 12 year old router that can bind/reserve a fixed IP address to a machine's ethernet interface ( IIRC on mac address ). Why does it have to be a variable IP address? Even in my Maybe you should ask that question of Carlos; it's his network. My response to this is, that is what Carlos wants to do, and I don't see any reason why he should be disallowed from doing it.
The reason is that I'm testing 15.1 for different scenarios, like for my laptops, that are not always connected to my LAN. They can connect to other LANs, or to my phone thether, and in those cases I do not control the dhcp.
UNIX days ( 1990s, AT&T UNIX System V ) I was tought that a reliable server should have the same IP address all the time and not rely on a DHCP pool. I I rather imagine that his server system does have the same IP all the time; it is the rest of his LAN that he wishes to have dynamic IPs.
Yes. Correct, the main install of the machine uses a fixed IP and runs bind. But this is a test partition where I want to use automatic network setup.
YaST is not designed to last forever in the same way it started. Networking hasn't. What can be configured in the system should be possible to do in YaST, should it not? Honestly, I don't see the point.
I have a vague mental image of some Boeing software developer saying the same thing in response to the question, "How do you turn MCAS off if it starts to misbehave?"
:-D -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On 07/05/2019 04.17, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 03:46:30 CEST schreef Darryl Gregorash:
On 2019-05-06 06:21 PM, Knurpht-openSUSE wrote:
As I was saying, it sets that in the /etc/hosts file. Using YaST > Network Services > Hostnames. Why insist on working on on something that does not work, instead of doing it incl. YaST usage in a way that does work. Things change.
Because Carlos wants to give each machine a fixed hostname, and assign its IP by DHCP! That should be possible to do without editing a text file by hand. Things like this are what YaST was designed to do, are they not? Yes, but like said, things change. I have a cheap > 12 year old router that can bind/reserve a fixed IP address to a machine's ethernet interface ( IIRC on mac address ). Why does it have to be a variable IP address? Even in my UNIX days ( 1990s, AT&T UNIX System V ) I was tought that a reliable server should have the same IP address all the time and not rely on a DHCP pool. I simply don't get the reasoning behind the desire not doing it like that.
I told you: because the dhcp is not always under my control. I can be a guest on another house, or I can be tethered to my android phone. I get it working by having a script hook on NM that edit /etc/hosts and using dnsmasq. Which is a hack. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 00.44, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 00:34:01 CEST schreef Darryl Gregorash:
On 2019-05-06 04:16 PM, Knurpht-openSUSE wrote:
Op maandag 6 mei 2019 22:43:47 CEST schreef Carlos E. R.:
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
Yes, you are barking up the wrong tree. You, on 15.1, also have YaST > Network Services > Hostnames. Set as many as you want. It will add the hostname/domain
That assumes a fixed known IP, and that is not the case.
That assigns a name to an IP, not to an interface or machine. I believe Carlos wants to give each machine a name, then obtain its IP by DHCP. If set properly in the hosts file, also hostname -f works as expexted.
Again, that assumes a fixed known IP, and that is not the case.
See knurpht@salt:~> hostname salt knurpht@salt:~> hostname -f salt.knurpht.nl knurpht@salt:~> cat /etc/resolv.conf | grep search search knurpht.nl knurpht@salt:~>
Just to mention: On this machine I have a dozen of domains and a plethora of subdomains. No FQDN or DNS issues at all. Carlos could even add the entire scope of DHCP addresses for the same domainname, it would still work. And AFAIK that is what Carlos wants.
Different names and domains to a single machine? I don't think that is possible. Even if done, it breaks reverse resolution. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 7 mei 2019 02:18:04 CEST schreef Carlos E. R.:
On 07/05/2019 00.44, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 00:34:01 CEST schreef Darryl Gregorash:
On 2019-05-06 04:16 PM, Knurpht-openSUSE wrote:
Op maandag 6 mei 2019 22:43:47 CEST schreef Carlos E. R.:
All that I'm trying to say is that you are barking up the wrong tree. If your concern is (non) working "hostname -f" or how to associate dynamic IP with static label it is not related to "Domain Name" field in YaST.
I'm not barking. I'm asking what is the correct place to set the domain name in Leap. It is very simple!
You are basically saying "nowhere".
Yes, you are barking up the wrong tree. You, on 15.1, also have YaST > Network Services > Hostnames. Set as many as you want. It will add the hostname/domain
That assumes a fixed known IP, and that is not the case.
That assigns a name to an IP, not to an interface or machine. I believe Carlos wants to give each machine a name, then obtain its IP by DHCP.
If set properly in the hosts file, also hostname -f works as expexted.
Again, that assumes a fixed known IP, and that is not the case.
See knurpht@salt:~> hostname salt knurpht@salt:~> hostname -f salt.knurpht.nl knurpht@salt:~> cat /etc/resolv.conf | grep search search knurpht.nl knurpht@salt:~>
Just to mention: On this machine I have a dozen of domains and a plethora of subdomains. No FQDN or DNS issues at all. Carlos could even add the entire scope of DHCP addresses for the same domainname, it would still work. And AFAIK that is what Carlos wants.
Different names and domains to a single machine? I don't think that is possible. Even if done, it breaks reverse resolution. knurpht@salt:~> cat /etc/hosts # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost 127.0.0.1 knurphtvps knurphtvps 127.0.0.1 salt.knurpht.nl salt.knurpht.nl 127.0.0.1 owncloud.knurpht.nl owncloud.knurpht.nl 127.0.0.1 cloud.knurpht.nl cloud.knurpht.nl 127.0.0.1 mijncloudkantoor.nl mijncloudkantoor.nl 127.0.0.1 office.knurpht.nl office.knurpht.nl 127.0.0.1 media.knurpht.nl media.knurpht.nl 127.0.0.1 phpmyadmin.knurpht.nl phpmyadmin.knurpht.nl 127.0.0.1 schermclub.knurpht.nl schermclub.knurpht.nl XXX.XXX.XXX.XXX salt.knurpht.nl salt.knurpht.nl XXX.XXX.XXX.XXX knurpht.nl knurpht.nl XXX.XXX.XXX.XXX mail.knurpht.nl mail.knurpht.nl XXX.XXX.XXX.XXX owncloud.knurpht.nl owncloud.knurpht.nl XXX.XXX.XXX.XXX cloud.knurpht.nl cloud.knurpht.nl XXX.XXX.XXX.XXX mijncloudkantoor.nl mijncloudkantoor.nl XXX.XXX.XXX.XXX office.knurpht.nl office.knurpht.nl XXX.XXX.XXX.XXX media.knurpht.nl media.knurpht.nl XXX.XXX.XXX.XXX phpmyadmin.knurpht.nl phpmyadmin.knurpht.nl XXX.XXX.XXX.XXX schermclub.knurpht.nl schermclub.knurpht.nl XXX.XXX.XXX.XXX office.knurpht.nl office.knurpht.nl # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts knurpht@salt:~> Do you believe me now? Please stop. These ( and there's a lot more ) all work. And yours doesn't. So I guess I'm wrong. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 02.27, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 02:18:04 CEST schreef Carlos E. R.:
...
Different names and domains to a single machine? I don't think that is possible. Even if done, it breaks reverse resolution. knurpht@salt:~> cat /etc/hosts # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost 127.0.0.1 knurphtvps knurphtvps 127.0.0.1 salt.knurpht.nl salt.knurpht.nl
This breaks postfix. .... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2 ...
knurpht@salt:~>
Do you believe me now? Please stop. These ( and there's a lot more ) all work. And yours doesn't. So I guess I'm wrong.
Elesar:~ # tail /etc/hosts fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.133 Elesar.valinor Elsesar 192.168.1.134 Elesar.valinor Elsesar Elesar:~ # Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # No, it does not work. Next idea? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 07/05/2019 02.27, Knurpht-openSUSE wrote:
knurpht@salt:~> cat /etc/hosts # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost 127.0.0.1 knurphtvps knurphtvps 127.0.0.1 salt.knurpht.nl salt.knurpht.nl
This breaks postfix.
.... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2
Uh no it doesn't. I've just put all of Gertjans /etc/hosts into one of mine and sent you a mail. (a 15.1 machine). Why is your postfix trying to listen on 127.0.0.2? -- Per Jessen, Zürich (4.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 08.15, Per Jessen wrote:
Carlos E. R. wrote:
On 07/05/2019 02.27, Knurpht-openSUSE wrote:
knurpht@salt:~> cat /etc/hosts # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost 127.0.0.1 knurphtvps knurphtvps 127.0.0.1 salt.knurpht.nl salt.knurpht.nl
This breaks postfix.
.... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2
Uh no it doesn't. I've just put all of Gertjans /etc/hosts into one of mine and sent you a mail. (a 15.1 machine).
I tried and I still would not get "hostname -f" working.
Why is your postfix trying to listen on 127.0.0.2?
I wrote a bugzilla about that years ago. At the time, yast created that entry. Since them, I take care to delete that or equivalent line from the hosts file. Don't you remember? Bug 824141 -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 07/05/2019 08.15, Per Jessen wrote:
Carlos E. R. wrote:
On 07/05/2019 02.27, Knurpht-openSUSE wrote:
knurpht@salt:~> cat /etc/hosts # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are # running. On small systems, this file can be used # instead of a "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost 127.0.0.1 knurphtvps knurphtvps 127.0.0.1 salt.knurpht.nl salt.knurpht.nl
This breaks postfix.
.... fatal: parameter inet_interfaces: no local interface found for 127.0.0.2
Uh no it doesn't. I've just put all of Gertjans /etc/hosts into one of mine and sent you a mail. (a 15.1 machine).
I tried and I still would not get "hostname -f" working.
Why is your postfix trying to listen on 127.0.0.2?
I wrote a bugzilla about that years ago. At the time, yast created that entry. Since them, I take care to delete that or equivalent line from the hosts file.
Don't you remember?
And this also happens on 15.1 ? We are not interested in the old stuff right now. -- Per Jessen, Zürich (11.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 13.50, Per Jessen wrote:
Carlos E. R. wrote:
On 07/05/2019 08.15, Per Jessen wrote:
Carlos E. R. wrote:
Why is your postfix trying to listen on 127.0.0.2?
I wrote a bugzilla about that years ago. At the time, yast created that entry. Since them, I take care to delete that or equivalent line from the hosts file.
Don't you remember?
And this also happens on 15.1 ? We are not interested in the old stuff right now.
I don't know, I have no way to test it currently. I have no reason to think the situation has changed, as both sides were adamant that it was the other side issue. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
Carlos E. R. wrote:
On 07/05/2019 13.50, Per Jessen wrote:
Carlos E. R. wrote:
On 07/05/2019 08.15, Per Jessen wrote:
Carlos E. R. wrote:
Why is your postfix trying to listen on 127.0.0.2?
I wrote a bugzilla about that years ago. At the time, yast created that entry. Since them, I take care to delete that or equivalent line from the hosts file.
Don't you remember?
And this also happens on 15.1 ? We are not interested in the old stuff right now.
I don't know, I have no way to test it currently. I have no reason to think the situation has changed, as both sides were adamant that it was the other side issue.
YaST apparently wrote that 127.0.0.2 entry to /etc/hosts - YaST has changed a lot, that seems reason enough to suspect this might have changed too. Anyway, as it isn't currently a problem, let's return when/if it re-appears. -- Per Jessen, Zürich (9.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2019 07.53, Per Jessen wrote:
Carlos E. R. wrote:
On 07/05/2019 13.50, Per Jessen wrote:
Carlos E. R. wrote:
On 07/05/2019 08.15, Per Jessen wrote:
Carlos E. R. wrote:
Why is your postfix trying to listen on 127.0.0.2?
I wrote a bugzilla about that years ago. At the time, yast created that entry. Since them, I take care to delete that or equivalent line from the hosts file.
Don't you remember?
And this also happens on 15.1 ? We are not interested in the old stuff right now.
I don't know, I have no way to test it currently. I have no reason to think the situation has changed, as both sides were adamant that it was the other side issue.
YaST apparently wrote that 127.0.0.2 entry to /etc/hosts - YaST has changed a lot, that seems reason enough to suspect this might have changed too. Anyway, as it isn't currently a problem, let's return when/if it re-appears.
It wont reappear on my machines as I take evasive actions to avoid it on my setups. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, May 7, 2019 6:13:02 AM CDT Carlos E. R. wrote:
On 07/05/2019 08.15, Per Jessen wrote:
[...]
Why is your postfix trying to listen on 127.0.0.2?
I wrote a bugzilla about that years ago. At the time, yast created that entry. Since them, I take care to delete that or equivalent line from the hosts file.
Don't you remember?
Bug 824141
I don't know about postfix, but on 15.0, yast created a similar entry. hosts contains 127.0.0.2 sgt.decathlon.org sgt . It doesn't seem to hurt anything. Should I change it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, May 7, 2019 9:25:13 AM CDT you wrote:
On Tuesday, May 7, 2019 6:13:02 AM CDT Carlos E. R. wrote:
On 07/05/2019 08.15, Per Jessen wrote: [...]
Why is your postfix trying to listen on 127.0.0.2?
I wrote a bugzilla about that years ago. At the time, yast created that entry. Since them, I take care to delete that or equivalent line from the hosts file.
Don't you remember?
Bug 824141
I don't know about postfix, but on 15.0, yast created a similar entry. hosts contains 127.0.0.2 sgt.decathlon.org sgt . It doesn't seem to hurt anything. Should I change it?
Yast also added the domain part to /etc/hostname -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Robert T Hardy wrote:
On Tuesday, May 7, 2019 9:25:13 AM CDT you wrote:
On Tuesday, May 7, 2019 6:13:02 AM CDT Carlos E. R. wrote:
On 07/05/2019 08.15, Per Jessen wrote: [...]
Why is your postfix trying to listen on 127.0.0.2?
I wrote a bugzilla about that years ago. At the time, yast created that entry. Since them, I take care to delete that or equivalent line from the hosts file.
Don't you remember?
Bug 824141
I don't know about postfix, but on 15.0, yast created a similar entry. hosts contains 127.0.0.2 sgt.decathlon.org sgt . It doesn't seem to hurt anything. Should I change it?
No reason to.
Yast also added the domain part to /etc/hostname
I am pretty certain that has been the practice since year dot. A while back, we had a debate about the default domain to use - it used to be 'local' (I think!), but then that was registered as a public tld, then we used 'suse' for a while. I have a 42.3 laptop here, that uses 'suse' as default domain. -- Per Jessen, Zürich (16.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
07.05.2019 17:47, Robert T Hardy пишет:
Yast also added the domain part to /etc/hostname
Which is entirely useless because SUSE since years stripped off domain part of hostname before setting it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 02:28 PM, Andrei Borzenkov wrote:
Again - what exactly constitutes "bug"? What worked on 15.0 but does not work on 15.1 because this field is not present?
I think we're talking about two different issues here. I was referring to 15.0, where there is a box for domain name, but it doesn't work. I had to add the domain name to domain search, so that just the host name could be used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
06.05.2019 21:32, James Knott пишет:
On 05/06/2019 02:28 PM, Andrei Borzenkov wrote:
Again - what exactly constitutes "bug"? What worked on 15.0 but does not work on 15.1 because this field is not present?
I think we're talking about two different issues here. I was referring to 15.0, where there is a box for domain name, but it doesn't work. I
It sort of worked but inconsistently. The first time you entered domain name nothing happened. Second time you called YaST value was copied into Domain Search field. If anything else was changed, it now appeared in /etc/resolv.conf - but not because it was entered in Domain Name. But if nothing was changed, nothing happened either.
had to add the domain name to domain search, so that just the host name could be used.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. composed on 2019-05-06 18:52 (UTC+0200):
Where is one supposed to write the domain name?
Where the configuration is supposed to be saved is a good question I don't know the answer to. I would expect /etc/sysconfig/network/config, but if it's in there it's not apparent to me. I use fixed IP and have an entry in /etc/hosts: ###.###.###.### FQDN Short -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 19.23, Felix Miata wrote:
Carlos E. R. composed on 2019-05-06 18:52 (UTC+0200):
Where is one supposed to write the domain name?
Where the configuration is supposed to be saved is a good question I don't know the answer to. I would expect /etc/sysconfig/network/config, but if it's in there it's not apparent to me. I use fixed IP and have an entry in /etc/hosts:
###.###.###.### FQDN Short
But in this test partition I'm using automatics. I could allow the router to set the domain name, though. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y
Elesar:~ # hostname -A
Elesar:~ # hostname Elesar Elesar:~ #
So, I start and look into Network Settings, and in hostname I try to write a domain name after a dot - it does not allow me to set a domain name.
Yes, something was changed in YaST - in 15.1, there is no longer an input field for a domain name and the hostname field only accepts a hostname. bugzilla ? https://files.jessen.ch/yast-lan-leap150.jpeg https://files.jessen.ch/yast-lan-leap151.jpeg -- Per Jessen, Zürich (7.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 6 mei 2019 18:52:03 CEST schreef Carlos E. R.:
Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y
Elesar:~ # hostname -A
Elesar:~ # hostname Elesar Elesar:~ #
So, I start and look into Network Settings, and in hostname I try to write a domain name after a dot - it does not allow me to set a domain name.
Where is one supposed to write the domain name? Check ( I'm on TW atm ) if the YaST > Network Services > Hostnames module exists. So far, any addition of hostnames / domains works fine using this.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2019 23.56, Knurpht-openSUSE wrote:
Op maandag 6 mei 2019 18:52:03 CEST schreef Carlos E. R.:
Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y
Elesar:~ # hostname -A
Elesar:~ # hostname Elesar Elesar:~ #
So, I start and look into Network Settings, and in hostname I try to write a domain name after a dot - it does not allow me to set a domain name.
Where is one supposed to write the domain name? Check ( I'm on TW atm ) if the YaST > Network Services > Hostnames module exists. So far, any addition of hostnames / domains works fine using this.
But that assumes a fixed IP, and it is not. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 11:52 AM, Carlos E. R. wrote:
Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y
Elesar:~ # hostname -A
Elesar:~ # hostname Elesar Elesar:~ #
Just a guess there is a mismatch between what you set as your hostname and what is found in /etc/hosts My approach # hostname yourhostname # echo yourhostname > /etc/hostname # vi /etc/hosts (make it match and set the domain part here) In the new systemd arena there is also hostnamectl that allows you to set the hostname there. Thus far, I've just stuck to the old ways. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 7 mei 2019 05:59:16 CEST schreef David C. Rankin:
In the new systemd arena there is also hostnamectl that allows you to set the hostname there. You may have hit exactly the point I could not make lacking the proper knowledge, i.e. an entry in /etc/hosts being necessary.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-05-06 10:03 PM, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 05:59:16 CEST schreef David C. Rankin:
In the new systemd arena there is also hostnamectl that allows you to set the hostname there. You may have hit exactly the point I could not make lacking the proper knowledge, i.e. an entry in /etc/hosts being necessary.
And the point the rest of us are making is this should be possible to do in YaST. Apologies for the "Boeing" remark. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/06/2019 11:03 PM, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 05:59:16 CEST schreef David C. Rankin:
In the new systemd arena there is also hostnamectl that allows you to set the hostname there. You may have hit exactly the point I could not make lacking the proper knowledge, i.e. an entry in /etc/hosts being necessary.
Yes, I haven't kept up with all the changes on how hostname resolution has is handled or changed in the past few years, but I have run into cases where if there is a mismatch between what /etc/hosts thinks the hostname is and what the system thinks it is -- that will cause messages very similar to what Carlos reports. There isn't a requirement /etc/hostname even be present, but traditionally it has always held the hostname for early-boot when there are no servers running to provide it. It can contain the DNS domain portion of the hostname as well, but most of the systems I have simply have the hostname without the domain component. (I'd be more apt to include it on systems using a fixed address) One of these days I'll have to come out from under my digital rock and chase down exactly how it is handled now. It's been since the dnsdomainname / gethostbyname changes half a decade or so ago that I even looked. One thing that is rather strange is 15.0 has no domain component in /etc/hostname, but it is included in /etc/hosts, 42.3 is the exact opposite. I have no recollection of intentionally setting either one way or the other, so I don't think it is critical which way it is done, so long as the domain is defined somewhere and the hostname is consistent between the sources... Looking at root's history on 15, it looks like I set the hostname with the domain component with hostname, but I have no record of what I put in the other... 5 2018-04-13 03:21:20 hostname vlleap15.3111skyline.com 6 2018-04-13 03:21:34 vi /etc/hostname 7 2018-04-13 03:21:53 vi /etc/hosts -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 07.05.19 um 07:02 schrieb David C. Rankin:
Looking at root's history on 15, it looks like I set the hostname with the domain component with hostname, but I have no record of what I put in the other...
5 2018-04-13 03:21:20 hostname vlleap15.3111skyline.com 6 2018-04-13 03:21:34 vi /etc/hostname 7 2018-04-13 03:21:53 vi /etc/hosts
hi david, how to get a root history? i know only the file bash_history, but i think you have some different? simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
Am 07.05.19 um 07:02 schrieb David C. Rankin:
Looking at root's history on 15, it looks like I set the hostname with the domain component with hostname, but I have no record of what I put in the other...
5 2018-04-13 03:21:20 hostname vlleap15.3111skyline.com 6 2018-04-13 03:21:34 vi /etc/hostname 7 2018-04-13 03:21:53 vi /etc/hosts
hi david, how to get a root history? i know only the file bash_history, but i think you have some different?
Just type 'history' ? -- Per Jessen, Zürich (5.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 07.05.19 um 08:44 schrieb Per Jessen:
Simon Becherer wrote:
Am 07.05.19 um 07:02 schrieb David C. Rankin:
Looking at root's history on 15, it looks like I set the hostname with the domain component with hostname, but I have no record of what I put in the other...
5 2018-04-13 03:21:20 hostname vlleap15.3111skyline.com 6 2018-04-13 03:21:34 vi /etc/hostname 7 2018-04-13 03:21:53 vi /etc/hosts
hi david, how to get a root history? i know only the file bash_history, but i think you have some different?
Just type 'history' ?
thanks, not knowing this command. but bad luck, its the same as stored in file bash_history i was thinking its something more like a "for ever stored, compressed file" like some system log files simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
Am 07.05.19 um 08:44 schrieb Per Jessen:
Simon Becherer wrote:
Am 07.05.19 um 07:02 schrieb David C. Rankin:
Looking at root's history on 15, it looks like I set the hostname with the domain component with hostname, but I have no record of what I put in the other...
5 2018-04-13 03:21:20 hostname vlleap15.3111skyline.com 6 2018-04-13 03:21:34 vi /etc/hostname 7 2018-04-13 03:21:53 vi /etc/hosts
hi david, how to get a root history? i know only the file bash_history, but i think you have some different?
Just type 'history' ?
thanks, not knowing this command. but bad luck, its the same as stored in file bash_history
I thought so too.
i was thinking its something more like a "for ever stored, compressed file" like some system log files
There is presumbly some limit - on one system, my root history goes back to June 2018. -- Per Jessen, Zürich (8.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, May 7, 2019 at 12:17 PM Per Jessen <per@computer.org> wrote:
i was thinking its something more like a "for ever stored, compressed file" like some system log files
There is presumbly some limit - on one system, my root history goes back to June 2018.
https://stackoverflow.com/questions/9457233/unlimited-bash-history -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
On Tue, May 7, 2019 at 12:17 PM Per Jessen <per@computer.org> wrote:
i was thinking its something more like a "for ever stored, compressed file" like some system log files
There is presumbly some limit - on one system, my root history goes back to June 2018.
https://stackoverflow.com/questions/9457233/unlimited-bash-history
aha, Set HISTSIZE and HISTFILESIZE in .bashrc to an empty string: HISTSIZE= HISTFILESIZE= 1000 entries is good enough for me :-) -- Per Jessen, Zürich (10.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 04:17 AM, Per Jessen wrote:
Simon Becherer wrote:
Am 07.05.19 um 08:44 schrieb Per Jessen:
Simon Becherer wrote:
Am 07.05.19 um 07:02 schrieb David C. Rankin:
Looking at root's history on 15, it looks like I set the hostname with the domain component with hostname, but I have no record of what I put in the other...
5 2018-04-13 03:21:20 hostname vlleap15.3111skyline.com 6 2018-04-13 03:21:34 vi /etc/hostname 7 2018-04-13 03:21:53 vi /etc/hosts
hi david, how to get a root history? i know only the file bash_history, but i think you have some different?
Just type 'history' ?
thanks, not knowing this command. but bad luck, its the same as stored in file bash_history
I thought so too.
i was thinking its something more like a "for ever stored, compressed file" like some system log files
There is presumbly some limit - on one system, my root history goes back to June 2018.
I always make sure I store at least 40K entries in my history file. In .bashrc: export HISTFILESIZE=40000 export HISTSIZE=40000 export HISTCONTROL=ignoreboth:erasedups export HISTIGNORE=' *:&' -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/07/2019 01:34 AM, Simon Becherer wrote:
Am 07.05.19 um 07:02 schrieb David C. Rankin:
Looking at root's history on 15, it looks like I set the hostname with the domain component with hostname, but I have no record of what I put in the other...
5 2018-04-13 03:21:20 hostname vlleap15.3111skyline.com 6 2018-04-13 03:21:34 vi /etc/hostname 7 2018-04-13 03:21:53 vi /etc/hosts
hi david, how to get a root history? i know only the file bash_history, but i think you have some different?
simoN
Simon, the 'history' command shows the users current history. If you want root's history, you su to root and type history. But like anything Linux you can always tailor it to your needs. I don't like typing and when I want to look at history, I ususally want to look at something specific. So instead of having to type 'history | grep "whatIwant"' each time, I add a simple function and alias to my .bashrc, so all I need to do is type 'hist whatIwant'. The function and alias are: showhist() { [ -z "$1" ] && { printf "usage: hist <search term>\n"; return 1; } history | grep "$1" } alias hist='showhist' I generally create a function that gives some usage information if I just type the name and forget to type the required arguments. Better yet, you would have it respond to '-h' or '--help' as well :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/05/2019 07.02, David C. Rankin wrote:
On 05/06/2019 11:03 PM, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 05:59:16 CEST schreef David C. Rankin:
In the new systemd arena there is also hostnamectl that allows you to set the hostname there. You may have hit exactly the point I could not make lacking the proper knowledge, i.e. an entry in /etc/hosts being necessary.
Yes, I haven't kept up with all the changes on how hostname resolution has is handled or changed in the past few years, but I have run into cases where if there is a mismatch between what /etc/hosts thinks the hostname is and what the system thinks it is -- that will cause messages very similar to what Carlos reports.
But it is a new system, I did not write what was on the /etc/hosts file myself.
There isn't a requirement /etc/hostname even be present, but traditionally it has always held the hostname for early-boot when there are no servers running to provide it. It can contain the DNS domain portion of the hostname as well, but most of the systems I have simply have the hostname without the domain component. (I'd be more apt to include it on systems using a fixed address)
One of these days I'll have to come out from under my digital rock and chase down exactly how it is handled now. It's been since the dnsdomainname / gethostbyname changes half a decade or so ago that I even looked.
One thing that is rather strange is 15.0 has no domain component in /etc/hostname, but it is included in /etc/hosts, 42.3 is the exact opposite.
cer@minas-tirith:~> cat /etc/hostname minas-tirith.valinor cer@minas-tirith:~> domainname (none) cer@minas-tirith:~> hostname -f minas-tirith.valinor cer@minas-tirith:~> cat /etc/os-release NAME="openSUSE Leap" VERSION="15.0" (this machine has dnsmasq running locally, so maybe that explains why it has a working fqdn) -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On Mon, May 06, 2019 at 06:52:03PM +0200, Carlos E. R. wrote:
Hi,
Elesar:~ # hostname -f hostname: Name or service not known Elesar:~ # hostname -d hostname: Name or service not known Elesar:~ # hostname -y
Elesar:~ # hostname -A
Elesar:~ # hostname Elesar Elesar:~ #
So, I start and look into Network Settings, and in hostname I try to write a domain name after a dot - it does not allow me to set a domain name.
Where is one supposed to write the domain name?
Nowhere! The domain name belongs to an active network device. Only the domain name of a YP/NIS domain can be set. And this active network device is used to ask the domain name server for the FQDN of the system. Source: man 1 hostname man 1 hostnamectl Nota Bene: the usage of the domain part of a FQDN in /etc/hostname is plain wrong Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On 07/05/2019 08.53, Dr. Werner Fink wrote:
On Mon, May 06, 2019 at 06:52:03PM +0200, Carlos E. R. wrote:
...
Where is one supposed to write the domain name?
Nowhere! The domain name belongs to an active network device. Only the domain name of a YP/NIS domain can be set. And this active network device is used to ask the domain name server for the FQDN of the system.
That's a fair answer, thanks.
Source: man 1 hostname man 1 hostnamectl
Nota Bene: the usage of the domain part of a FQDN in /etc/hostname is plain wrong
Oh! :-o :-( -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On 08/05/2019 00.12, Carlos E. R. wrote:
On 07/05/2019 08.53, Dr. Werner Fink wrote:
On Mon, May 06, 2019 at 06:52:03PM +0200, Carlos E. R. wrote:
...
Where is one supposed to write the domain name?
Nowhere! The domain name belongs to an active network device. Only the domain name of a YP/NIS domain can be set. And this active network device is used to ask the domain name server for the FQDN of the system.
That's a fair answer, thanks.
Next question: then what was the purpose of the domain entry box in Leap 15.0 and all previous versions since I remember? YaST2 - lan @ minas-tirith.valinor Network Settings ┌Global Options──Overview──Hostname/DNS──Routing──────────────┐ │┌Hostname and Domain Name───────────────────────────────────┐│ ││minas-tirith▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ valinor▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ││ <== ││[x] Assign Hostname to Loopback IP ││ ││Set Hostname via DHCP no▒▒▒▒▒▒▒▒▒↓ ││ │└───────────────────────────────────────────────────────────┘│ │Modify DNS Configuration Custom Policy Rule │ │Use Default Policy▒▒▒▒▒↓ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒↓ │ │┌Name Servers and Domain Search List────────────────────────┐│ ││Name Server 1 ┌Domain Search──────────────┐││ ││8.8.8.8▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │valinor │││ ││Name Server 2 │ │││ ││192.168.1.1▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ │││ ││Name Server 3 │ │││ ││▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ └───────────────────────────┘││ │└───────────────────────────────────────────────────────────┘│ └─────────────────────────────────────────────────────────────┘ [Help] [Cancel] [ OK ] -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On 08/05/2019 00.21, Carlos E. R. wrote:
On 08/05/2019 00.12, Carlos E. R. wrote:
On 07/05/2019 08.53, Dr. Werner Fink wrote:
On Mon, May 06, 2019 at 06:52:03PM +0200, Carlos E. R. wrote:
Next question: then what was the purpose of the domain entry box in Leap 15.0 and all previous versions since I remember?
YaST2 - lan @ minas-tirith.valinor
Network Settings ┌Global Options──Overview──Hostname/DNS──Routing──────────────┐ │┌Hostname and Domain Name───────────────────────────────────┐│ ││minas-tirith▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ valinor▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ││ <== ││[x] Assign Hostname to Loopback IP ││ ││Set Hostname via DHCP no▒▒▒▒▒▒▒▒▒↓ ││
The help says: ││Enter the short name for this computer (e.g. mymachine) and the DNS domain ┬│ ││(e.g. example.com) that it belongs to. The domain is especially important if││ ││this computer is a mail server. You can view the hostname of you computer ││ ││using the hostname command. So at some point in time at least it was possible to define the domain name in yast. Why not now, what has changed? (honest question). I assume that if the option has been removed intentionally, it is no longer possible to set it up. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On Wed, May 08, 2019 at 12:28:35AM +0200, Carlos E. R. wrote:
On 08/05/2019 00.21, Carlos E. R. wrote:
On 08/05/2019 00.12, Carlos E. R. wrote:
On 07/05/2019 08.53, Dr. Werner Fink wrote:
On Mon, May 06, 2019 at 06:52:03PM +0200, Carlos E. R. wrote:
Next question: then what was the purpose of the domain entry box in Leap 15.0 and all previous versions since I remember?
YaST2 - lan @ minas-tirith.valinor
Network Settings ┌Global Options──Overview──Hostname/DNS──Routing──────────────┐ │┌Hostname and Domain Name───────────────────────────────────┐│ ││minas-tirith▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ valinor▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ││ <== ││[x] Assign Hostname to Loopback IP ││ ││Set Hostname via DHCP no▒▒▒▒▒▒▒▒▒↓ ││
The help says:
││Enter the short name for this computer (e.g. mymachine) and the DNS domain ┬│ ││(e.g. example.com) that it belongs to. The domain is especially important if││ ││this computer is a mail server. You can view the hostname of you computer ││ ││using the hostname command.
So at some point in time at least it was possible to define the domain name in yast. Why not now, what has changed? (honest question). I assume that if the option has been removed intentionally, it is no longer possible to set it up.
e.g. boo#821599 and boo#1099464 AFAICR postfix as well as sendmail uses gethostbyaddr(3) to ask for the FQDN of local system for (one or more) of its network device(s). The resolution depends on /etc/host.conf, /etc/nsswitch.conf, and /etc/resolv.conf together with /etc/hosts in the default configuration. On static network configuration (e.g. with wicked) the FQDNs of the local system can be added for one or more of its network devices into /etc/hosts. On a mobile system (e.g. NetworkManager) I'd prefer not do this but let do the job the NetworkManager and its DHCP part. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
participants (15)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
Carlos E. R. -
Darryl Gregorash -
Dave Howorth -
David C. Rankin -
Dr. Werner Fink -
Felix Miata -
James Knott -
Knurpht-openSUSE -
Patrick Shanahan -
Per Jessen -
Robert T Hardy -
Simon Becherer