<?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 Problem in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/dns-problem/m-p/3056129#M6304</link>
    <description>This might be due to dns latency.&lt;BR /&gt;&lt;BR /&gt;Believe it or not some ISP's don't keep up with DNS changes, or are very late in doing so.&lt;BR /&gt;&lt;BR /&gt;At the affected customer site, try nslookup or dig and see if there is resolution.&lt;BR /&gt;&lt;BR /&gt;At the customer site if its linux:&lt;BR /&gt;&lt;BR /&gt;sendmail -v -d8 -d38 dng@e-ascender.com&lt;BR /&gt;&lt;BR /&gt;type a line of text&lt;BR /&gt;&lt;ENTER&gt;&lt;BR /&gt;.&lt;BR /&gt;&lt;ENTER&gt;&lt;BR /&gt;&lt;BR /&gt;You should be able to diagnose the problem with that.&lt;BR /&gt;&lt;BR /&gt;SEP&lt;/ENTER&gt;&lt;/ENTER&gt;</description>
    <pubDate>Mon, 25 Aug 2003 17:22:41 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2003-08-25T17:22:41Z</dc:date>
    <item>
      <title>DNS Problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-problem/m-p/3056128#M6303</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;My colleague and I have set up a Linux Redhat 8.0 (that is also our DNS and mail server) 2 weeks ago.  We provide web and email hosting service for some customers.  &lt;BR /&gt;&lt;BR /&gt;Two clients told me that they could not send emails to the email account (dng@e-ascender.com) that is hosted by our email server.&lt;BR /&gt;&lt;BR /&gt;The strange thing is that other clients can successfully send emails to the same email account (dng@e-ascender.com).&lt;BR /&gt;&lt;BR /&gt;Any idea? Pls help.&lt;BR /&gt;&lt;BR /&gt;Error message is as below:&lt;BR /&gt;&lt;BR /&gt;-------------------------------------------&lt;BR /&gt;&lt;BR /&gt;From: "Mail Delivery Subsystem" &lt;MAILER-DAEMON&gt;&lt;BR /&gt;To: &lt;RICKY&gt;&lt;BR /&gt;Sent: Sunday, August 24, 2003 1:38 PM&lt;BR /&gt;Subject: Returned mail: see transcript for details&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The original message was received at Sun, 24 Aug 2003 13:38:27 +0800&lt;BR /&gt;from imsantv21 [127.0.0.1]&lt;BR /&gt;&lt;BR /&gt;----- The following addresses had permanent fatal errors -----&lt;BR /&gt;&lt;DNG&gt;&lt;BR /&gt;&lt;BR /&gt;----- Transcript of session follows -----&lt;BR /&gt;550 5.1.2 &lt;DNG&gt;... Host unknown (Name server:&lt;BR /&gt;es1.e-ascender.com.: host not found)&lt;BR /&gt;&lt;/DNG&gt;&lt;/DNG&gt;&lt;/RICKY&gt;&lt;/MAILER-DAEMON&gt;</description>
      <pubDate>Mon, 25 Aug 2003 16:40:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-problem/m-p/3056128#M6303</guid>
      <dc:creator>Ng King Wang</dc:creator>
      <dc:date>2003-08-25T16:40:11Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-problem/m-p/3056129#M6304</link>
      <description>This might be due to dns latency.&lt;BR /&gt;&lt;BR /&gt;Believe it or not some ISP's don't keep up with DNS changes, or are very late in doing so.&lt;BR /&gt;&lt;BR /&gt;At the affected customer site, try nslookup or dig and see if there is resolution.&lt;BR /&gt;&lt;BR /&gt;At the customer site if its linux:&lt;BR /&gt;&lt;BR /&gt;sendmail -v -d8 -d38 dng@e-ascender.com&lt;BR /&gt;&lt;BR /&gt;type a line of text&lt;BR /&gt;&lt;ENTER&gt;&lt;BR /&gt;.&lt;BR /&gt;&lt;ENTER&gt;&lt;BR /&gt;&lt;BR /&gt;You should be able to diagnose the problem with that.&lt;BR /&gt;&lt;BR /&gt;SEP&lt;/ENTER&gt;&lt;/ENTER&gt;</description>
      <pubDate>Mon, 25 Aug 2003 17:22:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-problem/m-p/3056129#M6304</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-08-25T17:22:41Z</dc:date>
    </item>
  </channel>
</rss>

