Project

General

Profile

Actions
Copy link

Bug #8204

closed

unbound returning funny ip instead of nothing

Added by Tom Mü-Ko over 6 years ago. Updated over 6 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
12/12/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

where I ask unbount on pfSense for an IP, i.e. 1.1.1.1 it returns 62.138.239.45, 62.138.238.45:

dig @127.0.0.1 1.1.1.1 any

; <<>> DiG 9.11.2 <<>> @127.0.0.1 1.1.1.1 any
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30070
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;1.1.1.1.            IN    ANY

;; ANSWER SECTION:
1.1.1.1.        3600    IN    A    62.138.239.45
1.1.1.1.        3600    IN    A    62.138.238.45

;; Query time: 59 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Dec 12 16:54:58 CET 2017
;; MSG SIZE  rcvd: 68

This is the answer from a bind9

;; QUESTION SECTION:
;1.1.1.1.            IN    ANY

;; AUTHORITY SECTION:
.            10789    IN    SOA    a.root-servers.net. nstld.verisign-grs.com. 2017121200 1800 900 604800 86400

;; Query time: 0 msec

Actions
Copy link
 #1

Updated by Tom Mü-Ko over 6 years ago

close

Actions
Copy link
 #2

Updated by Tom Mü-Ko over 6 years ago

please close the ticket. Problem ist DNS of Provider.

Actions
Copy link
 #3

Updated by Jim Pingle over 6 years ago

  • Status changed from New to Not a Bug
  • Affected Version deleted (2.4.2)

It would appear that either you have forwarding mode on and your upstream server returns its own address instead of NXDOMAIN or something is intercepting your DNS queries and doing the same. Nothing in unbound would do that unless you manually went out of your way to setup an answer for that query.

Also, that query is bogus as you would not find an A record for an IP address, you'd have to perform a reverse lookup (e.g. dig -x)

Either way, not a bug. Follow up on the forum, mailing list, or Reddit for help tracking down your problem.

Actions
Copy link

Also available in: Atom PDF