[Pdns-users] Contact the reverse of the PowerDNS recursor
Hello, all NSD PowerDNS recursor 3.7.2, only for a specific domain is set to another want us to do so, but reverse only returned calls. The corresponding forward-zone parameter and it's thought that? $ grep -v -e "#" -e "^$" /etc/powerdns/recursor.conf allow-from=127.0.0.0/8, 10.0.0.0/8, 100.64.0.0/10, 169.254.0.0/16, 192.168.0.0/16, 172.16.0.0/12, ::1/128, fc00::/7, fe80::/10, 2000::/3 any-to-tcp=yes disable-packetcache=yes experimental-api-key=changeme experimental-webserver=yes forward-zones=kometch.local=127.0.0.1:10053 hint-file=/etc/powerdns/named.root max-mthreads=4096 query-local-address6=:: setgid=pdns setuid=pdns If the PowerDNS recursor: $ dig -x 240b:10:a8c0:a10:10::254 ; <<>> DiG 9.9.5-9-Debian <<>> -x 240b:10:a8c0:a10:10::254 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30873 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;4.5.2.0.0.0.0.0.0.0.0.0.0.1.0.0.0.1.a.0.0.c.8.a.0.1.0.0.b.0.4.2.ip6.arpa. IN PTR ;; AUTHORITY SECTION: 1.0.0.b.0.4.2.ip6.arpa. 2998IN SOA ns1.jpne.co.jp. nsadmin.jpne.co.jp. 2011053101 10800 3600 360 3600 ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Apr 29 18:55:44 JST 2015 ;; MSG SIZE rcvd: 148 $ dig -x 192.168.1.254 ; <<>> DiG 9.9.5-9-Debian <<>> -x 192.168.1.254 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28950 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;254.1.168.192.in-addr.arpa.IN PTR ;; AUTHORITY SECTION: 168.192.in-addr.arpa. 2997IN SOA localhost. root. 1 604800 86400 2419200 604800 ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Apr 29 18:55:58 JST 2015 ;; MSG SIZE rcvd: 95 If unbound: # dig -x 240b:10:a8c0:a10:10::254 ; <<>> DiG 9.9.4-RedHat-9.9.4-18.el7_1.1 <<>> -x 240b:10:a8c0:a10:10::254 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8950 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1280 ;; QUESTION SECTION: ;4.5.2.0.0.0.0.0.0.0.0.0.0.1.0.0.0.1.a.0.0.c.8.a.0.1.0.0.b.0.4.2.ip6.arpa. IN PTR ;; ANSWER SECTION: 4.5.2.0.0.0.0.0.0.0.0.0.0.1.0.0.0.1.a.0.0.c.8.a.0.1.0.0.b.0.4.2.ip6.arpa. 300 IN PTR ubuntu-virt.kometch.local. ;; Query time: 0 msec ;; SERVER: 192.168.122.249#53(192.168.122.249) ;; WHEN: Wed Apr 29 18:54:52 JST 2015 ;; MSG SIZE rcvd: 140 # dig -x 192.168.1.254 ; <<>> DiG 9.9.4-RedHat-9.9.4-18.el7_1.1 <<>> -x 192.168.1.254 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55455 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1280 ;; QUESTION SECTION: ;254.1.168.192.in-addr.arpa.IN PTR ;; ANSWER SECTION: 254.1.168.192.in-addr.arpa. 300 IN PTR ubuntu-virt.kometch.local. ;; Query time: 1 msec ;; SERVER: 192.168.1.249#53(192.168.1.249) ;; WHEN: Wed Apr 29 18:56:10 JST 2015 ;; MSG SIZE rcvd: 96 I want pointed if I have been mistaken as any. My best regards. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] API issue. 400 Bad Request
Hello Christian,
> In some versions, '400 Bad Request’ may also happen because of wrong
> authentication (i.e. wrong X-API-Key). Please double check the API Key.
recursor.conf on which was initialized, and has been set again following
parameters,
the results did not change.
experimental-api-key=changeme
experimental-webserver=yes
Is this Will such that it should be reported as issue?
Best regards.
> 2015/03/05 21:23、Christian Hofstaedtler
> のメール：
>
> Hi,
>
>> On 05 Mar 2015, at 13:16, kometch wrote:
> [..]
>> I have used to compile the PowerDNS recursor 3.7.1 on an ARM board from a
>> source that Cubietruck.
>
> [..]
>
>> $ curl -v -H 'X-API-Key: changeme' http://127.0.0.1:8082/servers/localhost |
>> jq .
>> * Hostname was NOT found in DNS cache
>> * Trying 127.0.0.1...
>> % Total% Received % Xferd Average Speed TimeTime Time Current
>>Dload Upload Total SpentLeft Speed
>> 0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
>> 0* Connected to 127.0.0.1 (127.0.0.1) port 8082 (#0)
>>> GET /servers/localhost HTTP/1.1
>>> User-Agent: curl/7.35.0
>>> Host: 127.0.0.1:8082
>>> Accept: */*
>>> X-API-Key: changeme
>>>
>> < HTTP/1.1 400 Bad Request
>> < Content-Type: 11
>> * no chunk, no close, no size. Assume close to signal end
>> <
>> { [data not shown]
>> 100110110 0976 0 --:--:-- --:--:-- --:--:--
>> 1100
>> * Closing connection 0
>> parse error: Invalid numeric literal at line 1, column 4
>
> In some versions, '400 Bad Request’ may also happen because of wrong
> authentication (i.e. wrong X-API-Key). Please double check the API Key.
>
> OTOH, I’m not sure anybody ever tested API on ARM, so maybe you found a bug.
>
> Best,
> Christian
>
>
>
> --
> Christian Hofstaedtler / Deduktiva GmbH (FN 418592 b, HG Wien)
> www.deduktiva.com / +43 1 353 1707
>
>
>
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] API issue. 400 Bad Request
Hello All,
I have used to compile the PowerDNS recursor 3.7.1 on an ARM board from a
source that Cubietruck.
Below the place you are trying to obtain statistical information
by API on which has been set to PowerDNS recursor to reference,
become Bad Request problem has occurred.
$ curl -v -H 'X-API-Key: changeme' http://127.0.0.1:8082/servers/localhost | jq
.
* Hostname was NOT found in DNS cache
* Trying 127.0.0.1...
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0*
Connected to 127.0.0.1 (127.0.0.1) port 8082 (#0)
> GET /servers/localhost HTTP/1.1
> User-Agent: curl/7.35.0
> Host: 127.0.0.1:8082
> Accept: */*
> X-API-Key: changeme
>
< HTTP/1.1 400 Bad Request
< Content-Type: 11
* no chunk, no close, no size. Assume close to signal end
<
{ [data not shown]
100110110 0976 0 --:--:-- --:--:-- --:--:-- 1100
* Closing connection 0
parse error: Invalid numeric literal at line 1, column 4
When you source compiled with CentOS6 the problem did not occur.
Is it just a matter of that environment is too special?
Verification environment:
$ uname -a
Linux dns02 3.19.0-rc5-cubieboard #6 SMP Fri Jan 23 06:17:54 EST 2015 armv7l
armv7l armv7l GNU/Linux
$
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename: trusty
$ sudo lsof -i :8082
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pdns_recu 14988 pdns 32u IPv4 3789953 0t0 TCP localhost:8082 (LISTEN)
It has been confirmed that the iptable also ufw also not running.
How can I solve this problem, and how do I to?
Best regards.
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
