[prev in list] [next in list] [prev in thread] [next in thread]
List: pdns-users
Subject: Re: [Pdns-users] AXFR Error: Unknown record was stored incorrectly, need 3 fields, got 1
From: Anthony Eden <anthonyeden () gmail ! com>
Date: 2012-07-04 8:13:30
Message-ID: CABcU2EGBEqQRssvuyZjP6TCpkRPzAoVqGAWtv12a0nLrQVaqAg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Wed, Jul 4, 2012 at 2:02 AM, Anthony Eden <anthonyeden@gmail.com> wrote:
> Sorry, I sent this to Peter directly and did not CC the list...
>
> On Tue, Jul 3, 2012 at 7:06 PM, Peter van Dijk <
> peter.van.dijk@netherlabs.nl> wrote:
>
> > Hello Anthony,
> >
> > On Jul 3, 2012, at 17:41 , Anthony Eden wrote:
> >
> > > I am using PowerDNS 3 with a MySQL backend and am attempting an AXFR,
> > however I am receiving the following error for a URL record (which we store
> > and handle with a custom backend during normal resolution)
> > >
> > > Exception: Unknown record was stored incorrectly, need 3 fields, got 1
> > >
> > > This error is described in http://wiki.powerdns.com/trac/ticket/156and is \
> > > marked as resolved. That was against 2.9.21 however so I wonder if
> > this is a regression or something else?
> >
> > URL records are not supported in PowerDNS 3 and up. How does your custom
> > backend handle AXFR? Or are you leaving AXFR to a gsql backend?
> >
> > Kind regards,
>
>
> My goal was to have AXFR on its own host and use a gqsl backend. It seems
> that it is blowing up on some other non-standard record types we have as
> well, so I think a custom AXFR backend is probably the best choice at this
> time. What do you think?
>
After speaking to Peter on IRC here are the options I can pursue:
1.) Modify the gmysql-list-query so that it skips custom records (like
URL). When we switch to DNSSEC then we would modify
the gmysql-list-query-auth query instead.
2.) Discuss with the customer another approach for slaving since dropping
records seems to negate the benefits of the slave.
I'm leaning towards option 2 at this point but am awaiting feedback from
our customer.
Thanks, Peter, for helping out.
-Anthony
--
http://anthonyeden.com | twitter: @aeden | skype: anthonyeden
[Attachment #5 (text/html)]
On Wed, Jul 4, 2012 at 2:02 AM, Anthony Eden <span dir="ltr"><<a \
href="mailto:anthonyeden@gmail.com" \
target="_blank">anthonyeden@gmail.com</a>></span> wrote:<br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> Sorry, I sent this to Peter \
directly and did not CC the list...<br><br><div class="gmail_quote"><div \
class="im">On Tue, Jul 3, 2012 at 7:06 PM, Peter van Dijk <span dir="ltr"><<a \
href="mailto:peter.van.dijk@netherlabs.nl" \
target="_blank">peter.van.dijk@netherlabs.nl</a>></span> wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Anthony,<br> <div><br>
On Jul 3, 2012, at 17:41 , Anthony Eden wrote:<br>
<br>
> I am using PowerDNS 3 with a MySQL backend and am attempting an AXFR, however I \
am receiving the following error for a URL record (which we store and handle with a \
custom backend during normal resolution)<br> ><br>
> Exception: Unknown record was stored incorrectly, need 3 fields, got 1<br>
><br>
> This error is described in <a href="http://wiki.powerdns.com/trac/ticket/156" \
target="_blank">http://wiki.powerdns.com/trac/ticket/156</a> and is marked as \
resolved. That was against 2.9.21 however so I wonder if this is a regression or \
something else?<br>
<br>
</div>URL records are not supported in PowerDNS 3 and up. How does your custom \
backend handle AXFR? Or are you leaving AXFR to a gsql backend?<br> <br>
Kind regards,</blockquote><div><br></div></div><div class="im"><div><span \
style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">My goal was \
to have AXFR on its own host and use a gqsl backend. It seems that it is blowing up \
on some other non-standard record types we have as well, so I think a custom AXFR \
backend is probably the best choice at this time. What do you think?</span> </div> \
</div></div></blockquote><div><br></div><div> After speaking to Peter on IRC here are \
the options I can pursue:</div><div><br></div><div>1.) Modify the gmysql-list-query \
so that it skips custom records (like URL). When we switch to DNSSEC then we would \
modify the gmysql-list-query-auth query instead.</div> <div>2.) Discuss with the \
customer another approach for slaving since dropping records seems to negate the \
benefits of the slave.</div><div><br></div><div>I'm leaning towards option 2 at \
this point but am awaiting feedback from our customer.</div> \
<div><br></div><div>Thanks, Peter, for helping \
out.</div><div><br></div><div>-Anthony</div>
<div><br></div></div>-- <br><a href="http://anthonyeden.com" \
target="_blank">http://anthonyeden.com</a> | twitter: @aeden | skype: anthonyeden<br>
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic