<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Nameserver setting in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793582#M2316</link>
    <description>My new setup linux server is quite slow now when conneting (telnet)from client , someone said to me , it would be better if modify the ??? resolv.conf ??? , what nameserver should I add to? How do I modify it to improve the connection speed? Thanks.&lt;BR /&gt;</description>
    <pubDate>Mon, 26 Aug 2002 01:01:40 GMT</pubDate>
    <dc:creator>O'lnes</dc:creator>
    <dc:date>2002-08-26T01:01:40Z</dc:date>
    <item>
      <title>Nameserver setting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793582#M2316</link>
      <description>My new setup linux server is quite slow now when conneting (telnet)from client , someone said to me , it would be better if modify the ??? resolv.conf ??? , what nameserver should I add to? How do I modify it to improve the connection speed? Thanks.&lt;BR /&gt;</description>
      <pubDate>Mon, 26 Aug 2002 01:01:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793582#M2316</guid>
      <dc:creator>O'lnes</dc:creator>
      <dc:date>2002-08-26T01:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: Nameserver setting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793583#M2317</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I guess "someone" try to give you advice that hostname resolution cause your problem.&lt;BR /&gt;If you want to do trouble shoot,&lt;BR /&gt;check following.&lt;BR /&gt;&lt;BR /&gt;1) telnet to server ip &lt;BR /&gt;2) telnet to server hostname&lt;BR /&gt;3) do "nslookup client ip" on the server.&lt;BR /&gt;4) do "nslookup client hostname" on the server&lt;BR /&gt;5) do "nslookup server ip" on the client.&lt;BR /&gt;6) do "nslookup server hostname" on the client.&lt;BR /&gt;&lt;BR /&gt;If all DNS information are configured without problem, you will find no difference in the tests.&lt;BR /&gt;If "telnet to IP" = "telnet to hostname", then you need to find another reason.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; what nameserver should I add?&lt;BR /&gt;Are they on the Internet or LAN?&lt;BR /&gt;&lt;BR /&gt;Also check /etc/nsswitch.conf.&lt;BR /&gt;This file control which method to use when name lookup required.&lt;BR /&gt;&lt;BR /&gt;good luck&lt;BR /&gt;</description>
      <pubDate>Mon, 26 Aug 2002 02:17:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793583#M2317</guid>
      <dc:creator>I_M</dc:creator>
      <dc:date>2002-08-26T02:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Nameserver setting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793584#M2318</link>
      <description>Slow connections like that can be caused by linux trying to do a reverse lookup on the IP that's connecting: I've noticed it particularly with SSH but I am not sure if telnetd does it.&lt;BR /&gt;&lt;BR /&gt;In any case, if you're on a small LAN the chances are you wont have any name servers, so adding arbitrary ones to resolv.conf wont help.&lt;BR /&gt;&lt;BR /&gt;You could try adding the client workstation to /etc/hosts, so linux will know the hostname of the IP which connects. So for example, your /etc/hosts might look like this:&lt;BR /&gt;&lt;BR /&gt;127.0.0.1    banana localhost.localdomain&lt;BR /&gt;&lt;CLIENT ip=""&gt;   &lt;CLIENT host=""&gt;&lt;BR /&gt;&lt;BR /&gt;HTH.&lt;/CLIENT&gt;&lt;/CLIENT&gt;</description>
      <pubDate>Thu, 29 Aug 2002 09:09:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793584#M2318</guid>
      <dc:creator>Philip Burrow</dc:creator>
      <dc:date>2002-08-29T09:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: Nameserver setting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793585#M2319</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;some fundamental informations:&lt;BR /&gt;in most cases there are 3 kinds of nameservices: files, dns and nis.&lt;BR /&gt;First check your /etc/nsswitch.conf file. In this file it is configured, which service the system use in which order.&lt;BR /&gt;the system tries first the first entry and so on.&lt;BR /&gt;for example:&lt;BR /&gt;hosts: files dns&lt;BR /&gt;means, if a programm tries to resolv a systemname from a known IP-adress or a IP-adress from a known systemname it looks first in the file /etc/hosts. If resolv is successful, procedure stops. Otherwise the system send a request to a configured dns-server. nis is not used in this example.&lt;BR /&gt;If dns is used, the next important file is /etc/resolv.conf. In this file you configure the ip-adress of one or more dns-servers and the domains to search for adresses.&lt;BR /&gt;It's a good idea to configure first files to reduce network traffic.&lt;BR /&gt;For configuring a dns server you of course must know if there is one reachable.&lt;BR /&gt;&lt;BR /&gt;Some tips:&lt;BR /&gt;- if you have a dns-server its important that the dns-tables are actual. Your new linux-server must be register on the dns server in both directions (name-&amp;gt;ip, ip-&amp;gt;name)&lt;BR /&gt;- to speed up your performance you can configure you linux server as a caching only dns server. That means, the linux server cached all dns information he has once requested from the dns server.&lt;BR /&gt;&lt;BR /&gt;hope this is helpful&lt;BR /&gt;Dirk&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Aug 2002 09:47:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nameserver-setting/m-p/2793585#M2319</guid>
      <dc:creator>Dirk Wiedemann</dc:creator>
      <dc:date>2002-08-29T09:47:58Z</dc:date>
    </item>
  </channel>
</rss>

