[ruby-core:96925] [Ruby master Bug#16515] lazy DNS response (sometimes no response at all) pichu.netlab.jp (ruby-lang.org NS)

[ruby-core:96925] [Ruby master Bug#16515] lazy DNS response (sometimes no response at all) pichu.netlab.jp (ruby-lang.org NS)

[meta]

Issue #16515 has been reported by meta@vmeta.jp (Koichiro Iwao).

----------------------------------------
Bug #16515: lazy DNS response (sometimes no response at all) pichu.netlab.jp (ruby-lang.org NS)
https://bugs.ruby-lang.org/issues/16515

* Author: meta@vmeta.jp (Koichiro Iwao)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
I'm reporting issue about ruby-lang.org network infrastructure. If here's not the place to report such issues,
I'd appreciate if let me know appropriate place to report such issues.

I've notified one of name servers of ruby-lang.org seems not working properly. 
Two name servers are registered as authority name servers of ruby-lang.org.
* support.netlab.jp
* pichu.netlab.jp

The latter one `pichu.netlab.jp` is tardy in its DNS response. It often cause timeouts.

```
% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error

% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error

% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error
```

The other one `support.netlab.jp` seems to be working fine.

```
% drill docs.ruby-lang.org @support.netlab.jp
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 31189
;; flags: qr aa rd ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; docs.ruby-lang.org.  IN      A

;; ANSWER SECTION:
docs.ruby-lang.org.     600     IN      CNAME   dualstack.m.shared.global.fastly.net.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 62 msec
;; SERVER: 153.246.96.163
;; WHEN: Fri Jan 17 18:48:47 2020
;; MSG SIZE  rcvd: 86
```

This causes faliure in name resolution when my local dns cache is expired.
Specifically, name resolution will fail at 50% chance every 300 minutes.


I've performed above `drill` test via 3 different ISPs and got the same result.
So I suppose this is your NaCl's name server side issue.

Thanks,



-- 
https://bugs.ruby-lang.org/

[ruby-core:96987] [Ruby master Misc#16515] lazy DNS response (sometimes no response at all) pichu.netlab.jp (ruby-lang.org NS)

[meta]

Issue #16515 has been updated by meta@vmeta.jp (Koichiro Iwao).


```
[icepick ~]% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error
[icepick ~]% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error
[icepick ~]% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error
```

It appears that `pichu.netlab.jp` has been down for a week.

----------------------------------------
Misc #16515: lazy DNS response (sometimes no response at all) pichu.netlab.jp (ruby-lang.org NS)
https://bugs.ruby-lang.org/issues/16515#change-84045

* Author: meta@vmeta.jp (Koichiro Iwao)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
I'm reporting issue about ruby-lang.org network infrastructure. If here's not the place to report such issues,
I'd appreciate if let me know appropriate place to report such issues.

I've notified one of name servers of ruby-lang.org seems not working properly. 
Two name servers are registered as authority name servers of ruby-lang.org.
* support.netlab.jp
* pichu.netlab.jp

The latter one `pichu.netlab.jp` is tardy in its DNS response. It often cause timeouts.

```
% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error

% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error

% drill docs.ruby-lang.org @pichu.netlab.jp
Error: error sending query: Could not send or receive, because of network error
```

The other one `support.netlab.jp` seems to be working fine.

```
% drill docs.ruby-lang.org @support.netlab.jp
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 31189
;; flags: qr aa rd ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; docs.ruby-lang.org.  IN      A

;; ANSWER SECTION:
docs.ruby-lang.org.     600     IN      CNAME   dualstack.m.shared.global.fastly.net.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 62 msec
;; SERVER: 153.246.96.163
;; WHEN: Fri Jan 17 18:48:47 2020
;; MSG SIZE  rcvd: 86
```

This causes faliure in name resolution when my local dns cache is expired.
Specifically, name resolution of `docs.ruby-lang.org` will fail at 50% chance every 600 minutes.

I've performed above `drill` test via 3 different ISPs and got the same result.
So I suppose this is your NaCl's name server side issue.

Thanks,



-- 
https://bugs.ruby-lang.org/