<?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 MX record in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859030#M84284</link>
    <description>I'll vote for using online Internet tools for verifying public services (DNS, mail, etc.) instead of local tests because there are many configuration errors that you cannot detect using local tools - like slave DNS server out of sync, mail open relays, routing problems, etc.</description>
    <pubDate>Sun, 10 Sep 2006 03:36:23 GMT</pubDate>
    <dc:creator>Vitaly Karasik_1</dc:creator>
    <dc:date>2006-09-10T03:36:23Z</dc:date>
    <item>
      <title>DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859022#M84276</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;I have a public domain and would like to create the correct MX record on my DNS server BIND 9&lt;BR /&gt;&lt;BR /&gt;the MAIL server should run on the same machine like DNS server.&lt;BR /&gt;&lt;BR /&gt;my MX record:&lt;BR /&gt;&lt;BR /&gt;# cat /etc/bind/domain.net.hosts&lt;BR /&gt;$ttl 38400&lt;BR /&gt;domain.net.   IN      SOA     ns.domain.net. admin.domain.net. (&lt;BR /&gt;                        2006090525&lt;BR /&gt;                        10800&lt;BR /&gt;                        3600&lt;BR /&gt;                        604800&lt;BR /&gt;                        38400 )&lt;BR /&gt;                IN      NS      ns.domain.net.&lt;BR /&gt;                IN      NS      ns1.isp.net.&lt;BR /&gt;                IN      NS      ns3.isp.net.&lt;BR /&gt;                IN      A       202.X.X.10&lt;BR /&gt;ns             IN      A       202.X.X.10&lt;BR /&gt;www             IN      A       202.X.X.10&lt;BR /&gt;                IN      MX    1 202.X.XX.10&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;but if I do a DNS test at:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.dnsreport.com" target="_blank"&gt;http://www.dnsreport.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I get the following error:&lt;BR /&gt;&lt;BR /&gt;MX Category ERROR: I couldn't find any MX records for domain.net. If you want to receive E-mail on this domain, you should have MX record(s). Without any MX records, mailservers should attempt to deliver mail to the A record for domain.net. I can't continue in a case like this, so I'm assuming you don't receive mail on this domain.&lt;BR /&gt;&lt;BR /&gt;what's wrong and howto solve this problem ?&lt;BR /&gt;</description>
      <pubDate>Thu, 07 Sep 2006 20:14:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859022#M84276</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2006-09-07T20:14:28Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859023#M84277</link>
      <description>Hello,&lt;BR /&gt;   At first glance, the format of the file that you posted looks like a secondary (slave) file for a domain.  Are you sure you're modifying the file on the primary (master) server for that domain?  Also, make sure you're reloading the zone after incrementing the serial number in the master file.  You can do an rndc reload domain.net    or restart your named.</description>
      <pubDate>Thu, 07 Sep 2006 21:05:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859023#M84277</guid>
      <dc:creator>ryan_gray</dc:creator>
      <dc:date>2006-09-07T21:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859024#M84278</link>
      <description>Your last line is responsible for DNS.&lt;BR /&gt;Since you ommit the first parameter that stands for domain/host, it's copied from a previous one (www in your case).&lt;BR /&gt;Add the name of your domain in the beginning of the last line, so it'll look like the following:&lt;BR /&gt;&lt;BR /&gt;domain.net.  IN MX 1 202.X.XX.10</description>
      <pubDate>Fri, 08 Sep 2006 03:02:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859024#M84278</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2006-09-08T03:02:35Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859025#M84279</link>
      <description>I will suggest the change of the location of the MX records. Theorically, the order should not matter, but in my experience it does. Configure your zone file like this:&lt;BR /&gt;&lt;BR /&gt;# cat /etc/bind/domain.net.hosts&lt;BR /&gt;$ttl 38400&lt;BR /&gt;domain.net. IN SOA ns.domain.net. admin.domain.net. (&lt;BR /&gt;2006090525&lt;BR /&gt;10800&lt;BR /&gt;3600&lt;BR /&gt;604800&lt;BR /&gt;38400 )&lt;BR /&gt;IN NS ns.domain.net.&lt;BR /&gt;IN NS ns1.isp.net.&lt;BR /&gt;IN NS ns3.isp.net.&lt;BR /&gt;IN MX 1 202.X.XX.10&lt;BR /&gt;IN A 202.X.X.10&lt;BR /&gt;ns IN A 202.X.X.10&lt;BR /&gt;www IN A 202.X.X.10&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;That is, move your MX record below NS records. You don't need dnsreport.com to test it, just use:&lt;BR /&gt;&lt;BR /&gt;dig @localhost ns.domain.net MX&lt;BR /&gt;&lt;BR /&gt;You should get the MX address in the ANSWER SECTION.</description>
      <pubDate>Fri, 08 Sep 2006 08:28:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859025#M84279</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-09-08T08:28:22Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859026#M84280</link>
      <description>@ryan_gray&lt;BR /&gt;&lt;BR /&gt;yep, &lt;BR /&gt;this is master zone file and I'm 100% sure.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Sep 2006 11:33:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859026#M84280</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2006-09-08T11:33:03Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859027#M84281</link>
      <description>I changed to:&lt;BR /&gt;&lt;BR /&gt;mail            IN A 202.X.X.10&lt;BR /&gt;domain.net.     IN      MX    1 mail.domain.net.&lt;BR /&gt;&lt;BR /&gt;and if I do a test now, then I'm getting:&lt;BR /&gt;&lt;BR /&gt;SPF record &lt;BR /&gt;Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).&lt;BR /&gt; &lt;BR /&gt;howto create SPF record ?</description>
      <pubDate>Fri, 08 Sep 2006 11:49:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859027#M84281</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2006-09-08T11:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859028#M84282</link>
      <description>link with examples followed by explanations:&lt;BR /&gt;&lt;A href="http://www.openspf.org/dns.html" target="_blank"&gt;http://www.openspf.org/dns.html&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Sep 2006 12:03:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859028#M84282</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2006-09-08T12:03:11Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859029#M84283</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;named-checkconf  named-checkzone&lt;BR /&gt;&lt;BR /&gt;Don't use dndsreport.com to check your work, use OS utilities. There is a very common delay in data getting to the checksites.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 08 Sep 2006 12:17:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859029#M84283</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-09-08T12:17:21Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859030#M84284</link>
      <description>I'll vote for using online Internet tools for verifying public services (DNS, mail, etc.) instead of local tests because there are many configuration errors that you cannot detect using local tools - like slave DNS server out of sync, mail open relays, routing problems, etc.</description>
      <pubDate>Sun, 10 Sep 2006 03:36:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859030#M84284</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2006-09-10T03:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859031#M84285</link>
      <description>yep, that's true&lt;BR /&gt;&lt;BR /&gt;in my case named-checkzone showed evrytime OK,  but was not OK.&lt;BR /&gt;</description>
      <pubDate>Sun, 10 Sep 2006 13:19:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859031#M84285</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2006-09-10T13:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859032#M84286</link>
      <description>&lt;!--!*#--&gt;Don't know if you have this working yet, but I took what you had and got it working in this form:&lt;BR /&gt;&lt;BR /&gt;$ttl 38400&lt;BR /&gt;$ORIGIN domain.net.&lt;BR /&gt;domain.net.             IN SOA ns.domain.net. admin.domain.net. (&lt;BR /&gt;                        2006090525&lt;BR /&gt;                        10800&lt;BR /&gt;                        3600&lt;BR /&gt;                        604800&lt;BR /&gt;                        38400 )&lt;BR /&gt;            IN      NS      ns.domain.net.&lt;BR /&gt;            IN      NS      ns1.isp.net.&lt;BR /&gt;            IN      NS      ns3.isp.net.&lt;BR /&gt;            IN      MX   1  202.0.0.10&lt;BR /&gt;&lt;BR /&gt;$ORIGIN domain.net.&lt;BR /&gt;            IN      A       202.0.0.10&lt;BR /&gt;ns          IN      A       202.0.0.10&lt;BR /&gt;www         IN      A       202.0.0.10&lt;BR /&gt;&lt;BR /&gt;That first A record is incomplete.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 11 Sep 2006 09:16:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859032#M84286</guid>
      <dc:creator>Al Licause</dc:creator>
      <dc:date>2006-09-11T09:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859033#M84287</link>
      <description>yep, this problem was already solved !&lt;BR /&gt;&lt;BR /&gt;there are my zone entries:&lt;BR /&gt;&lt;BR /&gt;# cat /etc/bind/domain.net.hosts&lt;BR /&gt;$ttl 38400&lt;BR /&gt;domain.net. IN SOA ns.domain.net. admin.domain.net. (&lt;BR /&gt;2006090525&lt;BR /&gt;10800&lt;BR /&gt;3600&lt;BR /&gt;604800&lt;BR /&gt;38400 )&lt;BR /&gt;IN NS ns.domain.net.&lt;BR /&gt;IN NS ns1.isp.net.&lt;BR /&gt;IN NS ns3.isp.net.&lt;BR /&gt;IN A 202.X.X.10&lt;BR /&gt;ns IN A 202.X.X.10&lt;BR /&gt;www IN A 202.X.X.10&lt;BR /&gt;&lt;BR /&gt;mail IN A 202.X.X.10&lt;BR /&gt;IN MX 1 mail.domain.net.&lt;BR /&gt;</description>
      <pubDate>Sat, 23 Sep 2006 20:12:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dns-mx-record/m-p/3859033#M84287</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2006-09-23T20:12:47Z</dc:date>
    </item>
  </channel>
</rss>

