DNS格式錯誤

Question

我得到一個與DNS格式錯誤。任何想法是什麼？

Client /root #dig @2029:192:168:119::170 ns udp.net +bufsize=50000 +tries=10 ns +noqr 
;; Warning, extra type option 

; <<>> DiG 9.3.1 <<>> @2029:192:168:119::170 ns udp.net +bufsize=50000 +tries=10 ns +noqr 
; (1 server found) 
;; global options: printcmd 
;; Got answer: 
;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 55070 
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 

;; OPT PSEUDOSECTION: 
; EDNS: version: 0, flags:; udp: 50000 
;; QUESTION SECTION: 
;udp.net.   IN NS 

;; Query time: 0 msec 
;; SERVER: 2029:192:168:119::170#53(2029:192:168:119::170) 
;; WHEN: Thu Nov 8 14:49:08 2012 
;; MSG SIZE rcvd: 36 

無法在Google上找到任何有用的材料。

Answer 1

我一直沒能敲定的確切原因，但也有一對夫婦已經從研究上來的主題我做：

• 這似乎是經常被歸咎於錯誤配置負載均衡器。
• 這似乎只發生在EDNS記錄發送。

例如，一些樣品：

$ dig AAAA gtm03.wallst.com @209.234.224.40 

; <<>> DiG 9.9.2 <<>> AAAA gtm03.wallst.com @209.234.224.40 
;; global options: +cmd 
;; Got answer: 
;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 29393 
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 
;; WARNING: recursion requested but not available 

;; OPT PSEUDOSECTION: 
; EDNS: version: 0, flags:; udp: 4096 
;; QUESTION SECTION: 
;gtm03.wallst.com.    IN  AAAA 

;; Query time: 80 msec 
;; SERVER: 209.234.224.40#53(209.234.224.40) 
;; WHEN: Fri Mar 15 02:51:24 2013 
;; MSG SIZE rcvd: 45 

$ dig +noedns AAAA gtm03.wallst.com @209.234.224.40 

; <<>> DiG 9.9.2 <<>> +noedns AAAA gtm03.wallst.com @209.234.224.40 
;; global options: +cmd 
;; Got answer: 
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23716 
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 
;; WARNING: recursion requested but not available 

;; QUESTION SECTION: 
;gtm03.wallst.com.    IN  AAAA 

;; AUTHORITY SECTION: 
wallst.com.    300  IN  SOA  dns01.wallst.com. dnsadmin.wallst.com. 2911145386 7200 3600 86313600 300 

;; Query time: 82 msec 
;; SERVER: 209.234.224.40#53(209.234.224.40) 
;; WHEN: Fri Mar 15 02:51:38 2013 
;; MSG SIZE rcvd: 85 

我得到在不同的主機相同的輸出，在兩個不同的大洲。

就我所知，這是您查詢的服務器的錯，而不是您自己的解析器。