How can it be that ssh somename works, while nslookup somename does not?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







16















How to know the IP address of some host somename I can ssh to? If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?





Neither /etc/hosts nor .ssh/config explanation worked.





EDIT



Sorry somename is fully qualified.



ssh somename.somedomain


works, while



ping somename.somedomain


and



nslookup somename.somedomain


don't










share|improve this question




















  • 12





    Is it listed in /etc/hosts or ~/.ssh/config?

    – Stephen Kitt
    May 7 at 10:14






  • 1





    The name could also be resolved using mDNS (Multicast DNS) or LLMNR (Link-Local Multicast Name Resolution).

    – Johan Myréen
    May 7 at 10:26











  • It may have an entry in your .ssh/config file

    – Tagwint
    May 7 at 10:31






  • 1





    @Dims You could try pinging somename.local. .local is a special domain reserved for mDNS. For LLMNR you could use this NMAP script.

    – Johan Myréen
    May 7 at 15:55






  • 2





    @mckenzm no, it won’t.

    – Stephen Kitt
    May 8 at 8:05


















16















How to know the IP address of some host somename I can ssh to? If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?





Neither /etc/hosts nor .ssh/config explanation worked.





EDIT



Sorry somename is fully qualified.



ssh somename.somedomain


works, while



ping somename.somedomain


and



nslookup somename.somedomain


don't










share|improve this question




















  • 12





    Is it listed in /etc/hosts or ~/.ssh/config?

    – Stephen Kitt
    May 7 at 10:14






  • 1





    The name could also be resolved using mDNS (Multicast DNS) or LLMNR (Link-Local Multicast Name Resolution).

    – Johan Myréen
    May 7 at 10:26











  • It may have an entry in your .ssh/config file

    – Tagwint
    May 7 at 10:31






  • 1





    @Dims You could try pinging somename.local. .local is a special domain reserved for mDNS. For LLMNR you could use this NMAP script.

    – Johan Myréen
    May 7 at 15:55






  • 2





    @mckenzm no, it won’t.

    – Stephen Kitt
    May 8 at 8:05














16












16








16








How to know the IP address of some host somename I can ssh to? If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?





Neither /etc/hosts nor .ssh/config explanation worked.





EDIT



Sorry somename is fully qualified.



ssh somename.somedomain


works, while



ping somename.somedomain


and



nslookup somename.somedomain


don't










share|improve this question
















How to know the IP address of some host somename I can ssh to? If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?





Neither /etc/hosts nor .ssh/config explanation worked.





EDIT



Sorry somename is fully qualified.



ssh somename.somedomain


works, while



ping somename.somedomain


and



nslookup somename.somedomain


don't







ssh nslookup host-name-resolution






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 8 at 14:00









Philip Couling

3,63811427




3,63811427










asked May 7 at 10:06









DimsDims

47711035




47711035








  • 12





    Is it listed in /etc/hosts or ~/.ssh/config?

    – Stephen Kitt
    May 7 at 10:14






  • 1





    The name could also be resolved using mDNS (Multicast DNS) or LLMNR (Link-Local Multicast Name Resolution).

    – Johan Myréen
    May 7 at 10:26











  • It may have an entry in your .ssh/config file

    – Tagwint
    May 7 at 10:31






  • 1





    @Dims You could try pinging somename.local. .local is a special domain reserved for mDNS. For LLMNR you could use this NMAP script.

    – Johan Myréen
    May 7 at 15:55






  • 2





    @mckenzm no, it won’t.

    – Stephen Kitt
    May 8 at 8:05














  • 12





    Is it listed in /etc/hosts or ~/.ssh/config?

    – Stephen Kitt
    May 7 at 10:14






  • 1





    The name could also be resolved using mDNS (Multicast DNS) or LLMNR (Link-Local Multicast Name Resolution).

    – Johan Myréen
    May 7 at 10:26











  • It may have an entry in your .ssh/config file

    – Tagwint
    May 7 at 10:31






  • 1





    @Dims You could try pinging somename.local. .local is a special domain reserved for mDNS. For LLMNR you could use this NMAP script.

    – Johan Myréen
    May 7 at 15:55






  • 2





    @mckenzm no, it won’t.

    – Stephen Kitt
    May 8 at 8:05








12




12





Is it listed in /etc/hosts or ~/.ssh/config?

– Stephen Kitt
May 7 at 10:14





Is it listed in /etc/hosts or ~/.ssh/config?

– Stephen Kitt
May 7 at 10:14




1




1





The name could also be resolved using mDNS (Multicast DNS) or LLMNR (Link-Local Multicast Name Resolution).

– Johan Myréen
May 7 at 10:26





The name could also be resolved using mDNS (Multicast DNS) or LLMNR (Link-Local Multicast Name Resolution).

– Johan Myréen
May 7 at 10:26













It may have an entry in your .ssh/config file

– Tagwint
May 7 at 10:31





It may have an entry in your .ssh/config file

– Tagwint
May 7 at 10:31




1




1





@Dims You could try pinging somename.local. .local is a special domain reserved for mDNS. For LLMNR you could use this NMAP script.

– Johan Myréen
May 7 at 15:55





@Dims You could try pinging somename.local. .local is a special domain reserved for mDNS. For LLMNR you could use this NMAP script.

– Johan Myréen
May 7 at 15:55




2




2





@mckenzm no, it won’t.

– Stephen Kitt
May 8 at 8:05





@mckenzm no, it won’t.

– Stephen Kitt
May 8 at 8:05










3 Answers
3






active

oldest

votes


















30














Nslookup is a program to query Internet domain name servers. Nslookup is very good for querying DNS servers but it does not give you the whole picture when it comes to name resolution.



On Linux name resolution is most commonly controlled by NSS which is configured by /etc/nsswitch.conf. Specifically, this configuration contains a hosts entry. For example:



hosts:          files dns


In the above entry you can see that the first thing to be queried is files followed by dns, meaning that /etc/hosts will be queried before DNS. Other options exist including LDAP, Multicast DNS and WINS.



Answering your question directly, SSH resolves the hostname to an IP address using NSS (pulling results from multiple sources) where nslookup only queries the DNS.



You can check to see which IP NSS resolves a hostname to using getent. For example to resolve somename:



getent hosts somename




Also In the case of SSH you can configure host specific information in /etc/ssh/ssh_config and ~/.ssh/config. This will even let you specify an IP address for a hostname, entirely skipping name resolution.:



The following tells SSH to use 192.168.1.25 for both dev and dev.example.com. SSH will use this address whether or not these names exist as DNS names for a different IP:



# contents of $HOME/.ssh/config
Host dev dev.example.com
HostName 192.168.1.25





share|improve this answer

































    10















    How to know the IP address of some host somename I can ssh to?




    Use the verbose flag (-v) of the ssh command:



    ssh somename -v


    The output should contain, among other things, a line that shows the resolved IP of the server you are connecting to:



    debug1: Connecting to aur.archlinux.org [5.9.250.164] port 22.





    If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?




    The most probable cause of ssh being able to resolve a hostname that nslookup cannot is that it is configured at the ssh level.



    Per the ssh_config(5) manual page, there are three places where ssh looks at for config files:





    1. command-line options

    2. user's configuration file (~/.ssh/config)

    3. system-wide configuration file (/etc/ssh/ssh_config)




    One of these files may contain your hostname somename (or a pattern that matches it) as an alias of another hostname or IP. For example:



    # explicit alias of somename to 8.8.8.8 IP
    Host somename
    HostName 8.8.8.8

    # pattern alias (that obviously matches somename) to another hostname
    # that is itself resolved via DNS (and that can be nslookup-ed).
    Host *
    HostName anotherhostname


    Please refer to the ssh_config(5) manual page explanations of Host and HostName directives and to the PATTERNS section for more information.






    share|improve this answer


























    • This answer does not answer the question, which was how a host name is recognized, even if it is not server by a DNS server.

      – Johan Myréen
      May 7 at 15:54






    • 1





      The answer correctly mentions very probable scenario where ssh user@someserver seems to "resolve" the someserver DNS name (even if this does not actually happen). If the Host someserver is configured in .ssh/config file, it is then possible to use the ssh command exactly as OP states even if the someserver is not in the DNS at all.

      – Fiisch
      May 7 at 18:32








    • 2





      @JohanMyréen The output from ssh -v somename includes the IP address (regardless of any ssh_config entries). So it directly answers the question "How to know the IP address of some host somename I can ssh to?", as well as being a good first step towards answering "How can it be that ssh somename works...?".

      – JigglyNaga
      May 8 at 11:20



















    4














    Philip is almost there, but heads off down the .ssh/config rathole which it's unlikely you configured.



    The commands...



    getent hosts somename


    ...queries NSS using the hosts: lookup line in /etc/nsswitch.conf, rather than just DNS as nslookup does. It's likely your Unix environment is using more than one naming service; possibly some type of AD integration.






    share|improve this answer





















    • 2





      I wouldn't say I headed off down that route. I added an "also" for completeness.

      – Philip Couling
      May 7 at 19:42











    • @PhilipCouling Sure, but your "pre-also" is incomplete - you're not showing how to arbitrarily resolve a name when the question is about "$thing versus nsloookup".

      – Rich
      May 7 at 20:22






    • 3





      As already commented on the Q, host is normally part of bind-utils (or equivalent) and like both nslookup and dig uses only DNS. OTOH getent hosts (or possibly ahosts) does what you describe.

      – dave_thompson_085
      May 8 at 0:24













    • @dave_thompson_085 Incorrect. host queries other name services. Agreed that getent hosts is the best unambiguous method to query "any configured name services".

      – Rich
      May 8 at 16:07








    • 1





      host is DNS-only per the man pages and confirmed by testing on the systems I use (CentOS, Ubuntu, FreeBSD, Solaris) as well as upstream. Also see the (near)dupes I commented on the Q which also say this.

      – dave_thompson_085
      May 10 at 4:49












    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f517542%2fhow-can-it-be-that-ssh-somename-works-while-nslookup-somename-does-not%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    30














    Nslookup is a program to query Internet domain name servers. Nslookup is very good for querying DNS servers but it does not give you the whole picture when it comes to name resolution.



    On Linux name resolution is most commonly controlled by NSS which is configured by /etc/nsswitch.conf. Specifically, this configuration contains a hosts entry. For example:



    hosts:          files dns


    In the above entry you can see that the first thing to be queried is files followed by dns, meaning that /etc/hosts will be queried before DNS. Other options exist including LDAP, Multicast DNS and WINS.



    Answering your question directly, SSH resolves the hostname to an IP address using NSS (pulling results from multiple sources) where nslookup only queries the DNS.



    You can check to see which IP NSS resolves a hostname to using getent. For example to resolve somename:



    getent hosts somename




    Also In the case of SSH you can configure host specific information in /etc/ssh/ssh_config and ~/.ssh/config. This will even let you specify an IP address for a hostname, entirely skipping name resolution.:



    The following tells SSH to use 192.168.1.25 for both dev and dev.example.com. SSH will use this address whether or not these names exist as DNS names for a different IP:



    # contents of $HOME/.ssh/config
    Host dev dev.example.com
    HostName 192.168.1.25





    share|improve this answer






























      30














      Nslookup is a program to query Internet domain name servers. Nslookup is very good for querying DNS servers but it does not give you the whole picture when it comes to name resolution.



      On Linux name resolution is most commonly controlled by NSS which is configured by /etc/nsswitch.conf. Specifically, this configuration contains a hosts entry. For example:



      hosts:          files dns


      In the above entry you can see that the first thing to be queried is files followed by dns, meaning that /etc/hosts will be queried before DNS. Other options exist including LDAP, Multicast DNS and WINS.



      Answering your question directly, SSH resolves the hostname to an IP address using NSS (pulling results from multiple sources) where nslookup only queries the DNS.



      You can check to see which IP NSS resolves a hostname to using getent. For example to resolve somename:



      getent hosts somename




      Also In the case of SSH you can configure host specific information in /etc/ssh/ssh_config and ~/.ssh/config. This will even let you specify an IP address for a hostname, entirely skipping name resolution.:



      The following tells SSH to use 192.168.1.25 for both dev and dev.example.com. SSH will use this address whether or not these names exist as DNS names for a different IP:



      # contents of $HOME/.ssh/config
      Host dev dev.example.com
      HostName 192.168.1.25





      share|improve this answer




























        30












        30








        30







        Nslookup is a program to query Internet domain name servers. Nslookup is very good for querying DNS servers but it does not give you the whole picture when it comes to name resolution.



        On Linux name resolution is most commonly controlled by NSS which is configured by /etc/nsswitch.conf. Specifically, this configuration contains a hosts entry. For example:



        hosts:          files dns


        In the above entry you can see that the first thing to be queried is files followed by dns, meaning that /etc/hosts will be queried before DNS. Other options exist including LDAP, Multicast DNS and WINS.



        Answering your question directly, SSH resolves the hostname to an IP address using NSS (pulling results from multiple sources) where nslookup only queries the DNS.



        You can check to see which IP NSS resolves a hostname to using getent. For example to resolve somename:



        getent hosts somename




        Also In the case of SSH you can configure host specific information in /etc/ssh/ssh_config and ~/.ssh/config. This will even let you specify an IP address for a hostname, entirely skipping name resolution.:



        The following tells SSH to use 192.168.1.25 for both dev and dev.example.com. SSH will use this address whether or not these names exist as DNS names for a different IP:



        # contents of $HOME/.ssh/config
        Host dev dev.example.com
        HostName 192.168.1.25





        share|improve this answer















        Nslookup is a program to query Internet domain name servers. Nslookup is very good for querying DNS servers but it does not give you the whole picture when it comes to name resolution.



        On Linux name resolution is most commonly controlled by NSS which is configured by /etc/nsswitch.conf. Specifically, this configuration contains a hosts entry. For example:



        hosts:          files dns


        In the above entry you can see that the first thing to be queried is files followed by dns, meaning that /etc/hosts will be queried before DNS. Other options exist including LDAP, Multicast DNS and WINS.



        Answering your question directly, SSH resolves the hostname to an IP address using NSS (pulling results from multiple sources) where nslookup only queries the DNS.



        You can check to see which IP NSS resolves a hostname to using getent. For example to resolve somename:



        getent hosts somename




        Also In the case of SSH you can configure host specific information in /etc/ssh/ssh_config and ~/.ssh/config. This will even let you specify an IP address for a hostname, entirely skipping name resolution.:



        The following tells SSH to use 192.168.1.25 for both dev and dev.example.com. SSH will use this address whether or not these names exist as DNS names for a different IP:



        # contents of $HOME/.ssh/config
        Host dev dev.example.com
        HostName 192.168.1.25






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited May 8 at 14:23

























        answered May 7 at 11:42









        Philip CoulingPhilip Couling

        3,63811427




        3,63811427

























            10















            How to know the IP address of some host somename I can ssh to?




            Use the verbose flag (-v) of the ssh command:



            ssh somename -v


            The output should contain, among other things, a line that shows the resolved IP of the server you are connecting to:



            debug1: Connecting to aur.archlinux.org [5.9.250.164] port 22.





            If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?




            The most probable cause of ssh being able to resolve a hostname that nslookup cannot is that it is configured at the ssh level.



            Per the ssh_config(5) manual page, there are three places where ssh looks at for config files:





            1. command-line options

            2. user's configuration file (~/.ssh/config)

            3. system-wide configuration file (/etc/ssh/ssh_config)




            One of these files may contain your hostname somename (or a pattern that matches it) as an alias of another hostname or IP. For example:



            # explicit alias of somename to 8.8.8.8 IP
            Host somename
            HostName 8.8.8.8

            # pattern alias (that obviously matches somename) to another hostname
            # that is itself resolved via DNS (and that can be nslookup-ed).
            Host *
            HostName anotherhostname


            Please refer to the ssh_config(5) manual page explanations of Host and HostName directives and to the PATTERNS section for more information.






            share|improve this answer


























            • This answer does not answer the question, which was how a host name is recognized, even if it is not server by a DNS server.

              – Johan Myréen
              May 7 at 15:54






            • 1





              The answer correctly mentions very probable scenario where ssh user@someserver seems to "resolve" the someserver DNS name (even if this does not actually happen). If the Host someserver is configured in .ssh/config file, it is then possible to use the ssh command exactly as OP states even if the someserver is not in the DNS at all.

              – Fiisch
              May 7 at 18:32








            • 2





              @JohanMyréen The output from ssh -v somename includes the IP address (regardless of any ssh_config entries). So it directly answers the question "How to know the IP address of some host somename I can ssh to?", as well as being a good first step towards answering "How can it be that ssh somename works...?".

              – JigglyNaga
              May 8 at 11:20
















            10















            How to know the IP address of some host somename I can ssh to?




            Use the verbose flag (-v) of the ssh command:



            ssh somename -v


            The output should contain, among other things, a line that shows the resolved IP of the server you are connecting to:



            debug1: Connecting to aur.archlinux.org [5.9.250.164] port 22.





            If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?




            The most probable cause of ssh being able to resolve a hostname that nslookup cannot is that it is configured at the ssh level.



            Per the ssh_config(5) manual page, there are three places where ssh looks at for config files:





            1. command-line options

            2. user's configuration file (~/.ssh/config)

            3. system-wide configuration file (/etc/ssh/ssh_config)




            One of these files may contain your hostname somename (or a pattern that matches it) as an alias of another hostname or IP. For example:



            # explicit alias of somename to 8.8.8.8 IP
            Host somename
            HostName 8.8.8.8

            # pattern alias (that obviously matches somename) to another hostname
            # that is itself resolved via DNS (and that can be nslookup-ed).
            Host *
            HostName anotherhostname


            Please refer to the ssh_config(5) manual page explanations of Host and HostName directives and to the PATTERNS section for more information.






            share|improve this answer


























            • This answer does not answer the question, which was how a host name is recognized, even if it is not server by a DNS server.

              – Johan Myréen
              May 7 at 15:54






            • 1





              The answer correctly mentions very probable scenario where ssh user@someserver seems to "resolve" the someserver DNS name (even if this does not actually happen). If the Host someserver is configured in .ssh/config file, it is then possible to use the ssh command exactly as OP states even if the someserver is not in the DNS at all.

              – Fiisch
              May 7 at 18:32








            • 2





              @JohanMyréen The output from ssh -v somename includes the IP address (regardless of any ssh_config entries). So it directly answers the question "How to know the IP address of some host somename I can ssh to?", as well as being a good first step towards answering "How can it be that ssh somename works...?".

              – JigglyNaga
              May 8 at 11:20














            10












            10








            10








            How to know the IP address of some host somename I can ssh to?




            Use the verbose flag (-v) of the ssh command:



            ssh somename -v


            The output should contain, among other things, a line that shows the resolved IP of the server you are connecting to:



            debug1: Connecting to aur.archlinux.org [5.9.250.164] port 22.





            If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?




            The most probable cause of ssh being able to resolve a hostname that nslookup cannot is that it is configured at the ssh level.



            Per the ssh_config(5) manual page, there are three places where ssh looks at for config files:





            1. command-line options

            2. user's configuration file (~/.ssh/config)

            3. system-wide configuration file (/etc/ssh/ssh_config)




            One of these files may contain your hostname somename (or a pattern that matches it) as an alias of another hostname or IP. For example:



            # explicit alias of somename to 8.8.8.8 IP
            Host somename
            HostName 8.8.8.8

            # pattern alias (that obviously matches somename) to another hostname
            # that is itself resolved via DNS (and that can be nslookup-ed).
            Host *
            HostName anotherhostname


            Please refer to the ssh_config(5) manual page explanations of Host and HostName directives and to the PATTERNS section for more information.






            share|improve this answer
















            How to know the IP address of some host somename I can ssh to?




            Use the verbose flag (-v) of the ssh command:



            ssh somename -v


            The output should contain, among other things, a line that shows the resolved IP of the server you are connecting to:



            debug1: Connecting to aur.archlinux.org [5.9.250.164] port 22.





            If I do nslookup on this host it says "no answer". How can ssh resolve it's name then?




            The most probable cause of ssh being able to resolve a hostname that nslookup cannot is that it is configured at the ssh level.



            Per the ssh_config(5) manual page, there are three places where ssh looks at for config files:





            1. command-line options

            2. user's configuration file (~/.ssh/config)

            3. system-wide configuration file (/etc/ssh/ssh_config)




            One of these files may contain your hostname somename (or a pattern that matches it) as an alias of another hostname or IP. For example:



            # explicit alias of somename to 8.8.8.8 IP
            Host somename
            HostName 8.8.8.8

            # pattern alias (that obviously matches somename) to another hostname
            # that is itself resolved via DNS (and that can be nslookup-ed).
            Host *
            HostName anotherhostname


            Please refer to the ssh_config(5) manual page explanations of Host and HostName directives and to the PATTERNS section for more information.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited May 7 at 18:13

























            answered May 7 at 15:50









            Jules LamurJules Lamur

            20114




            20114













            • This answer does not answer the question, which was how a host name is recognized, even if it is not server by a DNS server.

              – Johan Myréen
              May 7 at 15:54






            • 1





              The answer correctly mentions very probable scenario where ssh user@someserver seems to "resolve" the someserver DNS name (even if this does not actually happen). If the Host someserver is configured in .ssh/config file, it is then possible to use the ssh command exactly as OP states even if the someserver is not in the DNS at all.

              – Fiisch
              May 7 at 18:32








            • 2





              @JohanMyréen The output from ssh -v somename includes the IP address (regardless of any ssh_config entries). So it directly answers the question "How to know the IP address of some host somename I can ssh to?", as well as being a good first step towards answering "How can it be that ssh somename works...?".

              – JigglyNaga
              May 8 at 11:20



















            • This answer does not answer the question, which was how a host name is recognized, even if it is not server by a DNS server.

              – Johan Myréen
              May 7 at 15:54






            • 1





              The answer correctly mentions very probable scenario where ssh user@someserver seems to "resolve" the someserver DNS name (even if this does not actually happen). If the Host someserver is configured in .ssh/config file, it is then possible to use the ssh command exactly as OP states even if the someserver is not in the DNS at all.

              – Fiisch
              May 7 at 18:32








            • 2





              @JohanMyréen The output from ssh -v somename includes the IP address (regardless of any ssh_config entries). So it directly answers the question "How to know the IP address of some host somename I can ssh to?", as well as being a good first step towards answering "How can it be that ssh somename works...?".

              – JigglyNaga
              May 8 at 11:20

















            This answer does not answer the question, which was how a host name is recognized, even if it is not server by a DNS server.

            – Johan Myréen
            May 7 at 15:54





            This answer does not answer the question, which was how a host name is recognized, even if it is not server by a DNS server.

            – Johan Myréen
            May 7 at 15:54




            1




            1





            The answer correctly mentions very probable scenario where ssh user@someserver seems to "resolve" the someserver DNS name (even if this does not actually happen). If the Host someserver is configured in .ssh/config file, it is then possible to use the ssh command exactly as OP states even if the someserver is not in the DNS at all.

            – Fiisch
            May 7 at 18:32







            The answer correctly mentions very probable scenario where ssh user@someserver seems to "resolve" the someserver DNS name (even if this does not actually happen). If the Host someserver is configured in .ssh/config file, it is then possible to use the ssh command exactly as OP states even if the someserver is not in the DNS at all.

            – Fiisch
            May 7 at 18:32






            2




            2





            @JohanMyréen The output from ssh -v somename includes the IP address (regardless of any ssh_config entries). So it directly answers the question "How to know the IP address of some host somename I can ssh to?", as well as being a good first step towards answering "How can it be that ssh somename works...?".

            – JigglyNaga
            May 8 at 11:20





            @JohanMyréen The output from ssh -v somename includes the IP address (regardless of any ssh_config entries). So it directly answers the question "How to know the IP address of some host somename I can ssh to?", as well as being a good first step towards answering "How can it be that ssh somename works...?".

            – JigglyNaga
            May 8 at 11:20











            4














            Philip is almost there, but heads off down the .ssh/config rathole which it's unlikely you configured.



            The commands...



            getent hosts somename


            ...queries NSS using the hosts: lookup line in /etc/nsswitch.conf, rather than just DNS as nslookup does. It's likely your Unix environment is using more than one naming service; possibly some type of AD integration.






            share|improve this answer





















            • 2





              I wouldn't say I headed off down that route. I added an "also" for completeness.

              – Philip Couling
              May 7 at 19:42











            • @PhilipCouling Sure, but your "pre-also" is incomplete - you're not showing how to arbitrarily resolve a name when the question is about "$thing versus nsloookup".

              – Rich
              May 7 at 20:22






            • 3





              As already commented on the Q, host is normally part of bind-utils (or equivalent) and like both nslookup and dig uses only DNS. OTOH getent hosts (or possibly ahosts) does what you describe.

              – dave_thompson_085
              May 8 at 0:24













            • @dave_thompson_085 Incorrect. host queries other name services. Agreed that getent hosts is the best unambiguous method to query "any configured name services".

              – Rich
              May 8 at 16:07








            • 1





              host is DNS-only per the man pages and confirmed by testing on the systems I use (CentOS, Ubuntu, FreeBSD, Solaris) as well as upstream. Also see the (near)dupes I commented on the Q which also say this.

              – dave_thompson_085
              May 10 at 4:49
















            4














            Philip is almost there, but heads off down the .ssh/config rathole which it's unlikely you configured.



            The commands...



            getent hosts somename


            ...queries NSS using the hosts: lookup line in /etc/nsswitch.conf, rather than just DNS as nslookup does. It's likely your Unix environment is using more than one naming service; possibly some type of AD integration.






            share|improve this answer





















            • 2





              I wouldn't say I headed off down that route. I added an "also" for completeness.

              – Philip Couling
              May 7 at 19:42











            • @PhilipCouling Sure, but your "pre-also" is incomplete - you're not showing how to arbitrarily resolve a name when the question is about "$thing versus nsloookup".

              – Rich
              May 7 at 20:22






            • 3





              As already commented on the Q, host is normally part of bind-utils (or equivalent) and like both nslookup and dig uses only DNS. OTOH getent hosts (or possibly ahosts) does what you describe.

              – dave_thompson_085
              May 8 at 0:24













            • @dave_thompson_085 Incorrect. host queries other name services. Agreed that getent hosts is the best unambiguous method to query "any configured name services".

              – Rich
              May 8 at 16:07








            • 1





              host is DNS-only per the man pages and confirmed by testing on the systems I use (CentOS, Ubuntu, FreeBSD, Solaris) as well as upstream. Also see the (near)dupes I commented on the Q which also say this.

              – dave_thompson_085
              May 10 at 4:49














            4












            4








            4







            Philip is almost there, but heads off down the .ssh/config rathole which it's unlikely you configured.



            The commands...



            getent hosts somename


            ...queries NSS using the hosts: lookup line in /etc/nsswitch.conf, rather than just DNS as nslookup does. It's likely your Unix environment is using more than one naming service; possibly some type of AD integration.






            share|improve this answer















            Philip is almost there, but heads off down the .ssh/config rathole which it's unlikely you configured.



            The commands...



            getent hosts somename


            ...queries NSS using the hosts: lookup line in /etc/nsswitch.conf, rather than just DNS as nslookup does. It's likely your Unix environment is using more than one naming service; possibly some type of AD integration.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited May 15 at 0:50

























            answered May 7 at 17:16









            RichRich

            417312




            417312








            • 2





              I wouldn't say I headed off down that route. I added an "also" for completeness.

              – Philip Couling
              May 7 at 19:42











            • @PhilipCouling Sure, but your "pre-also" is incomplete - you're not showing how to arbitrarily resolve a name when the question is about "$thing versus nsloookup".

              – Rich
              May 7 at 20:22






            • 3





              As already commented on the Q, host is normally part of bind-utils (or equivalent) and like both nslookup and dig uses only DNS. OTOH getent hosts (or possibly ahosts) does what you describe.

              – dave_thompson_085
              May 8 at 0:24













            • @dave_thompson_085 Incorrect. host queries other name services. Agreed that getent hosts is the best unambiguous method to query "any configured name services".

              – Rich
              May 8 at 16:07








            • 1





              host is DNS-only per the man pages and confirmed by testing on the systems I use (CentOS, Ubuntu, FreeBSD, Solaris) as well as upstream. Also see the (near)dupes I commented on the Q which also say this.

              – dave_thompson_085
              May 10 at 4:49














            • 2





              I wouldn't say I headed off down that route. I added an "also" for completeness.

              – Philip Couling
              May 7 at 19:42











            • @PhilipCouling Sure, but your "pre-also" is incomplete - you're not showing how to arbitrarily resolve a name when the question is about "$thing versus nsloookup".

              – Rich
              May 7 at 20:22






            • 3





              As already commented on the Q, host is normally part of bind-utils (or equivalent) and like both nslookup and dig uses only DNS. OTOH getent hosts (or possibly ahosts) does what you describe.

              – dave_thompson_085
              May 8 at 0:24













            • @dave_thompson_085 Incorrect. host queries other name services. Agreed that getent hosts is the best unambiguous method to query "any configured name services".

              – Rich
              May 8 at 16:07








            • 1





              host is DNS-only per the man pages and confirmed by testing on the systems I use (CentOS, Ubuntu, FreeBSD, Solaris) as well as upstream. Also see the (near)dupes I commented on the Q which also say this.

              – dave_thompson_085
              May 10 at 4:49








            2




            2





            I wouldn't say I headed off down that route. I added an "also" for completeness.

            – Philip Couling
            May 7 at 19:42





            I wouldn't say I headed off down that route. I added an "also" for completeness.

            – Philip Couling
            May 7 at 19:42













            @PhilipCouling Sure, but your "pre-also" is incomplete - you're not showing how to arbitrarily resolve a name when the question is about "$thing versus nsloookup".

            – Rich
            May 7 at 20:22





            @PhilipCouling Sure, but your "pre-also" is incomplete - you're not showing how to arbitrarily resolve a name when the question is about "$thing versus nsloookup".

            – Rich
            May 7 at 20:22




            3




            3





            As already commented on the Q, host is normally part of bind-utils (or equivalent) and like both nslookup and dig uses only DNS. OTOH getent hosts (or possibly ahosts) does what you describe.

            – dave_thompson_085
            May 8 at 0:24







            As already commented on the Q, host is normally part of bind-utils (or equivalent) and like both nslookup and dig uses only DNS. OTOH getent hosts (or possibly ahosts) does what you describe.

            – dave_thompson_085
            May 8 at 0:24















            @dave_thompson_085 Incorrect. host queries other name services. Agreed that getent hosts is the best unambiguous method to query "any configured name services".

            – Rich
            May 8 at 16:07







            @dave_thompson_085 Incorrect. host queries other name services. Agreed that getent hosts is the best unambiguous method to query "any configured name services".

            – Rich
            May 8 at 16:07






            1




            1





            host is DNS-only per the man pages and confirmed by testing on the systems I use (CentOS, Ubuntu, FreeBSD, Solaris) as well as upstream. Also see the (near)dupes I commented on the Q which also say this.

            – dave_thompson_085
            May 10 at 4:49





            host is DNS-only per the man pages and confirmed by testing on the systems I use (CentOS, Ubuntu, FreeBSD, Solaris) as well as upstream. Also see the (near)dupes I commented on the Q which also say this.

            – dave_thompson_085
            May 10 at 4:49


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f517542%2fhow-can-it-be-that-ssh-somename-works-while-nslookup-somename-does-not%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

            He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

            Slayer Innehåll Historia | Stil, komposition och lyrik | Bandets betydelse och framgångar | Sidoprojekt och samarbeten | Kontroverser | Medlemmar | Utmärkelser och nomineringar | Turnéer och festivaler | Diskografi | Referenser | Externa länkar | Navigeringsmenywww.slayer.net”Metal Massacre vol. 1””Metal Massacre vol. 3””Metal Massacre Volume III””Show No Mercy””Haunting the Chapel””Live Undead””Hell Awaits””Reign in Blood””Reign in Blood””Gold & Platinum – Reign in Blood””Golden Gods Awards Winners”originalet”Kerrang! Hall Of Fame””Slayer Looks Back On 37-Year Career In New Video Series: Part Two””South of Heaven””Gold & Platinum – South of Heaven””Seasons in the Abyss””Gold & Platinum - Seasons in the Abyss””Divine Intervention””Divine Intervention - Release group by Slayer””Gold & Platinum - Divine Intervention””Live Intrusion””Undisputed Attitude””Abolish Government/Superficial Love””Release “Slatanic Slaughter: A Tribute to Slayer” by Various Artists””Diabolus in Musica””Soundtrack to the Apocalypse””God Hates Us All””Systematic - Relationships””War at the Warfield””Gold & Platinum - War at the Warfield””Soundtrack to the Apocalypse””Gold & Platinum - Still Reigning””Metallica, Slayer, Iron Mauden Among Winners At Metal Hammer Awards””Eternal Pyre””Eternal Pyre - Slayer release group””Eternal Pyre””Metal Storm Awards 2006””Kerrang! Hall Of Fame””Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Bullet-For My Valentine booed at Metal Hammer Golden Gods Awards””Unholy Aliance””The End Of Slayer?””Slayer: We Could Thrash Out Two More Albums If We're Fast Enough...””'The Unholy Alliance: Chapter III' UK Dates Added”originalet”Megadeth And Slayer To Co-Headline 'Canadian Carnage' Trek”originalet”World Painted Blood””Release “World Painted Blood” by Slayer””Metallica Heading To Cinemas””Slayer, Megadeth To Join Forces For 'European Carnage' Tour - Dec. 18, 2010”originalet”Slayer's Hanneman Contracts Acute Infection; Band To Bring In Guest Guitarist””Cannibal Corpse's Pat O'Brien Will Step In As Slayer's Guest Guitarist”originalet”Slayer’s Jeff Hanneman Dead at 49””Dave Lombardo Says He Made Only $67,000 In 2011 While Touring With Slayer””Slayer: We Do Not Agree With Dave Lombardo's Substance Or Timeline Of Events””Slayer Welcomes Drummer Paul Bostaph Back To The Fold””Slayer Hope to Unveil Never-Before-Heard Jeff Hanneman Material on Next Album””Slayer Debut New Song 'Implode' During Surprise Golden Gods Appearance””Release group Repentless by Slayer””Repentless - Slayer - Credits””Slayer””Metal Storm Awards 2015””Slayer - to release comic book "Repentless #1"””Slayer To Release 'Repentless' 6.66" Vinyl Box Set””BREAKING NEWS: Slayer Announce Farewell Tour””Slayer Recruit Lamb of God, Anthrax, Behemoth + Testament for Final Tour””Slayer lägger ner efter 37 år””Slayer Announces Second North American Leg Of 'Final' Tour””Final World Tour””Slayer Announces Final European Tour With Lamb of God, Anthrax And Obituary””Slayer To Tour Europe With Lamb of God, Anthrax And Obituary””Slayer To Play 'Last French Show Ever' At Next Year's Hellfst””Slayer's Final World Tour Will Extend Into 2019””Death Angel's Rob Cavestany On Slayer's 'Farewell' Tour: 'Some Of Us Could See This Coming'””Testament Has No Plans To Retire Anytime Soon, Says Chuck Billy””Anthrax's Scott Ian On Slayer's 'Farewell' Tour Plans: 'I Was Surprised And I Wasn't Surprised'””Slayer””Slayer's Morbid Schlock””Review/Rock; For Slayer, the Mania Is the Message””Slayer - Biography””Slayer - Reign In Blood”originalet”Dave Lombardo””An exclusive oral history of Slayer”originalet”Exclusive! Interview With Slayer Guitarist Jeff Hanneman”originalet”Thinking Out Loud: Slayer's Kerry King on hair metal, Satan and being polite””Slayer Lyrics””Slayer - Biography””Most influential artists for extreme metal music””Slayer - Reign in Blood””Slayer guitarist Jeff Hanneman dies aged 49””Slatanic Slaughter: A Tribute to Slayer””Gateway to Hell: A Tribute to Slayer””Covered In Blood””Slayer: The Origins of Thrash in San Francisco, CA.””Why They Rule - #6 Slayer”originalet”Guitar World's 100 Greatest Heavy Metal Guitarists Of All Time”originalet”The fans have spoken: Slayer comes out on top in readers' polls”originalet”Tribute to Jeff Hanneman (1964-2013)””Lamb Of God Frontman: We Sound Like A Slayer Rip-Off””BEHEMOTH Frontman Pays Tribute To SLAYER's JEFF HANNEMAN””Slayer, Hatebreed Doing Double Duty On This Year's Ozzfest””System of a Down””Lacuna Coil’s Andrea Ferro Talks Influences, Skateboarding, Band Origins + More””Slayer - Reign in Blood””Into The Lungs of Hell””Slayer rules - en utställning om fans””Slayer and Their Fans Slashed Through a No-Holds-Barred Night at Gas Monkey””Home””Slayer””Gold & Platinum - The Big 4 Live from Sofia, Bulgaria””Exclusive! Interview With Slayer Guitarist Kerry King””2008-02-23: Wiltern, Los Angeles, CA, USA””Slayer's Kerry King To Perform With Megadeth Tonight! - Oct. 21, 2010”originalet”Dave Lombardo - Biography”Slayer Case DismissedArkiveradUltimate Classic Rock: Slayer guitarist Jeff Hanneman dead at 49.”Slayer: "We could never do any thing like Some Kind Of Monster..."””Cannibal Corpse'S Pat O'Brien Will Step In As Slayer'S Guest Guitarist | The Official Slayer Site”originalet”Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Kerrang! Awards 2006 Blog: Kerrang! Hall Of Fame””Kerrang! Awards 2013: Kerrang! Legend”originalet”Metallica, Slayer, Iron Maien Among Winners At Metal Hammer Awards””Metal Hammer Golden Gods Awards””Bullet For My Valentine Booed At Metal Hammer Golden Gods Awards””Metal Storm Awards 2006””Metal Storm Awards 2015””Slayer's Concert History””Slayer - Relationships””Slayer - Releases”Slayers officiella webbplatsSlayer på MusicBrainzOfficiell webbplatsSlayerSlayerr1373445760000 0001 1540 47353068615-5086262726cb13906545x(data)6033143kn20030215029