Project

General

Profile

Misc #16515

one of authoritative name server of ruby-lang.org "pichu.netlab.jp" not responding DNS query

Added by meta@vmeta.jp (Koichiro Iwao) 5 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
[ruby-core:96925]

Description

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,

#1

Updated by meta@vmeta.jp (Koichiro Iwao) 5 months ago

  • Description updated (diff)
#2

Updated by jeremyevans0 (Jeremy Evans) 5 months ago

  • Backport deleted (2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN)
  • Tracker changed from Bug to Misc

Updated by meta@vmeta.jp (Koichiro Iwao) 4 months ago

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

#4

Updated by meta@vmeta.jp (Koichiro Iwao) 4 months ago

  • Subject changed from lazy DNS response (sometimes no response at all) pichu.netlab.jp (ruby-lang.org NS) to one of authoritative name server of ruby-lang.org "pichu.netlab.jp" not responding DNS query

Updated by shugo (Shugo Maeda) 4 months ago

  • Status changed from Open to Closed

Sorry for the delay.
We have changed the secondary DNS server of ruby-lang.org to ns.tokyo.netlab.jp.

Updated by meta@vmeta.jp (Koichiro Iwao) 4 months ago

Also, support.netlab.jp is not responding IPv6 DNS query.

% drill support.netlab.jp AAAA
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 45087
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; support.netlab.jp.   IN      AAAA

;; ANSWER SECTION:
support.netlab.jp.      569     IN      AAAA    2001:268:306::53:1
% drill www.ruby-lang.org @2001:268:306::53:1
Error: error sending query: Could not send or receive, because of network error
% drill www.ruby-lang.org @2001:268:306::53:1
Error: error sending query: Could not send or receive, because of network error
% drill www.ruby-lang.org @2001:268:306::53:1
Error: error sending query: Could not send or receive, because of network error

If support.netlab.jp is not IPv6 reachable, you should remove AAAA record of support.netlab.jp.

Updated by naruse (Yui NARUSE) 4 months ago

Just FYI, now we use Route53 as NS:

% dig ruby-lang.org NS

; <<>> DiG 9.10.6 <<>> ruby-lang.org NS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62218
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ruby-lang.org.         IN  NS

;; ANSWER SECTION:
ruby-lang.org.      51  IN  NS  ns-783.awsdns-33.net.
ruby-lang.org.      51  IN  NS  ns-1439.awsdns-51.org.
ruby-lang.org.      51  IN  NS  ns-1617.awsdns-10.co.uk.
ruby-lang.org.      51  IN  NS  ns-458.awsdns-57.com.

;; Query time: 16 msec
;; SERVER: 10.0.24.254#53(10.0.24.254)
;; WHEN: Fri Feb 14 18:51:09 JST 2020
;; MSG SIZE  rcvd: 168

Updated by meta@vmeta.jp (Koichiro Iwao) 4 months ago

Nice to hear that 🎉

Also available in: Atom PDF