<?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 Re: dns resolving timeouts in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659587#M47899</link>
    <description>root@grecopr2:/# nslookup grecopr2&lt;BR /&gt;Using /etc/hosts on:  grecopr2&lt;BR /&gt;&lt;BR /&gt;looking up FILES&lt;BR /&gt;Name:    grecopr2&lt;BR /&gt;Address:  10.15.7.22&lt;BR /&gt;Aliases:  grecopr2.&lt;BR /&gt;&lt;BR /&gt;root@grecopr2:/# nslookup 10.5.7.22&lt;BR /&gt;Using /etc/hosts on:  grecopr2&lt;BR /&gt;&lt;BR /&gt;looking up FILES&lt;BR /&gt;*** No hostname information is available for "10.5.7.22"&lt;BR /&gt;root@grecopr2:/#&lt;BR /&gt;&lt;BR /&gt;Yes, grecopr2 is the name of the machine.&lt;BR /&gt;&lt;BR /&gt;The content of /etc/hosts is:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;10.15.7.22      grecopr2 grecopr2.&lt;BR /&gt;10.15.7.23      grecods                 &lt;BR /&gt;10.15.7.21      grecopr1                  &lt;BR /&gt;10.15.7.27      tareadb                 &lt;BR /&gt;10.15.7.25      tareaap1                  &lt;BR /&gt;10.15.7.26      tareaap2                  &lt;BR /&gt;10.15.7.24      tareads                 &lt;BR /&gt;10.15.7.28      pkgsap&lt;BR /&gt;10.15.7.29      grecopkg&lt;BR /&gt;135.10.0.6      greco01&lt;BR /&gt;127.0.0.1       localhost       loopback localhost.grecopr2.grecopr2&lt;BR /&gt;10.15.6.1       sapdesa&lt;BR /&gt;135.10.0.2 EH02&lt;BR /&gt;&lt;BR /&gt;But I insist: qmail doesn't use /etc/hosts for dns query</description>
    <pubDate>Wed, 06 Feb 2002 13:20:25 GMT</pubDate>
    <dc:creator>Ruben Cardenal</dc:creator>
    <dc:date>2002-02-06T13:20:25Z</dc:date>
    <item>
      <title>dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659578#M47890</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;Well, this is a qmail &amp;amp; dns related question. I have qmail installed in one of my HP9000 servers. That server collects logs, etc, from other machines via e-mail. Later, through POP3, I read messages in the accont where they arrive. But there's a little problem (in fact, a timeout). As these machines are isolated from the internet, they do not use DNS. When I do this:&lt;BR /&gt;&lt;BR /&gt;root@grecopr2:/# telnet localhost 110&lt;BR /&gt;Trying...&lt;BR /&gt;Connected to localhost.&lt;BR /&gt;Escape character is '^]'.&lt;BR /&gt;+OK &amp;lt;18155.1012994166@grecopr2&amp;gt;&lt;BR /&gt;&lt;BR /&gt;Before the last line, there's a delay of 30 seconds, which is the time the dns gives a timeout because it can't resolve the machine name. After that, messages can be, of course, readed properly. As qmail is a daemon that does *NOT* read /etc/hosts, it's not a solution for me to put machine address machine IP in that file. I need another way for dns to resolve at least my local machine IP for POP3 logins to be done quickly. I hope I have explained myself well :)&lt;BR /&gt;&lt;BR /&gt;TIA</description>
      <pubDate>Wed, 06 Feb 2002 11:19:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659578#M47890</guid>
      <dc:creator>Ruben Cardenal</dc:creator>
      <dc:date>2002-02-06T11:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659579#M47891</link>
      <description>Hi,&lt;BR /&gt;I'm not quite clear as to why qmail would not use /etc/hosts. Doesn't that depend on what is in /etc/nsswitch.conf ? If there's a line in there like ...&lt;BR /&gt;hosts:       files&lt;BR /&gt;... why wouldn't qmail then use /etc/hosts ?&lt;BR /&gt;&lt;BR /&gt;Maybe you could post your /etc/nsswitch.conf file ?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Tom Geudens</description>
      <pubDate>Wed, 06 Feb 2002 12:12:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659579#M47891</guid>
      <dc:creator>Tom Geudens</dc:creator>
      <dc:date>2002-02-06T12:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659580#M47892</link>
      <description>The /etc/nsswitch.conf has the correct entries, such as &lt;BR /&gt;hosts:        files&lt;BR /&gt;&lt;BR /&gt;qmail daemon tries to do dns inquiries from a dns server, and doesn't take care of /etc/hosts file.</description>
      <pubDate>Wed, 06 Feb 2002 12:27:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659580#M47892</guid>
      <dc:creator>Ruben Cardenal</dc:creator>
      <dc:date>2002-02-06T12:27:46Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659581#M47893</link>
      <description>What does&lt;BR /&gt;&lt;BR /&gt;/etc/resolv.conf&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;say?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Wed, 06 Feb 2002 12:32:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659581#M47893</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-02-06T12:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659582#M47894</link>
      <description>i tried browsing through the source of the qmail (v1.03) DNS query routines and to me it seems like they use the resolver library underneath. are you sure you're not having a resolver library configuration problem?</description>
      <pubDate>Wed, 06 Feb 2002 12:50:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659582#M47894</guid>
      <dc:creator>marko asplund</dc:creator>
      <dc:date>2002-02-06T12:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659583#M47895</link>
      <description>Harry: that file doesn't exist in these machines.&lt;BR /&gt;&lt;BR /&gt;Marko: I's not that kind of problem...</description>
      <pubDate>Wed, 06 Feb 2002 12:55:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659583#M47895</guid>
      <dc:creator>Ruben Cardenal</dc:creator>
      <dc:date>2002-02-06T12:55:39Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659584#M47896</link>
      <description>Hi,&lt;BR /&gt;I had a look through &lt;A href="http://www.lifewithqmail.org/" target="_blank"&gt;http://www.lifewithqmail.org/&lt;/A&gt;&lt;BR /&gt;and came up with the smtproutes parameter, which (according to the document) should be used when there's no dns available.&lt;BR /&gt;&lt;BR /&gt;You probably looked at this already ... but ...&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Tom Geudens</description>
      <pubDate>Wed, 06 Feb 2002 13:06:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659584#M47896</guid>
      <dc:creator>Tom Geudens</dc:creator>
      <dc:date>2002-02-06T13:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659585#M47897</link>
      <description>Tom: smtproutes is for SMTP'ing purposes, not POP3 related :(</description>
      <pubDate>Wed, 06 Feb 2002 13:12:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659585#M47897</guid>
      <dc:creator>Ruben Cardenal</dc:creator>
      <dc:date>2002-02-06T13:12:31Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659586#M47898</link>
      <description>Is grecopr2 your localhost? What does /etc/hosts have for localhost?&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Wed, 06 Feb 2002 13:14:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659586#M47898</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-02-06T13:14:30Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659587#M47899</link>
      <description>root@grecopr2:/# nslookup grecopr2&lt;BR /&gt;Using /etc/hosts on:  grecopr2&lt;BR /&gt;&lt;BR /&gt;looking up FILES&lt;BR /&gt;Name:    grecopr2&lt;BR /&gt;Address:  10.15.7.22&lt;BR /&gt;Aliases:  grecopr2.&lt;BR /&gt;&lt;BR /&gt;root@grecopr2:/# nslookup 10.5.7.22&lt;BR /&gt;Using /etc/hosts on:  grecopr2&lt;BR /&gt;&lt;BR /&gt;looking up FILES&lt;BR /&gt;*** No hostname information is available for "10.5.7.22"&lt;BR /&gt;root@grecopr2:/#&lt;BR /&gt;&lt;BR /&gt;Yes, grecopr2 is the name of the machine.&lt;BR /&gt;&lt;BR /&gt;The content of /etc/hosts is:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;10.15.7.22      grecopr2 grecopr2.&lt;BR /&gt;10.15.7.23      grecods                 &lt;BR /&gt;10.15.7.21      grecopr1                  &lt;BR /&gt;10.15.7.27      tareadb                 &lt;BR /&gt;10.15.7.25      tareaap1                  &lt;BR /&gt;10.15.7.26      tareaap2                  &lt;BR /&gt;10.15.7.24      tareads                 &lt;BR /&gt;10.15.7.28      pkgsap&lt;BR /&gt;10.15.7.29      grecopkg&lt;BR /&gt;135.10.0.6      greco01&lt;BR /&gt;127.0.0.1       localhost       loopback localhost.grecopr2.grecopr2&lt;BR /&gt;10.15.6.1       sapdesa&lt;BR /&gt;135.10.0.2 EH02&lt;BR /&gt;&lt;BR /&gt;But I insist: qmail doesn't use /etc/hosts for dns query</description>
      <pubDate>Wed, 06 Feb 2002 13:20:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659587#M47899</guid>
      <dc:creator>Ruben Cardenal</dc:creator>
      <dc:date>2002-02-06T13:20:25Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659588#M47900</link>
      <description>Not sure if this will apply..but what the hey...&lt;BR /&gt;&lt;BR /&gt;I had a problem here with mail. Our DNS server is outside our lan, the relay is an NT server using GroupWise,so we could mail from our UNIX boxes through GroupWise ok.., but for mail to stay here (to me@here.com or co-worker@here.com) it couldn't resolve because once it went out the door, the State's DNS server didn't resolve 'me@here.com'.  So I needed a way to send mail in &amp;amp; out...and also send mail within our lan.  Confused yet.  In other words I needed a way to stop at the door before the mail hit the DNS server and look back inside before resolving out of house...See what I mean...&lt;BR /&gt;What we did was to resolve my problem within our PIX firewall using an Alias command to resolve the IP:&lt;BR /&gt;ALIAS 'private host ip#' 'public host ip#' 255.255.255.255&lt;BR /&gt;&lt;BR /&gt;where:&lt;BR /&gt;      'private host ip#' = The private ip address configured on the&lt;BR /&gt;mail server. = XXX.XXX.XXX.XXX&lt;BR /&gt;&lt;BR /&gt;      'public host ip#'  = The public ip address as configured in the&lt;BR /&gt;                           DNS for the mail server. = &lt;MAIL.SERVER.IP&gt;&lt;BR /&gt;&lt;BR /&gt;       255.255.255.255   = Full mask specifying a single host. = as is.&lt;BR /&gt;====&lt;BR /&gt;Be sure to issue a 'CLEAR XLATE' command on the PIX after adding the&lt;BR /&gt;ALIAS command... otherwise it won't take effect.&lt;BR /&gt;==========================&lt;BR /&gt;I can't take credit for the above resolution (and it worked)..a great network person &amp;amp; I worked on this to get it resolved.&lt;BR /&gt;&lt;BR /&gt;Don't know if this will help, but it's a thought...&lt;BR /&gt;Rgrds,&lt;BR /&gt;Rita&lt;BR /&gt;&lt;BR /&gt;&lt;/MAIL.SERVER.IP&gt;</description>
      <pubDate>Wed, 06 Feb 2002 13:52:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659588#M47900</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2002-02-06T13:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: dns resolving timeouts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659589#M47901</link>
      <description>Good morning,&lt;BR /&gt;&lt;BR /&gt;Rita, yes, that's a solution... if there were a firewall and a dns server here. What I'd need is a way of having the only IP/Hostname of this machine being resolved without installing a DNS server here :(</description>
      <pubDate>Thu, 07 Feb 2002 07:53:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-resolving-timeouts/m-p/2659589#M47901</guid>
      <dc:creator>Ruben Cardenal</dc:creator>
      <dc:date>2002-02-07T07:53:19Z</dc:date>
    </item>
  </channel>
</rss>

