socket is not connectet
Mark.Andrews at nominum.com
Mark.Andrews at nominum.com
Tue May 29 07:16:23 UTC 2001
Zone transfers to Windows 2000 DNS servers sometimes fail due to a bug
in the Windows 2000 DNS server where DNS messages larger than 16K are
not handled properly. There will be a hot fix available from
Microsoft to address this issue. In the meantime, the problem can
be worked around by setting "transfer-format one-answer;".
[As of May 4 2001 the hotfix was still being prepared]
>
> Hi there,
> I've problem to send my zone from a AiX server to a windows nameservice. I go
> t the following message in the syslog:
> /usr/local/sbin/named[6122]: client 132.10.2.53#3340: transfer of 'de.myzone.
> com': send: socket is not connected
> May 29 08:40:36 cws1e /usr/local/sbin/named[6122]: client 132.10.2.53#3371: t
> ransfer of 'de.myzone.com': send: socket is not connected
> May 29 08:42:36 cws1e /usr/local/sbin/named[6122]: client 132.10.2.53#3398: t
> ransfer of 'de.myzone.com': send: socket is not connected
>
> The server are full reachable ping, telnet, what ever. A zone update for anot
> her zone in the other direction works good. Bind on Aix is 9.1, on Windows t
> he NT named. What could the reason for that?
>
> Thanks
>
> Thomas
> --
> ________________________________________________
> redseven Community - Alleine war gestern
> http://www.redseven.de
> redseven freemail - der kostenlose eMail-Service
> http://mail.redseven.de
>
> Join us now!
>
>
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at nominum.com
More information about the bind-users
mailing list