Guidelines

This site is for tech Q&A. Please keep your posts focused on the subject at hand.

Ask one question at a time. Don't conflate multiple problems into a single question.

Make sure to include all relevant information in your posts. Try to avoid linking to external sites.

Links to documentation are fine, but in addition you should also quote the relevant parts in your posts.

0 votes
54 views
54 views

When running pdnsutil check-all-zones on a PowerDNS server I'm getting a lot of warnings for a reverse zone. Example:

[Warning] Parsed and original record content are not equal: 23.42.168.192.in-addr.arpa. IN PTR 'foo.example.org.' (Content parsed as 'foo.example.org')

DNS is working, though, and the record should be correct.

in General by (245) 7

Your answer

Preview

Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:
By submitting this post you agree to our Terms & Conditions.
To avoid this verification in future, please log in or register.

1 Answer

0 votes
 
Best answer

Apparently the records have been stored with a trailing . in the backend, when they should have been stored without. If you're using PowerAdmin as a frontend for PowerDNS you can simply correct this in the web UI. Open the zone in PowerAdmin and then click Commit changes on all pages containing a record that the check complained about (without changing anything). That should update the records in the format PowerDNS expects.

If you don't have PowerAdmin you need to remove the trailing dots in the backend. If you're using MySQL as the backend that would be something like

UPDATE records SET content = trim(trailing '.' from content) WHERE content LIKE '%.';
by (245) 7
edited by
...