issue with name resolution - SSH

This is a discussion on issue with name resolution - SSH ; dear all, I have a slackware 10.2 box, and a remote linux box I want login to. Here my problems: traceroute [remote-hostname] -> no problems ssh [remote-ip-address] -> works without problems ssh [remote-hostname] -> connection fails, with a time out ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: issue with name resolution

  1. issue with name resolution

    dear all,

    I have a slackware 10.2 box, and a remote linux box I want login to.

    Here my problems:

    traceroute [remote-hostname] -> no problems
    ssh [remote-ip-address] -> works without problems

    ssh [remote-hostname] -> connection fails, with a time out error
    message.
    By logging the ssh messages, I found out that it tries to connect to
    host [1.0.0.0], i.e. it wrongly resolvs the host.

    However, if I do

    host [remote-hostname] -> ok

    and then

    ssh [remote-hostname] -> ok

    ssh works; it seems that it uses same cache of host resolution.

    Can you explain me how to fix the hostname resolution?

    best regards

    G.

  2. Re: issue with name resolution


    "Giorgio Corani" wrote in message
    news:43897da1$0$16204$4fafbaef@reader3.news.tin.it ...
    > dear all,
    >
    > I have a slackware 10.2 box, and a remote linux box I want login to.
    >
    > Here my problems:
    >
    > traceroute [remote-hostname] -> no problems
    > ssh [remote-ip-address] -> works without problems
    >
    > ssh [remote-hostname] -> connection fails, with a time out error
    > message.
    > By logging the ssh messages, I found out that it tries to connect to host
    > [1.0.0.0], i.e. it wrongly resolvs the host.
    >
    > However, if I do
    >
    > host [remote-hostname] -> ok
    >
    > and then
    >
    > ssh [remote-hostname] -> ok
    >
    > ssh works; it seems that it uses same cache of host resolution.
    >
    > Can you explain me how to fix the hostname resolution?
    >
    > best regards


    Is the reverse DNS for your host correct? And it's unclear to me whether you
    are checking the logs on your client, or on the SSH serving host, and what
    you are actually seeing. Can you post the logs?



  3. Re: issue with name resolution

    I am on the client side.

    I have found out that:

    (a) my ssh client do work correctly with ip-addresses, but wrongly with
    hostnames.
    By using ssh -v, I discovered that it tries always to
    connect to address 1.0.0.0
    Then, it returns a "connection time out" message

    (b)if I reboot the client machine in windows, I reach the remote
    machine via ssh (providing indifferently hostname, or ip-address)
    without problems

    (c)in linux, if I do
    host

    and then

    ssh

    then ssh works.

    thanks all for suggestions


  4. Re: issue with name resolution

    On 2005-11-28, gcorani@gmail.com wrote:
    > (a) my ssh client do work correctly with ip-addresses, but wrongly with
    > hostnames.
    > By using ssh -v, I discovered that it tries always to
    > connect to address 1.0.0.0
    > Then, it returns a "connection time out" message


    I'm wondering if something along the line is misinterpretting a
    "-1" meaning failure as an IP address. Do you have the name service
    cache (nscd) running, and if so does stopping it make any difference?

    Do you have multiple nameservers listed in /etc/resolv.conf and do they
    all work? What SSH software and version is this?

    I suspect that strace'ing ssh during the failure will provide a clue as
    to where the bogus address is coming from.

    --
    Darren Tucker (dtucker at zip.com.au)
    GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
    usually comes from bad judgement.

+ Reply to Thread