Hi!
I'm experiencing strange problem with my superslave powerdns version 3.4.2
using sqlite3 backend.
I have one large zone, that has many NS records, about 200 and the problem
is, that this zone is not created on the superslave server automatically.
Unable to find backend willing to host zone.n
Nikolaos Milas wrote:
> Despite the fact that PowerDNS with LDAP backend seems underutilized and LDAP
> backend development has been neglected for years (due to lack of interest and
> private investment), I see much potential in it, as you, and it would be worth
> trying to revive it.
Yes, IMHO it
> This version of PowerDNS we use is PowerDNS Authoritative Server 3.4.2.
> This is the entire pdns.conf file in /etc/powerdns:
>
> http://pastebin.com/14LqMbLp
Line 623 has crud behind it; that better not be in the configuration.
Also show us the *exact* curl command you're using from the
comma
On 4/3/2015 8:17 μμ, Michael Ströder wrote:
This sounds a bit like a special case for split horizon DNS.
Precisely.
I promised to configure a demo using powerdns with LDAP backend for this based
on OpenLDAP ACLs and several powerdns instances using different LDAP identities.
Feel free to co
Tried the config lines from this post (
http://jpmens.net/2015/01/09/a-look-at-the-powerdns-rest-api/) and the curl
commands give no errors anymore. But the problem remains, that nothing is
listening on 8081. So the curl in the command line returns nothing.
2015-03-04 20:09 GMT+01:00 Melvin Mughal
This version of PowerDNS we use is PowerDNS Authoritative Server 3.4.2.
This is the entire pdns.conf file in /etc/powerdns:
http://pastebin.com/14LqMbLp
2015-03-04 18:30 GMT+01:00 AJ McKee :
> Weird...
>
> For sure its not hitting the API service, its apache. Could you post
> version and config
Nikolaos Milas wrote:
> On 3/3/2015 2:44 μμ, Nikolaos Milas wrote:
>
>> Ideally, we would like pdns to be configured to reply to requests *for
>> particular names* (under a specific subdomain, say internal.example.com) by
>> only providing records (if available, otherwise no results) and hide
Weird...
For sure its not hitting the API service, its apache. Could you post
version and config information please, removing any identifiable or
security information and i will test your config on a vm and let you know
AJ
On 4 March 2015 at 16:27, Melvin Mughal wrote:
> Yes, already in the sam
Yes, already in the same config:
# Enable and config API
experimental-json-interface=yes
experimental-api-key=NwY>kpVMMuGEaDH8ib (not the real API key)
webserver=yes
2015-03-04 17:20 GMT+01:00 AJ McKee :
> You will also have to ensure have been set in config.
>
> experimental-json-interface=y
Local port doesn't change anything and nc localhost returns nothing. To
configure the port, I added these lines:
*# IP Address of web server to listen on*
*webserver-address=127.0.0.1*
*# Port of web server to listen on*
*webserver-port=8081*
*# Web server access is only allowed from these sub
You will also have to ensure have been set in config.
experimental-json-interface=yes
experimental-api-key=changeme
On 4 March 2015 at 16:15, Melvin Mughal wrote:
> Local port doesn't change anything and nc localhost returns nothing. To
> configure the port, I added these lines:
>
> *# IP Addr
Yes because you are telling curl to use port 8081,
try just curl hostname:8081 and you commands, i.e. remove --local-port
Failing that, try nc localhost 8081 and simulate a HTTP request to the
service.
AJ
On 4 March 2015 at 15:41, Melvin Mughal wrote:
> Yep, tried it. Put it in the config on
--local-port specifies which OUTGOING PORT will curl use. not the
destination port.
On 03/04/15 16:41, Melvin Mughal wrote:
> Yep, tried it. Put it in the config on 8081 and also tried 8082. But
> then we get the 'curl: (45) bind failed with errno 48: Address already
> in use' response back. So n
Yep, tried it. Put it in the config on 8081 and also tried 8082. But then
we get the 'curl: (45) bind failed with errno 48: Address already in use'
response back. So no luck with that :(
2015-03-04 16:31 GMT+01:00 AJ McKee :
> Hi Melvin,
>
> Seems you are talking to your local apache,
>
> Try ho
Hi Melvin,
Seems you are talking to your local apache,
Try hostname:8081 for your request, unless of course you have gone through
the trouble of reverse proxying the pdns instance.
AJ
On 4 March 2015 at 15:17, Melvin Mughal wrote:
> Followed the readme (https://doc.powerdns.com/md/httpapi/REA
Followed the readme (https://doc.powerdns.com/md/httpapi/README/). Added
those three lines to the pdns.conf, to get the API working. When we try an
API call, it gives:
**
**
*404 Not Found*
**
*Not Found*
*The requested URL /servers/localhost/zones was not found on this
server.*
**
*Apache/
16 matches
Mail list logo
