>> ;; QUESTION SECTION:
>> ;eurobank-direktna.rs <http://eurobank-direktna.rs/>. IN
>> NS
>>
>> ;; ANSWER SECTION:
>> eurobank-direktna.rs <http://eurobank-direktna.rs/>. 3600 IN NS
>> bgdit01edns01.eurobank.rs <http://bgdit01edns01.eurobank.rs/>.
>>
>> This is obviously wrong, but why should a resolver query
>> @ns1.eurobank.rs for eurobank-direktna.rs <http://eurobank-direktna.rs/>
>> nameservers as
>> this information is already known.
>
> This can happen in a variety of ways. Sometimes the child zone
> "helpfully" includes NS records in the authority section along with
> answers. Sometimes this happens when the delegation records are
> being refreshed due to TTL expiration, and sometimes an explicit user
> or application query for the NS records.
>
> In any case BIND is "entitled" to prefer the child zone NS RR, which
> then turns out to be unusable. The zone in question is misconfigured.
Thanks for clarification, Viktor.
Alex, you might try unbound instead of bind while this error persists.
https://unbound.docs.nlnetlabs.nl/en/latest/reference/history/requirements.html
-->
Parent and child with different nameserver information
A misconfiguration that sometimes happens is where the parent and child
have different NS, glue information. The child is authoritative, and
unbound will not trust information from the parent nameservers as the
final answer. To help lookups, unbound will however use the parent-side
version of the glue as a last resort lookup. This resolves lookups for
those misconfigured domains where the servers reported by the parent are
the only ones working, and servers reported by the child do not.
<--
In case you or your customer is affiliated with eurobank, you might
tell them about that misconfiguration.
Best regards,
Gerald
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
