* Peter Nunn <[email protected]> [161211 12:49]: > pdnsutil returned the following on one of the broken zones > > pdnsutil check-zone example.com > Dec 11 22:44:49 Reading random entropy from '/dev/urandom' > [Error] Following record had a problem: example.com IN SOA ns1.example.com > hostmaster.example.com 2016110702 28800 7200 604800 86400 > [Error] Error was: All data was not consumed > [Error] No NS record at zone apex in zone 'example.com' > Checked 23 records of 'exapmle..com', 2 errors, 0 warnings. > > Does that shed any light. I suspect database corruption during the manual > database schema upgrade?
That sounds extremely unlikely. Here are some hints for getting useful answers from this list: - your report needs to be complete. Show us your source (= database contents) and output (= dig) data. - do not obscure zone names. Chances are you'll hide the actual problem and/or make typos (as you did). - name your NS public IP so we can send some dig queries to it that may help reveal the issue. There's nothing wrong with actually having a test zone set up on your public NS that reproduces the problem though. Good luck, -- Christian Hofstaedtler / Deduktiva GmbH (FN 418592 b, HG Wien) www.deduktiva.com / +43 1 353 1707 _______________________________________________ Pdns-users mailing list [email protected] https://mailman.powerdns.com/mailman/listinfo/pdns-users
