Re: [Pdns-users] Request for Help with PowerDNS + Recursor Configuration for Final Year Project

2025-05-07 Thread frank--- via Pdns-users
> On 7 May 2025, at 17:03, Nacho Oppo wrote: > > Hi Frank. > > Another option I considered is creating a program that modifies the > /etc/hosts files. With resolv.conf pointing to the internet and the > nsswitch with host as file and dns, I'd have it solved. The only thing > I need to implemen

Re: [Pdns-users] Request for Help with PowerDNS + Recursor Configuration for Final Year Project

2025-05-07 Thread frank--- via Pdns-users
> On 7 May 2025, at 16:19, Nacho Oppo wrote: > > Hi, Frank > > > I believe I may not have explained the scenario clearly in my previous > messages. Let me try to clarify it with a simplified example, which might > better illustrate the situation: > > I have a server A with IP address dirip

Re: [Pdns-users] Request for Help with PowerDNS + Recursor Configuration for Final Year Project

2025-05-07 Thread frank--- via Pdns-users
Hi Nacho, How "static" is the list of domains which need to resolve locally? Updated sub-second? Once every minute? Once every hour? I would not use pdns-recursor at all. I would let dnsdist be the first point of entry, with 2 pools: a "auth" pool and a resolver pool. Add the pdns-auth (with M

Re: [Pdns-users] Request for Help with PowerDNS + Recursor Configuration for Final Year Project

2025-05-07 Thread frank--- via Pdns-users
> On 7 May 2025, at 10:04, Nacho Oppo via Pdns-users > wrote: > > The goal is to configure PowerDNS so that it first checks an A record in a > MySQL backend, and if the record is not found o if database does´not respond, > it should forward the query to an external DNS server, such as Google’

Re: [Pdns-users] Need help after the upgrade

2025-02-27 Thread frank--- via Pdns-users
; ++-+-++--+--++-+-+--+--+-+ >>>> | 1 | SIMPLE | domains | NULL | ALL | PRIMARY,name_index >>>> | NULL | NULL| NULL|1 | >>>> 100.00 | NUL

Re: [Pdns-users] Need help after the upgrade

2025-02-27 Thread frank--- via Pdns-users
|1 | 100.00 | >> NULL| >> | 1 | SIMPLE | records | NULL | ref | nametype_index,domain_id >> | nametype_index | 271 | powerdns.domains.name,const |1 |10.00 | >> Using where | >> +----+-----+-++--+--++-+-+--+--+-+ &

Re: [Pdns-users] Need help after the upgrade

2025-02-27 Thread frank--- via Pdns-users
> > Forgot to mention: it also might be your DB schema is missing an > index, making the zone cache query slow. Posting the result of the following db query might help: explain select domains.id , domains.name, records.content, domains.type, domains.master, domains.notified

Re: [Pdns-users] Multips subnets in one Reverse Zone

2025-02-21 Thread frank--- via Pdns-users
Hi Rob, Yes, should be possible, PowerDNS won't complain about 2000-3000 or more records in the zone. If you should or not depends on how often and how you'll change them. Some web UIs might get slow if there are 3000 records in a zone, so try that out. Frank > On 21 Feb 2025, at 11:52, rob

Re: [Pdns-users] PowerDNS, multi-cloud, feedback needed on options I am considering

2025-01-24 Thread frank--- via Pdns-users
Your options seem valid. There's always going to be a trade-off and there's always going to be some sort of sync-mechanism that you'll have to trust. Whether that's the middleware app or the database replication mechanism or something else. What option to choose is a question only you can make