[Pdns-users] Temporarily disable SOA requirement for slave AXFR
Hi all, I'm trying to set up a delegated zone on my master PowerDNS server to be slaved out to my slaves, however even if I pdns_control notify the slaves, they don't AXFR the zone instead throwing this error: Sep 3 13:02:20 service-1 pdns[6115]: Error trying to retrieve/refresh 'example.com': Query to '192.0.2.1' for SOA of 'example.com' produced a NS record (Obviously these aren't the real zone or IP) The master hasn't got an SOA and shouldn't have one, so is there a way to avoid this check? On the master the zone only has these records: sqlite> select * from records where domain_id=13; id|domain_id|name|type|content|ttl|prio|change_date 13260|13|example.com|NS|ns1.someotherzone.invalid|86400|| 13261|13|example.com|NS|ns2.someotherzone.invalid|86400|| -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Hidden supermasters
Hi Richard, On Fri, 2010-08-06 at 15:27 +1000, Richard McLean wrote: > I have wondered about this. We'd love to implement a hidden supermaster type > setup, using AXFR, which auto-updates the 4 main name servers, but is *not* > in the list of name servers for a domain and is not publicly available. Is > the > restriction above able to be worked around or turned off? I've managed to work around this by adding a config line like: gsql-supermaster-query=select account from supermasters where ip='%s' In this setup, only IP addresses need to be listed in the supermasters table and the other checks are bypassed. This might need some careful checks if the database schema / the expected returned field list etc changes at some point in the future. -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] MySQL docs bug?
Aha yes, the documentation should probably mention that the constraint needs to be appended to an alter or create! On Wed, 2010-06-02 at 23:37 +1200, Michael wrote: > On Wed, 02 Jun 2010 23:33:19 you wrote: > > Hi Michael, > > > > On Wed, 2010-06-02 at 20:10 +1200, Michael wrote: > > > The following does not work: > > > > > > CONSTRAINT `records_ibfk_1` FOREIGN KEY (`domain_id`) REFERENCES > > > `domains` (`id`) ON DELETE CASCADE > > > http://docs.powerdns.com/generic-mypgsql-backends.html > > > > Are you using an InnoDB or MyISAM table? MyISAM is the default on some > > (all?) MySQL installations and doesn't support constraints like this. > > InnoDB. I have found the answer - it needs an 'ALTER... something (can't > recall what it was) prefixed. -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz Phone: 0800 750 250 DDI: 03 978 1223 Mobile: 027 666 4482 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] EDNS support + default buffer size
Hi Bert, Thanks for the expedient and comprehensive reply. On Thu, 2010-03-18 at 06:45 +0100, bert hubert wrote: > > The 'nothing but trouble' refers to the surprisingly large number of servers > that when queried with EDNS on, either provide no answer, return a SERVFAIL > or a malformed answer. > As it turns out, my testing has shown that at least one important NZ-based government website falls in to this category :( > > I hope the above answers your questions. > Sure did, cheers. -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz Phone: 0800 750 250 DDI: 03 978 1223 Mobile: 027 666 4482 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] EDNS support + default buffer size
Hi all, I've just tested the PowerDNS Recursor 3.2 with its out of the box configuration against the tests outlined at https://www.dns-oarc.net/oarc/services/replysizetest It seems that EDNS is disabled by default, which is confirmed by the comment attached to changeset #1430 (http://wiki.powerdns.com/trac/changeset/1430) Looking at the source it seems in 3.2 an option "disable-edns=no" was added which turns EDNS support on. A cursory test here shows that adding this to the stock config does cause the dns-oarc reply size test to report a reply size of 1200 vs 512 when EDNS is off. What is the status of EDNS support? Is it safe to rely on in production environments? What specifically does the "nothing but trouble" comment on the changeset refer to? Also, the buffer size of "1200" appears to be hard coded. Is there any particular reason for this value? I'm guessing it has to do with avoiding fragmentation, but it'd be nice to know for sure. Thanks, -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz Phone: 0800 750 250 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
