Ruediger Meier wrote:

On Friday 12 August 2016, Per Jessen wrote:

...

I have a cron job running every 20 minutes monitoring a temperature sensor for minor changes in trend up/down. This has been running for a few months.

Today at 1521 I got a warning that the trend dad changed to slightly upward. The next one failed on a DNS issue.

The puzzle:

wget -nd http://office20.local.net:4444/--slope--/1.2.3.4/0 --2016-08-12 20:38:24-- http://office20.local.net:4444/--slope--/1.2.3.4/0 Resolving office20.local.net (office20.local.net)... failed: Name or service not known. wget: unable to resolve host address ‘office20.local.net’

So clearly "office20.local.net" does not resolve. Except:

...

host office20.local.net

office20.local.net has address 192.168.3.20

...

ping office20.local.net

PING office20.local.net (192.168.3.20) 56(84) bytes of data. 64 bytes from office20.local.net (192.168.3.20): icmp_seq=1 ttl=64 time=0.029 ms 64 bytes from office20.local.net (192.168.3.20): icmp_seq=2 ttl=64 time=0.040 ms

...

dig office20.local.net a

; <<>> DiG 9.9.4-rpz2.13269.14-P2 <<>> office20.local.net a ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30802 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;office20.local.net. IN A

;; ANSWER SECTION: office20.local.net. 86400 IN A 192.168.3.20

So clearly "office20.local.net" _does_ resolve. Except in wget.

No changes were applied to this system for at least a month, likely longer.

Why can't wget resolve the address when others have no problem?

office20.local.net

Do you really own 'local.net'?

Hehe, nono. That one is only used locally on 192.168.0.0/16.

Some programs may do the lookup manually without glibc, ignoring /etc/resolv.conf. I know that postfix does that by default.

Are you sure? At least it couldn't do it without /etc/resolv.conf, and I'm pretty certain my installations also use /etc/hosts (which is handy for overrides).

You should better not use domains which you don't own! Or at least a top level domain which does not exist (hard to find one nowadays.)

I agree completely, but 'local.net' has been used internally for maybe 15 years, and changing it to something truly local would mean a lot of checking and double-checking.

Could be that you are using another unwanted nameserver which you have not configured to serve your own local.net. (autoconfig/dhcp),

Check, /etc/resolv.conf is fine.

Some other possibilites: - nscd issues?

I did think of that one, and did "nscd -i hosts" - however, ping will also use nscd, and that works.

- Maybe wget handles ipv4/v6 stupidly? Try wget -4.

Ah, forgot about that one. Yes! that was it. What remains of the puzzle - why did this suddenly start yesterday at 15:21 after running fine since April? I swear that machine was not touched. I don't really want to add that '-4' as it shouldn't be necessary. Anyway, thanks for mentioning that. I'll have to look a little closer at wget. -- Per Jessen, Zürich (17.1°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

...

office20.local.net

Do you really own 'local.net'?

Hehe, nono. That one is only used locally on 192.168.0.0/16.

No its not: # ping office20.local.net PING office20.local.net (69.172.201.153) 56(84) bytes of data. ^C --- office20.local.net ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 11086ms # dig office20.local.net ; <<>> DiG 9.9.6-P1 <<>> office20.local.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4399 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;office20.local.net. IN A ;; ANSWER SECTION: office20.local.net. 279 IN A 69.172.201.153 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sat Aug 13 07:41:35 EDT 2016 ;; MSG SIZE rcvd: 63 I'm using dnsmasq. -- 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 Saturday 13 August 2016, Per Jessen wrote:

Anton Aylward wrote:

...

...

...

office20.local.net

Do you really own 'local.net'?

Hehe, nono. That one is only used locally on 192.168.0.0/16.

No its not:

Well, yes it is - locally in the DNS view for 192.168.0.0/16. Sure, someone actually has "local.net" registered, but I'm not concerned with that.

local.net is available for selling. You could buy it to be on the safe side without changing your local DNS setup ;) see, http://local.net/ Ohh, hope you are able to use that link from within your network ;) cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Quoting IEEE alias :

Quoting Per Jessen :

...

I have a cron job running every 20 minutes monitoring a temperature sensor for minor changes in trend up/down. This has been running for a few months.

Today at 1521 I got a warning that the trend dad changed to slightly upward. The next one failed on a DNS issue.

The puzzle:

wget -nd http://office20.local.net:4444/--slope--/1.2.3.4/0 --2016-08-12 20:38:24-- http://office20.local.net:4444/--slope--/1.2.3.4/0 Resolving office20.local.net (office20.local.net)... failed: Name or service not known. wget: unable to resolve host address ‘office20.local.net’

So clearly "office20.local.net" does not resolve. Except:

and on my machine, see below. local.net is a real domain name, so how it resolves will be highly implementation dependent. IIRC, Postfix always goes directly to DNS, ignoring /etc/hosts. I use .local for my LAN with 192.168.x.x addresses. So far it hasn't bit me. At the moment, away from my home network, .local does not resolve. IIRC, there is a TLD that is reserved for private networks, maybe .localdomain?

[snip] See https://tools.ietf.org/html/draft-chapin-rfc2606bis-00 It reserves: .local, .localdomain, .domain, .lan, .home, .host, .corp. However, apparently Apple networks reserve .local for a non-conforming use. I use .lan (i.e. /etc/HOSTS is viajero.bearhouse.lan on this laptop). HTH, Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Friday 12 August 2016, Jeffrey L. Taylor wrote:

Quoting Per Jessen :

...

I have a cron job running every 20 minutes monitoring a temperature sensor for minor changes in trend up/down. This has been running for a few months.

Today at 1521 I got a warning that the trend dad changed to slightly upward. The next one failed on a DNS issue.

The puzzle:

wget -nd http://office20.local.net:4444/--slope--/1.2.3.4/0 --2016-08-12 20:38:24-- http://office20.local.net:4444/--slope--/1.2.3.4/0 Resolving office20.local.net (office20.local.net)... failed: Name or service not known. wget: unable to resolve host address ‘office20.local.net’

So clearly "office20.local.net" does not resolve. Except:

and on my machine, see below. local.net is a real domain name, so how it resolves will be highly implementation dependent. IIRC, Postfix always goes directly to DNS, ignoring /etc/hosts. I use .local for my LAN with 192.168.x.x addresses. So far it hasn't bit me.

I'm also using .local since years but I've noticed already that it will bite you if mDNS, avahi, etc. is involved. .local is very very special and maybe the worst domain you could use for local DNS. https://en.wikipedia.org/wiki/.local It's on my TODO since years to find something better than .local but as long as I blacklist any avahi/mDNS, stuff it works. BTW suse default was .site for a long time but it's also an existing toplevel domain nowadays. cu, Rudi

At the moment, away from my home network, .local does not resolve. IIRC, there is a TLD that is reserved for private networks, maybe .localdomain?

HTH, Jeffrey

$ dig local.net

; <<>> DiG 9.9.4-rpz2.13269.14-P2 <<>> local.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27256 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;local.net. IN A

;; ANSWER SECTION: local.net. 299 IN A 69.172.201.153

;; Query time: 93 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Aug 12 16:12:51 CDT 2016 ;; MSG SIZE rcvd: 54

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Saturday 13 August 2016, Anton Aylward wrote:

On 08/12/2016 09:02 PM, Ruediger Meier wrote:

...

It's on my TODO since years to find something better than .local but as long as I blacklist any avahi/mDNS, stuff it works.

As regular readers will entice, I won my own domian. My solution to the above is to have a subdomain "HOME." within that for which my local machine is the authority.

Yes .home or .lan might be a better choice than .local. So .home and .lan are widely used by router manufacturers as factory default, since there is no better choice for such a default. FYI see paragraph "Name Collision Concerns Impede Delegation" here: https://icannwiki.com/.home But IMO the best practice would be to use a subdomain of your real domain, like .local.company.org, see the first answer plus comments here: http://serverfault.com/questions/17255/top-level-domain-domain-suffix-for-pr... cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Jeffrey L. Taylor wrote:

Quoting Per Jessen :

...

I have a cron job running every 20 minutes monitoring a temperature sensor for minor changes in trend up/down. This has been running for a few months.

Today at 1521 I got a warning that the trend dad changed to slightly upward. The next one failed on a DNS issue.

The puzzle:

wget -nd http://office20.local.net:4444/--slope--/1.2.3.4/0 --2016-08-12 20:38:24-- http://office20.local.net:4444/--slope--/1.2.3.4/0 Resolving office20.local.net (office20.local.net)... failed: Name or service not known. wget: unable to resolve host address ‘office20.local.net’

So clearly "office20.local.net" does not resolve. Except:

and on my machine, see below. local.net is a real domain name, so how it resolves will be highly implementation dependent. IIRC, Postfix always goes directly to DNS, ignoring /etc/hosts.

How the resolver behaves depends on /etc/nsswitch.conf.

I use .local for my LAN with 192.168.x.x addresses. So far it hasn't bit me. At the moment, away from my home network, .local does not resolve. IIRC, there is a TLD that is reserved for private networks, maybe .localdomain?

I think '.site' used to be, but that was turned into a public TLD too. -- Per Jessen, Zürich (17.2°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