send: socket is not connected

[Ondřej Surý]

Hi Mike,

your report does not include any actionable information.

You did not specify what version of DNS servers are you running
on the primary nor on the secondary. It is not even clear that you
are running BIND 9 at all.

But honestly, this feels like a networking issue between the primary
and the secondary - something like IDS/IPS/firewall being to eager.

If you want the help with the problem, you will have to be more
specific and also provide the configurations from both of the servers
(named-checkconf -px). Having pcaps to see what really happened
on the networking layer would also help.

Cheers,
Ondrej
--
Ondřej Surý (He/Him)
ondrej at isc.org

ADHD brain at work: I sometimes lose track of my inbox. Please feel free to send a gentle nudge if you're waiting on a reply!

My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.

> On 8. 7. 2026, at 22:52, Muzinich, Mike <MuziniM at losrios.edu> wrote:
> 
> I am having an issue with one zone on one server.
>  The slave shows:
>  failed while receiving responses: connection reset
> Transfer status: connection reset
>  While the master shows:
>  send: socket is not connected
>  Doing a zone transfer with dig from the slave works.  Anybody seen this before?
> -- 
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.