Please help! Pretty please? (DNS trouble, I think)

From: Carlos Moreno (moreno_at_mochima_dot_com_at_xx.xxx)
Date: 01/18/04 

Date: Sun, 18 Jan 2004 16:37:01 -0500

Hi,

I'm so damn frustrated by how utterly clueless I am about
what could be the reason of this behaviour that I can't
even begin to imagine how it is physically possible that
it happens.

Here's what's happening:

I log on to the server (it's a "dedicated server" that
we're renting from a web hoster -- it has "direct"
connection to the net, with a static IP address), and
type the command:

$ telnet localhost 5555

For about ten seconds I have no reply. Then, I get the
expected:

Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused

(there's nothing listening on that port, and there is no
iptables rules affecting that port either)

If I type:

$ telnet 127.0.0.1 5555

Then I get the expected response in zero time.

The file /etc/hosts contains the following: (I changed
the actual IP addresses and names, but other than that
this is verbatim what the /etc/hosts file contains)

--- FILE CONTENTS BEGIN ---
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
1.2.3.4 www.domain.com
1.2.3.5 secure.domain.com
1.2.3.6 mail.domain.com
--- FILE CONTENTS END ---

The file /etc/host.conf contains a single line:

order hosts,bind

Can you think of something that could explain this
behaviour?? I'm tempted to think that it's our hoster's
DNS servers fault (I tried telnetting port 53 of their
DNS servers, and it did take some time to reply); but
the thing is that I can not understand or justify how
could that affect the behaviour of a connection to
localhost. I mean, that even if their DNS were slow,
or misconfigured, or even completely down, I still don't
see how that would produce a delay in establishing a
connection to *localhost*.

Could someone please enlighten me?

Thanks,

Carlos 

--

Relevant Pages

  • Re: Random unprivileged TCP ports below 5000 kind-of open for a fraction of a second
    ... When Nmap (or many ... > other applications, such as Telnet) does a connectcall, the OS is ... > supposed to choose a good souce port to bind to for the connection. ... I saw a familiar "Connection reset by peer" every time the random port ...
    (Incidents)
  • Re: IP Blocker in SBS2003 exchange
    ... > What I was trying to explain in the telnet section was that I realise ... > the server is listening for connections on ports 110 and 25. ... > but he can connect to port 110. ... > well as another wireless broadband connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Port 25 blocked ?
    ... Thx for you cue i did try like you suggest to telnet other mx and no ... If you want to confirm it, just try a telnet on port 25 to some one else's ... Is there a way to tell if Port 25 is block for outbound connection? ...
    (microsoft.public.windows.server.sbs)
  • RE: how to block connections running on non-default ports
    ... masqueraded connections because all the telnet protocol does is send any ... This is why you can use telnet to connect to a website on port 80 and ... indistinguishable from an SSL connection coming from a browser. ...
    (Security-Basics)
  • Re: outbound mail
    ... internal DNS servers set up? ... As far as making sure port 25 is open, typically that shouldn't be a concern ... for outbound. ... Try some other remote mail servers (telnet on port 25) and post ...
    (microsoft.public.exchange.admin)