Replies: 5 comments
-
|
I trace of the failing recursor query would probably shed some light on what was happening here. |
Beta Was this translation helpful? Give feedback.
-
|
For rec, to know that a zone inside a |
Beta Was this translation helpful? Give feedback.
-
|
What would be the best combination of recursor configuration options to get the information desired? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Heh... I just realized this morning that part of the cause could be that this was a newly-registered domain, and so the content of the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My DNS configuration is
hidden primary->hidden secondary->recursor. The auth servers are running pdns-auth 5.0.0-1pdns.debian13 and the recursor is running 5.3.0-1pdns.debian13.The hidden primary has a 'producer' catalog zone along with a number of normal 'primary' zones. The hidden secondary has a matching 'consumer' catalog zone. The recursor also uses this catalog zone for configuring forward-zones; it forwards queries to the hidden secondary (the hidden secondary and recursor are on the same machine). The hidden secondary is configured with secondary-do-renotify so that it will send NOTIFY to the recursor when it receives new content for any of the zones; the recursor uses this both to refresh the catalog zone and to wipe caches for the regular zones.
Today I added a new zone
714durham.uson the hidden primary, and included it into the catalog zone. The hidden primary sent NOTIFY to the hidden secondary for both zones, and the hidden secondary used AXFR to retrieve the contents of both zones. The hidden secondary sent NOTIFY to the recursor once those AXFRs were completed. The recursor used IXFR to retrieve the contents of the catalog zone from the hidden secondary. All of this was expected.After that was completed, I used
pdnsutil zone edit 714durham.usto add a number of RRs to the zone, including an MX RRset. The NOTIFY+AXFR process happened again. I then attempted to query the recursor for the MX RRs, and got a SERVFAIL response with EDE indicating "EDE: 10 (RRSIGs Missing)", which was surprising since the zone is not signed.Querying the hidden secondary for the same RRs worked fine. I did not see anything out of the ordinary in the recursor logs, so I restarted it and sent the query again, and this time the recursor provided the proper answer.
Log from the hidden primary:
(
fddd:a03f:2620:186::20is the hidden secondary involved here)Log from the hidden secondary:
(the final two AXFR-out are from the recursor being restarted)
Log from the recursor (with
statsandwebserverentries removed):I can likely reproduce this by adding another zone, so if additional details are needed I'll give that a try.
Beta Was this translation helpful? Give feedback.
All reactions