Shyamal Prasad <[EMAIL PROTECTED]> writes: > My somewhat uneducated guess is that your reverse DNS might be behind > this. Notice what I get (apologies for the telnets to your box ;-):
debian.enode.de is not my box, it is just a name I use internally for my box (as enode.de is my domain). debian.enode.de resolved to my Web provider ... My external name is enode.dyndns.org > ------------------------------------------------------------------------ > > [EMAIL PROTECTED]:~$ dig debian.enode.de > <..deleted...> > ;; ANSWER SECTION: > debian.enode.de. 86388 IN A 212.227.109.196 > <..deleted..> > > [EMAIL PROTECTED]:~$ telnet debian.enode.de > Trying 212.227.109.196... > Connected to kundenserver.de. > Escape character is '^]'. > Warning! > > For security reasons all ssh and telnet sessions are logged, and may > be monitored. By logging in you give consent to these conditions. > > <...deleted stuff where I get auto disconnected....> > > [EMAIL PROTECTED]:~$ dig 196.109.227.212.in-addr.arpa ptr > <...deleted...> > > ;; ANSWER SECTION: > 196.109.227.212.in-addr.arpa. 86400 IN PTR kundenserver.de. > > <...deleted...> > ------------------------------------------------------------------------ > > So at least now I have a hint about where the kundenserver.de is > coming from. Yes, the telnetd resolves debian.enode.de and then reverse-resolves the IP. But why doesn't it just take the hostname? > I'm still not sure why your telnet issue looks the way it > does, and further, I don't see the same thing from here. Yes, because you have a proper hostname. -- Please don't CC me on replies!
