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))

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

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

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 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 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

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 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

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

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

Andrei Borzenkov wrote:

On Wed, May 8, 2019 at 10:29 AM Per Jessen 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

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 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 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

On Wed, May 8, 2019 at 11:41 AM Per Jessen 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

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

Andrei Borzenkov wrote:

On Wed, May 8, 2019 at 2:30 PM Per Jessen 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 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

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

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

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

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 Wed, 08 May 2019 20:36:10 +0200 Per Jessen 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

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 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 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

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

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

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

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

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

* Carlos E. R. [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 [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 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

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

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

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

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

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

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

* Carlos E. R. [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 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: 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 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... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 7 May 2019 23:50:08 +0200 "Carlos E. R." 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

On Wed, May 8, 2019 at 2:18 PM Per Jessen 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

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

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 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

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

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

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 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

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

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

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 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

...

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

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 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

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

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

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

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

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

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

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 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 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 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 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

* James Knott [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 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

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

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 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 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