On 6/30/06, Jun Salen <[EMAIL PROTECTED]> wrote:
Hi,

I check our domain name using www.dnsreport.com for me
to determine if our domain are ok. This is due to
feedback from from user that some of their incoming
mails are lost. The following are the results that is
maybe a problem for us.

* (Warn) Missing Direct Parent check - WARNING. Your
direct parent zone (com.ph) does not exist . This is
legal but can cause confusion.

You have to resolve this issue with names.ph

* (Warn) Glue at parent nameserver - WARNING. The
parent servers are not providing glue for all your
nameservers.

You have to resolve this issue with names.ph 

* (Fail) Open DNS Servers - ERROR: One or more of your
nameservers reports that it is an open DNS server.

This means that anyone can perform recursive host lookups on your dns servers. If you control this, allow recursion to trusted hosts only like your LAN.
 
* (Warn) All nameservers report identical NS records -
WARNING: Your nameservers report somewhat different
answers for your NS records (varying TTL, for
example).

This means that your dns info is not properly propagated to the slave servers. You should use only one master dns server to avoid confusion and specifically allow only slave servers to get updated records.

* (Fail) Missing nameservers 2 - ERROR: One or more of
the nameservers listed at the parent servers are not
listed as NS records at your nameservers.

This means that the NS fields on your dns records does not match what you have entered on your domain registry.
Verify the DNS servers you placed in your domain registry it should match the ones you placed in your master DNS server.

* (Warn) TCP Allowed - 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.

One of your DNS servers are down or blocks TCP connections. Try checking your firewall or if it(the dns server) is really up.
 

* (Warn) Mail server host name in greeting - 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.

By default your smtp server should display 220 followed by the hostname ... unless for some reason you have disabled it.
 

* (Warn) Acceptance of abuse address - WARNING: One or
more of your mailservers does not accept mail to
[EMAIL PROTECTED].

Just create an "abuse" account to accept complaints. 

* (Warn) SPF record - Your domain does not have an SPF
record.

Use the spf wizard[1] and append the spf  on your dns record.

What can I do to solve this.




If possible, use secondary mx servers especially if your bandwidth is already congested.

Hth.

'Jopoy


[1] http://www.openspf.org/
 

Many thanks,

junji
 

_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

Reply via email to