Erroneous 'not found' logs in mdns on NOTIFYs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
High
|
Erik Olof Gunnar Andersson |
Bug Description
When Designate sends a NOTIFY, and gets a valid answer (NOERROR with no answer section),
we currently log a "zone not found on ip:port"
2017-03-09 19:17:43.086 6939 INFO designate.
This happens on seemingly every single NOTIFY.
This has no real effect, but it's a crazy confusing thing to have in the log.
It looks like it's because we have generalized code that catches this:
https:/
You probably don't want that when you're querying the SOA record, obviously.
So that needs to be unwound a bit.
Changed in designate: | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: low-hanging-fruit |
Changed in designate: | |
assignee: | nobody → Pavan (pavan02) |
Changed in designate: | |
assignee: | Pavan (pavan02) → nobody |
status: | In Progress → Triaged |
Changed in designate: | |
assignee: | nobody → Simon Leinen (simon-leinen) |
status: | Triaged → In Progress |
Hi, I went through the code and I see that it logs for every attempt in sending DNS message(be it notify or SOA). Based on the description I assume that logs shouldn't happen for SOA. Am I correct?
If this is still a issue I would like to work on it.