http://www.dnsreport.com/tools/dnsre...in=desilva.biz
Ouch!

------------WARN---------Missing (stealth) nameservers-------------
WARNING: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly.
ns1.cpanel.dxon.net.
ns2.cpanel.dxon.net.

------------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. The problem NS records are:
NS2.desilva.biz.
NS1.desilva.biz.

------------WARN---------Nameservers on separate class C's-----------
WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location. [If the parent servers have no glue for your domain, this could be a false positive.]

------------WARN---------SOA MNAME Check-----------------------------
WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: 199.236.4.60.. However, that server is not listed at the parent servers as one of your NS records! This is probably legal, but you should be sure that you know what you are doing.

------------WARN---------SOA REFRESH value-----------------------------
WARNING: Your SOA REFRESH interval is : 28800 seconds. This seems a bit high. You should consider decreasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours; 12 hours seems very high to us), although some registrars may limit you to 10000 seconds or higher, and if you are using DNS NOTIFY the refresh value is not as important (RIPE recommend 86400 seconds if using DNS NOTIFY). This value determines how often secondary/slave nameservers check with the master for updates. A value that is too high will cause DNS changes to be in limbo for a long time.

------------WARN---------SOA Expire value-----------------------------
WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.

------------WARN---------Multiple MX records-----------------------------
WARNING: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you.

------------WARN---------Mail server host name in greeting--------------
WARNING: One or more of your mailservers claims 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). This probably won't cause any harm, but is a technical violation of RFC821 4.3.

desilva.biz claims to be host cp01.cpanel.dxon.net.

------------WARN---------Acceptance of domain literals-----------------------
WARN: One or more of your mailservers does not accept mail in the domain literal format (user@[0.0.0.0]). Mailservers are technically required RFC1123 5.2.17 to accept mail to domain literals for any of its IP addresses. Not accepting domain literals can make it more difficult to test your mailserver, and can prevent you from receiving E-mail from people reporting problems with your mailserver. However, it is unlikely that any problems will occur if the domain literals are not accepted.

desilva.biz's postmaster@[199.236.4.62] response:
>>> RCPT TO: <postmaster@[199.236.4.62]>
<<< 501 : domain literals not allowed

Also, I thought Dedicated Servers did not show that you are using their servers. Because they are designed to make it look like you are the person who has the server. But I found your server is from http://www.dxon.net/hosting/vds

Thought you might want to know, I ran a check on my site, and sent an e-mail to my host regarding the WARNING and FAIL messages I got. I think I had like 8 WARN and 2 FAIL.

Anyways, check it out.

Isn't DNSReport wonderful?

I am aware of the FAILED report, it is something I created myself and certainly not the fault of my web host.

If you need some background info into the issue and why I did this, click through to this page: http://www.gidforums.com/t-671.html

__________________
J de Silva
Learning Journal | GIDForums™ | GIDNetwork™ | GIDWebhosts™ | GIDSearch™