Hello,
I have 3 name server setup
ns1 to ns3 from ip .142 to .144
I customer try to edit his name server in his registrar but he has this error :
"Information sur la Zone
charentes.fr.
ns2.carat-hosting.com. 65.110.36.143
ns3.carat-hosting.com. 65.110.36.144
connectivit? TCP (IP=65.110.36.144)
R?sultat des tests
---- fatal ----
Le serveur n’?coute pas ou ne r?pond pas en TCP sur le port 53
R?f: IETF RFC1035 (p.32 4.2. Transport)
The DNS assumes that messages will be transmitted as datagrams or in a byte stream carried by a virtual circuit. While virtual circuits can be used for any DNS activity, datagrams are preferred for queries due to their lower overhead and better performance.
ns2.carat-hosting.com./65.110.36.143
Statut final
ECHEC
Profile: afnic (delegation under .fr/.re done by AFNIC registry)
Statistics: 17 tests in 4.96 sec accross 2 nameservers
Release: ZoneCheck-2.0.4-AFNIC
Last generated: 2004/10/19 02:39 UTC
" Le serveur n’?coute pas ou ne r?pond pas en TCP sur le port 53"
means
The server doesn’t listen or answer in TCP on port 53
it says to see the IETF RFC1035 (p.32 4.2. Transport) page 32 point 4.2
here ftp://ftp.ietf.org/rfc/rfc1035.txt
here is the text
4.2.2. TCP usage
Messages sent over TCP connections use server port 53 (decimal). The
message is prefixed with a two byte length field which gives the message
Mockapetris [Page 32]
RFC 1035 Domain Implementation and Specification November 1987
length, excluding the two byte length field. This length field allows
the low-level processing to assemble a complete message before beginning
to parse it.
Several connection management policies are recommended:
-
The server should not block other activities waiting for TCP
data. -
The server should support multiple connections.
-
The server should assume that the client will initiate
connection closing, and should delay closing its end of the
connection until all outstanding client requests have been
satisfied. -
If the server needs to close a dormant connection to reclaim
resources, it should wait until the connection has been idle
for a period on the order of two minutes. In particular, the
server should allow the SOA and AXFR request sequence (which
begins a refresh operation) to be made on a single connection.
Since the server would be unable to answer queries anyway, a
unilateral close or reset may be used instead of a graceful
close.
I really don’t understand what happens, as it is the first time I have this pbm
(his registrar, ovh, wanted I change my name server because they were on the same IP : I did it, and now this :\ )
Do you have an idea ?
What I have to do ?
Thanks