[Pdns-users] Route53 compatible API frontend to PowerDNS
Has anyone made, or is aware of, a Route53 compatible API frontend to PowerDNS? To clarify, I want to allow users to use Route53 compatible tools to configure their DNS in PowerDNS. Ie. the opposite of this: http://romana.now.ie/route53d/ -- Erik ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Retry NXDOMAIN with a secondary forwarder
On Mon, Jan 9, 2012 at 11:30 AM, Richard Connon co...@irconan.co.uk wrote: On 08/01/2012 21:55, Erik Weber wrote: On Sat, Jan 7, 2012 at 6:30 PM, Richard Connonco...@irconan.co.uk wrote: On 07/01/2012 17:24, Peter van Dijk wrote: On Jan 7, 2012, at 4:45 , Richard Connon wrote: Is it possible through lua scripting or otherwise to configure powerdns to look NXDOMAIN responses up in a second forwarder before returning NXDOMAIN. To clarify I'd like it to go something like: lookup name in NS1 if found in NS1: return NS1 result else: lookup name in NS2 return NS2 result Taking one step back: what actual problem are you trying to solve here? I want to overlay a set of names onto an existing DNS zone for which I don't control the nameserver. I have a number of names which are mine inside a zone managed higher up my organisation. The zone also contains lots of names which are not mine. DNS updates can take over 3 weeks (ridiculous, no?) to happen on the actual organisational nameservers so I want to make a resolver which will reflect our changes immediately. Could you possibly access your data by any other means than DNS (like database or something)? If so, couldn't you just write a plugin that checks your backend for the record and otherwise just return to normal lookup mode? I could do that. How difficult would that be? At the moment I wouldn't know where to start. Take a look at the sample here: http://doc.powerdns.com/recursor-scripting.html You'd have to write some lookup code (to the database) and correctly build the return packet. The first thing I'd do is make some code that does the lookup when run directly, then try to fit that into a PowerDNS-script. Some more info at http://wiki.powerdns.com/trac/wiki/Lua -- Erik ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Retry NXDOMAIN with a secondary forwarder
On Sat, Jan 7, 2012 at 6:30 PM, Richard Connon co...@irconan.co.uk wrote: On 07/01/2012 17:24, Peter van Dijk wrote: On Jan 7, 2012, at 4:45 , Richard Connon wrote: Is it possible through lua scripting or otherwise to configure powerdns to look NXDOMAIN responses up in a second forwarder before returning NXDOMAIN. To clarify I'd like it to go something like: lookup name in NS1 if found in NS1: return NS1 result else: lookup name in NS2 return NS2 result Taking one step back: what actual problem are you trying to solve here? I want to overlay a set of names onto an existing DNS zone for which I don't control the nameserver. I have a number of names which are mine inside a zone managed higher up my organisation. The zone also contains lots of names which are not mine. DNS updates can take over 3 weeks (ridiculous, no?) to happen on the actual organisational nameservers so I want to make a resolver which will reflect our changes immediately. Could you possibly access your data by any other means than DNS (like database or something)? If so, couldn't you just write a plugin that checks your backend for the record and otherwise just return to normal lookup mode? -- Erik ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Split Horizon Scripts
On Mon, Nov 14, 2011 at 9:55 PM, Daniel L. Miller dmil...@amfes.com wrote:
On 11/14/2011 11:55 AM, Daniel L. Miller wrote:
Are any of these scripts, and instructions for their use, available?
Ok - further googling and examination of the wiki gave me a starting point.
I've got it working but for two of my domains - the others work correctly.
Can you tell me what's broken? The two domains that don't seem to work are
lv-mircom.us and lv-firealarm.us.
function preresolve ( requestorip, domain, qtype )
if string.find( domain, amfes.com. ) and qtype == pdns.A then
return 0, { { qtype=pdns.A, content=192.168.0.2 } }
elseif string.find( domain, amfire.us. ) and qtype == pdns.A then
return 0, { { qtype=pdns.A, content=192.168.0.2 } }
elseif string.find( domain, lv-mircom.us. ) and qtype == pdns.A then
return 0, { { qtype=pdns.A, content=192.168.0.2 } }
elseif string.find( domain, lv-firealarm.us. ) and qtype == pdns.A then
return 0, { { qtype=pdns.A, content=192.168.0.2 } }
elseif string.find( domain, alarmsonline.us. ) and qtype == pdns.A then
return 0, { { qtype=pdns.A, content=192.168.0.2 } }
elseif string.find( domain, lgma.us. ) and qtype == pdns.A then
return 0, { { qtype=pdns.A, content=192.168.0.2 } }
elseif string.find( domain, poweredup.us. ) and qtype == pdns.A then
return 0, { { qtype=pdns.A, content=192.168.0.2 } }
else
return -1, {}
end
end
In Lua you have to escape the dash in string.find with a %-sign.
if string.find(domain,lv%-mircom.us.) ..
--
Erik
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Split Horizon Scripts
On Tue, Nov 15, 2011 at 7:42 AM, Daniel L. Miller dmil...@amfes.com wrote: On 11/14/2011 1:28 PM, Erik Weber wrote: In Lua you have to escape the dash in string.find with a %-sign. if string.find(domain,lv%-mircom.us.) .. I figured it would be something like that - thanks!!! Is there a better way to do this (read: more efficient or scalable)? I assume the processing overhead is negligible due to the caching? - when watching the logs, looks like the script only gets run once for a given query. I have no idea, I haven't done something like that myself, but I recently started learning Lua and thought I should comment on the dash escaping :-) That said, I would've tried to solve your problem differently. Do you already run two copies of the same zones somehow (one with external and one with internal ips)? If not, here's my suggested workaround; 1) let your official dns be as it is 2) set up a separate pdns authorative server with a copy of the zones you need to access internally, this can run on the same server on a different port 3) set up a recursor that forwards your internal zones to the server/service mentioned in 2) this is done with the forward-zones option in pdns-recursor. 4) set your internal clients to use the server in 3) as dns-server If that's not doable I would probably look at implementing an acl-based split in lua, serving from two different databases depending on acl match. I'm not sure how pdns would solve caching in that case. -- Erik ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PowerDNS in an ISP environment
On Tue, Aug 16, 2011 at 10:05 AM, Chris Russell chris.russ...@knowledgeit.co.uk wrote: Hi Bert, The best I can do is refer to this thread, which lists some data points: http://mailman.powerdns.com/pipermail/pdns-users/2011-May/007719.html Cheers, that's a good start :) We're an ISP utilizing PowerDNS, although small scale if you compare us to others/other countries (~2000 domains). Measuring the 'company domain name' with fpdns is of limited utility - the company domain name itself is often not on the ISP production platform. Yes I know, it more was I was expecting pdns or no match, but it came back with bind. It's not so much the question of is this supported 24x7 etc, I`m already impressed with the level of support provided on these lists which your response is a fine example of which says how good the commercial support would be. We may go down that route but I think their feedback is really more just about a name. My direct manager knows Bind, so I have to justify not bind, if you see what I mean. Our selling point was the MySQL backend, which to be true, is the mainly reason we use PowerDNS. When we started it was the only DNS software with a stable MySQL backend, and since it has worked well we haven't looked for alternatives. The MySQL backend makes it a whole lot easier for us to write management software, as we don't have to fuddle with file permissions, zone reloading and what not. I don't know if that's something you would work towards/use. -- Erik ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PowerDNS in an ISP environment
On Tue, Aug 16, 2011 at 7:00 PM, Brielle Bruns br...@2mbit.com wrote: Some other things to consider why running PDNS is better: 1) BIND is agonizingly slow when loading lots of zones. Only recently have they bothered to work on that so it doesn't take 6 hours to load a ton of domains. 2) Auth and caching services can be run separately, helping keep one potential issue from affecting another. 3) Config options are a heck of alot more easy to use/understand 4) Its trivially easy to run multiple backends, including the bind backend, and even run multiple server instances isolating types of customers, etc. 5) LUA and pipe backends Just shooting in with a feature that I just came to remember. 6) Fancy records. I haven't researched BIND for years, so I'm not sure if that's easily supported there now. But with PowerDNS it's easy to set up web forwarding, it has literally saved me from creating hundreds of empty web config files just to redirect somewhere else. You do have to implement the whole forwarding thingy yourself (unless it's in contrib or something by now?), but it's a few lines of code in e.g. PHP or your favorite web language. -- Erik ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PowerDNS in an ISP environment
On Tue, Aug 16, 2011 at 8:29 PM, Anthony Eden anthonye...@gmail.com wrote: On Tue, Aug 16, 2011 at 8:23 PM, Posner, Sebastian s.pos...@telekom.de wrote: Erik Weber wrote: Some other things to consider why running PDNS is better: [...] Just shooting in with a feature that I just came to remember. 6) Fancy records. 3.0 doesn't support fancy records any more. I, for one, am sad about this. We're still running PowerDNS 2.x and haven't faced this change yet. Shouldn't it be a matter of extending the records table with a column with the URL information, and just insert the record as a normal A record? Your management software and the forwarding software would have to confront the URL field, but to PowerDNS it should look like a normal record. -- Erik ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] CNAME / MX for @
On Mon, Oct 4, 2010 at 5:54 AM, Mouncif Benniane mounci...@gmail.com wrote: I am running pdns Version: 2.9.22-3 on ubuntu 10.0.4 with mysql backend (poweradmin gui). I am trying to understand the following situation I set: �...@domain.com CNAME www1.externaldomain.com Resolution works! as soon I set: domain.com MX 10 mail.externaldomain.com this doesn't work and returns: www1.externaldomain.com instead of mail.externaldomain.com Yeah, that's how it's supposed to work. Read http://en.wikipedia.org/wiki/CNAME_record, specifically the 'Restrictions' part. -- Erik ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
