You are not logged in.

#1 2016-12-23 14:02:32

hwa
Member
Registered: 2014-03-12
Posts: 10

dig v9.11 gives error:"WARNING: recursion requested but not available"

All,
Something has changed in how dig v9.11 handles queries in my intranet. All previous versions, eg. 9.10.4-P3, work well and resolves any host thru our internal AD DNS. I verified the behaviour by downgrading bind-tools to a previous version I had in cache.

Example (shortened for readability):

# dig @192.168.248.19 mail.google.com

; <<>> DiG 9.10.4-P3 <<>> @192.168.248.19 mail.google.com

;; ANSWER SECTION:
mail.google.com.	77173	IN	CNAME	googlemail.l.google.com.
googlemail.l.google.com. 58	IN	A	216.58.211.133

Now, dig 9.11 errors out:

# dig @192.168.248.19 www.google.com

; <<>> DiG 9.11.0-P1 <<>> @192.168.248.19 www.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 15433
;; 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
; COOKIE: c17ecb6441f2e12b (echoed)
;; QUESTION SECTION:
;www.google.com.			IN	A

DNS is running on W2008R2, recursion is enabled, and all other servers, be it Windows or Centos[6/7], do resolve both internal and external addresses A-OK. It's just this one and only Arch that gives trouble. On the other hand, the other Arch I have in DMZ and which is running a DNS (bind) of its own has no trouble at all.

The question is why this one Arch behaves like this and why previous dig works OK?

Offline

Board footer

Powered by FluxBB