问题原文
原帖链接 · RGBD · CC BY-SA 3.0
Long story short.
dig c.cx
returns
; <<>> DiG 9.11.0-P2 <<>> c.cx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32806
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;c.cx. IN A
;; ANSWER SECTION:
c.cx. 6903 IN A 0.0.0.0
;; Query time: 90 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Feb 06 22:33:08 +03 2017
;; MSG SIZE rcvd: 49
i. e. address 0.0.0.0.
Questions:
- does it have any special meaning?
- is it legal (are there any limitations on what addresses dns record can contain)?
社区高分解答
原帖链接 · TOP · CC BY-SA 4.0
Famously it was used to shut down parler.com by the domain registrar epik
$ dig @NS3.EPIK.COM parler.com
; <<>> DiG blah blah blah <<>> @NS3.EPIK.COM parler.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43362
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;parler.com. IN A
;; ANSWER SECTION:
parler.com. 300 IN A 0.0.0.0
The result was to serve an error page from the local web server.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
