Просмотрите полный отчет о настройках DNS для своего домена. Этот инструмент разработан, чтобы помочь веб-мастерам и системным администраторам диагностировать связанные с DNS проблемы.
DNSreport - asrmehr.ir.
|How I am searching:
Searching for asrmehr.ir. record at m.root-servers.net [22.214.171.124]: Got referral to c.nic.ir [took 38 ms]
Searching for asrmehr.ir. record at c.nic.ir [126.96.36.199]: Got referral to e.ns.arvancdn.ir [took 30 ms]
Searching for asrmehr.ir. record at e.ns.arvancdn.ir [188.8.131.52]: Reports asrmehr.ir. [took 28 ms]
|Parent nameservers have your nameservers listed
|OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers.
|DNS servers have A records
|OK. All your DNS servers either have A records at the zone parent servers, or do not need them.
|NS records at parent servers
|Your NS records at the parent servers are:
|NS records at your nameservers
|Your NS records at your nameservers are:
|No NS A records at nameservers
|WARNING. Your nameservers do not include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
|Open DNS servers
|OK. Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be open DNS servers).
|All nameservers report identical NS records
|OK. The NS records at all your nameservers are identical.
|All nameservers respond
|OK. All of your nameservers listed at the parent nameservers responded.
|Number of nameservers
|OK. You have 2 nameservers. You must have at least 2 nameservers.
|OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.
|Missing nameservers (reversed)
|OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
|No CNAMEs for domain
|OK. There are no CNAMEs for asrmehr.ir.
|No NSs with CNAMEs
|OK. There are no CNAMEs for your NS records.
|Nameservers on separate class C
|FAILED. You not have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations.
|All NS IPs public
|OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
|OK. All your DNS servers allow 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.
|Your nameservers have the following versions:
|Your SOA record is:
Primary DNS server: e.ns.arvancdn.ir.
Responsible Name: hostmaster.arvancloud.ir.
|NS agreement on SOA Serial
|OK. All your nameservers agree that your SOA serial number is 1700507772.
|SOA MNAME Check
|OK. Your SOA (Start of Authority) record states that your master (primary) name server is: e.ns.arvancdn.ir. That server is listed at the parent servers, which is correct.
|SOA RNAME Check
|OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: email@example.com. (techie note: we have changed the initial '.' to an '@' for display purposes).
|SOA Serial Number
|OK. Your SOA serial number is: 1700507772. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. So this indicates that your DNS was last updated on 17 Apr 1704.
|SOA REFRESH value
|WARNING. Your SOA REFRESH interval is: 86400 seconds. The normal interval is about 1200-43200 seconds (20 minutes to 12 hours). This value determines how often secondary/slave nameservers check with the master for updates.
|SOA RETRY value
|OK. Your SOA RETRY interval is: 7200 seconds. The normal interval is about 120-7200 seconds. The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
|SOA EXPIRE value
|WARNING. Your SOA EXPIRE time: 604800 seconds. The normal interval is about 1209600-2419200 seconds (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.
|SOA MINIMUM TTL value
|OK. Your SOA MINIMUM TTL is: 7200 seconds. The normal interval is about 3600-10800 seconds (1-3 hours). This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
|Your 1 MX records are:
|OK. All of your MX records appear to use valid hostnames, without any invalid characters.
|All MX IPs public
|OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
|MX records are not CNAMEs
|OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
|MX is host name, not IP
|OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
|Multiple MX records
|FAILED. You do not have multiple MX records. This means that if one is down or unreachable, the other(s) will be able to accept mail for you.
|Differing MX-A records
|OK. I did not detect differing IPs for your MX records. This would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records.
|Duplicate MX records
|OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
|Reverse DNS entries for MX records
|FAILED. The IPs of not all of your mail server(s) have correct reverse DNS (PTR) entries. The reverse DNS entries are:
|Connect to mail servers
|FAILED. You were not able to connect to:
|Mail server host name in greeting
|OK. All of your mailservers have their host name in the greeting:
Unable to connect to host mail.asrmehr.ir.
|Sending test mail
Unable to connect to host mail.asrmehr.ir.
|Open relay test
|OK. All of your mailservers appear to be closed to relaying.
|OK. You have an SPF record. This is very good, as it will help prevent spammers from abusing your domain. Your SPF record (I don't check to see if it is well designed!) is:
"v=spf1 ip4:184.108.40.206 ~all"
|Your www.asrmehr.ir. A record is:
www.asrmehr.ir. A 220.127.116.11 [TTL=180]
www.asrmehr.ir. A 18.104.22.168 [TTL=180]
|All WWW IPs public
|OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.
|OK. Your web site (www.asrmehr.ir.) has not a CNAME record.
|Domain A Lookup
|Your asrmehr.ir. A record is:
asrmehr.ir. A 22.214.171.124 [TTL=180]
asrmehr.ir. A 126.96.36.199 [TTL=180]
|Connect to HTTP servers
|OK. You were able to connect to all of your HTTP servers.
www.asrmehr.ir. [188.8.131.52]: HTTP/1.1 301 Moved Permanently Date: Thu, 29 Feb 2024 05:57:59 GMT Content-Type: text/html
www.asrmehr.ir. [184.108.40.206]: HTTP/1.1 301 Moved Permanently Date: Thu, 29 Feb 2024 05:58:00 GMT Content-Type: text/html