Hello Franky, On 27.02.2017 12:04, battossai via Unbound-users wrote: > Hi Carsten, > > Thank you for your information. > But the real issue is unbound unable to resolv an .id domain. > Any other solutions ? >
does not seem to be a general Unbound issue, my Unbound resolves the .id domain without issues. $ dig polri.go.id ; <<>> DiG 9.10.4-P6-RedHat-9.10.4-4.P6.fc25 <<>> polri.go.id ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10130 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;polri.go.id. IN A ;; ANSWER SECTION: polri.go.id. 38400 IN A 120.29.225.249 ;; Query time: 2812 msec ;; SERVER: 2a01:198:2b6::22#53(2a01:198:2b6::22) ;; WHEN: Mo Feb 27 12:49:18 CET 2017 ;; MSG SIZE rcvd: 56 However the domain "polri.go.id" has several errors, see <https://zonemaster.net/test/774bd160515887e1> and <http://dnsviz.net/d/polri.go.id/dnssec/> If you have issues resolving this domain, it is a problem of this domain, not of the Unbound DNS resolver. Best regards Carsten
