should they also fix the various DNS errors?
DNS info for dreamhost.com
ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:
WARNING: One or more of your DNS servers does not accept TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. The problem servers are:
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mx2.looney.mail.dreamhost.net claims to be host gollum.dreamhost.com [but that host is at 220.127.116.11 (may be cached), not 18.104.22.168].
mx1.looney.mail.dreamhost.net claims to be host legolas.dreamhost.com [but that host is at 22.214.171.124 (may be cached), not 126.96.36.199].
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).