Re: [Pdns-users] Wildcard record based on type
On 5/14/2013 4:11 PM, Fernando Morgenstern wrote: The issue is that sometimes Powerdns won't "see" the new subdomains. I'm not able to reproduce this issue easily, but even with the subdomain created, it takes a while for Powerdns to serve that record properly. In other words, i see it in the database, but a simple dig directly to Powerdns won't return it. This is the problem you should spend your time on solving. Even if you hack your way into having both a wildcard record and a TXT record returned properly, I'd bet that you'll still have a problem with newly added TXT records not being available in a timely matter. (in other words if you can't see new A records when you expect to, you probably won't see new TXT records either) -- Dave Sparro ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Possible bug observed in PowerDNS Recursor 3.2.1
On 8/4/2010 6:36 AM, Nuno Nunes wrote: Hello all, I've gone through the last few months of the ML, up until the announcement of the release of 3.2.1, and didn't find any reference to this bug I'm apparently seeing, so I'm reporting this to you all for help. I work at an ISP where we have a number of servers running PowerDNS Resolver 3.2.1 as our customer-facing resolvers. We have had this setup for a few months now and sometimes a weird thing happens (and no, I can't reproduce it in any deterministic way and it only happens sometimes): when the TTL for a record of a given zone expires and a new request comes in for it, some of the caches on the farm go out and get the new information, but some others just seem to ignore the TTL and stick with the old data forever. This is most notable when a zone changes name servers and the owner of the zone comes complaining to us that we still have the old data, even after the appropriate amount of time has elapsed for it to have been refreshed (and on these cases we typically observe this behaviour on NS records, but we have observed it on A records also, for example). I see this all the time on BIND resolvers. The keys to the situation are: * Domain's old NS records have a relatively long TTL (from old auth. servers) * Domain owner changes auth. servers with registrar * Domain owner does NOT update data on old auth. servers. (they're now serving stale data, but authoritatively) Since the domain owner is your ISP customer, you get get queries for the domain relatively often, so your recursive servers rely on the cached NS records for the domain (the ones that point to the auth. server serving stale data). I think that BIND resets the TTL when the recursive server sees NS records in the authority section of a response. Maybe PowerDNS is doing this as well? I generally advise the domian owner to have the domain removed from the old auth. server. -- Dave ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] dynamic load balacing
On 5/21/07, fatih cerit <[EMAIL PROTECTED]> wrote: >From: Duane <[EMAIL PROTECTED]> >To: fatih cerit <[EMAIL PROTECTED]> >CC: pdns-users@mailman.powerdns.com >Subject: Re: [Pdns-users] dynamic load balacing >Date: Tue, 22 May 2007 01:51:21 +1000 > >fatih cerit wrote: >>3- if your clients registering sip.example.com at 172.16.0.1 and server >>down then your clients going to register sip.example.com at 172.16.30.40 >>if you have a failover rotation rule at DNS level. But if you have a >>dynamic fail over rule you can say some clients register sip.example.com >>at 172.16.60.70 >> >>thanks for your advice I am looking for a solution like 3th. > >At a guess you will most likely need some kind of hardware device beyond >simple DNS redirect as they cache and you can't control that completely >because you are at the behest of others... You can on the other hand >perfectly control a load balancing device. if I can query like this where type='A' and name='sip.example.com' and client_ip_address = '172.2.2.2' ; I will be able to load balance and failover dynamically and maybe ttl times help me for caching of sip devices. _ Beware, the "client_ip_address" you see is not likely to be the end-user's IP address, but that of the caching DNS server that their stub resolver queries. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
