What steps will reproduce the problem?
1. See belows
2.
3.
What is the expected output? What do you see instead?
I expect the DNS could resolve the website correctly.
What version of the product are you using? On what operating system?
LINUX
Please provide any additional information below.
STEPS:
linux-01pt:~ #
linux-01pt:~ #
linux-01pt:~ # date
Fri Jun 27 18:59:47 CST 2014
linux-01pt:~ # nslookup www.twitter.com
;; connection timed out; no servers could be reached
linux-01pt:~ # nslookup www.twitter.com 202.96.209.5
Server: 202.96.209.5
Address: 202.96.209.5#53
Non-authoritative answer:
Name: www.twitter.com
Address: 59.24.3.173
linux-01pt:~ # nslookup www.twitter.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: www.twitter.com
Address: 59.24.3.173
linux-01pt:~ # dig @8.8.8.8 www.twitter.com
; <<>> DiG 9.9.3-rpz2+rl.156.01-P2 <<>> @8.8.8.8 www.twitter.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46978
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.twitter.com. IN A
;; ANSWER SECTION:
www.twitter.com. 300 IN A 37.61.54.158
;; Query time: 26 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Jun 27 19:00:49 CST 2014
;; MSG SIZE rcvd: 64
linux-01pt:~ # dig @8.8.8.8 www.twitter.com +tcp
; <<>> DiG 9.9.3-rpz2+rl.156.01-P2 <<>> @8.8.8.8 www.twitter.com +tcp
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
linux-01pt:~ # dig @42.120.21.30 www.twitter.com +tcp
;; Connection to 42.120.21.30#53(42.120.21.30) for www.twitter.com failed:
connection refused.
linux-01pt:~ # dig @42.120.21.30 www.twitter.com
; <<>> DiG 9.9.3-rpz2+rl.156.01-P2 <<>> @42.120.21.30 www.twitter.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
linux-01pt:~ # nslookup www.twitter.com 42.120.21.30
;; connection timed out; no servers could be reached
Original issue reported on code.google.com by zhoujion...@gmail.com on 27 Jun 2014 at 11:05
Original issue reported on code.google.com by
zhoujion...@gmail.com
on 27 Jun 2014 at 11:05