<div dir="ltr">Oops, celebrated too early. Today, I recorded another unexpected NXDOMAIN reply:<div><br></div><div><div>13:37:32.372046 IP (tos 0x0, ttl 64, id 24351, offset 0, flags [DF], proto UDP (17), length 69)<br></div>
<div> 10.1.2.39.9903 > 10.1.1.60.53: [udp sum ok] 553+ A? dbint039487.c1.internal. (41)</div><div>13:37:32.373650 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 152)</div><div> 10.1.1.60.53 > 10.1.2.39.9903: [udp sum ok] 553 NXDomain*- q: A? dbint039487.c1.internal. 1/1/0 dbint039487.c1.internal. CNAME database33.c1.internal. ns: internal. SOA <a href="http://nsa.byte.nl">nsa.byte.nl</a>. <a href="http://hostmaster.byte.nl">hostmaster.byte.nl</a>. 2009121500 10800 3600 604800 3600 (124)</div>
<div>13:37:32.373660 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 152)</div><div> 10.1.1.60.53 > 10.1.2.39.9903: [udp sum ok] 553 NXDomain*- q: A? dbint039487.c1.internal. 1/1/0 dbint039487.c1.internal. CNAME database33.c1.internal. ns: internal. SOA <a href="http://nsa.byte.nl">nsa.byte.nl</a>. <a href="http://hostmaster.byte.nl">hostmaster.byte.nl</a>. 2009121500 10800 3600 604800 3600 (124)</div>
</div><div><br></div><div>(also, am not sure where the dupe reply came from, perhaps because we're using bonding and tcpdump listened on 'any'). </div><div><br></div><div>Config & database rows @ <a href="https://gist.github.com/gwillem/8686d364e2d9cad92c62">https://gist.github.com/gwillem/8686d364e2d9cad92c62</a></div>
<div><br></div><div>Any suggestions how to debug this?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 11, 2014 at 1:12 PM, Chris <span dir="ltr"><<a href="mailto:lists@shthead.com" target="_blank">lists@shthead.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
For the subdomain wildcard problem you have, see my post here:
<a href="http://mailman.powerdns.com/pipermail/pdns-users/2014-May/010652.html" target="_blank">http://mailman.powerdns.com/pipermail/pdns-users/2014-May/010652.html</a><br>
<br>
And Peter's follow up here:
<a href="http://mailman.powerdns.com/pipermail/pdns-users/2014-May/010653.html" target="_blank">http://mailman.powerdns.com/pipermail/pdns-users/2014-May/010653.html</a><br>
<br>
I believe that might be related?<br>
<br>
I upgraded from 2.9 to 3.3 a while back with no real hassles
(roughly 7m records in 4 instances), only thing to watch out for was
the schema changes. I import zones from servers running cPanel
(using zone2sql on the named files) and that didn't require any
changes which was nice.<br>
<br>
Chris<div><div class="h5"><br>
<br>
<div>On 11/07/2014 6:08 PM, Willem wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">FYI, here are my notes from upgrading our 1M
records mysql-based setup from 2.9 to 3.3.1:
<div><br>
</div>
<div>One nasty bug that was our reason to upgrade in the first
place, is gone. We used to have 1 out of every million queries
giving a false NXDOMAIN reply, not anymore. You could call us
very happy ;)</div>
<div><br>
</div>
<div>A huge issue (for us) was the stricter database model. The
new pdns requires every record to have the same domain_id as
the corresponding SOA record. Specifically, this means that an
A record for sub.domain.tld will not work anymore, if a SOA
record for sub.domain.tld with another domain_id exists. We
had to rewrite quite a few procedures to comply with this new
behaviour and run a periodic check on our database to see
whether there are still processes that write the wrong
domain_id's. </div>
<div><br>
</div>
<div>Another thing biting us, is that an A query for
x.sub.dom.tld doesn't work anymore, given A records
"*.dom.tld" and "sub.dom.tld". An A query for x.sub2.dom.tld
does still work. We haven't fixed this yet. I've posted the
details at <a href="https://gist.github.com/gwillem/6bbcf43545de6c25cf0e" target="_blank">https://gist.github.com/gwillem/6bbcf43545de6c25cf0e</a></div>
<div><br>
</div>
<div>All in all, the upgrade and fixing all dependencies was a
lot of work (3 weeks), but a big succes.</div>
<div>Thanks for making powerdns!</div>
<div><br>
</div>
<div>Willem </div>
<div><br>
</div>
<div><br>
<div>
<br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Pdns-users mailing list
<a href="mailto:Pdns-users@mailman.powerdns.com" target="_blank">Pdns-users@mailman.powerdns.com</a>
<a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Pdns-users mailing list<br>
<a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
<a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
<br></blockquote></div><br></div>