| Parent |  | Domain NS records | Nameserver records returned by the parent servers are: ns1.rumahweb.com. ['198.199.101.34', '139.162.19.83'](NO GLUE) [TTL=3600]
ns3.rumahweb.net. ['203.175.8.195', '45.32.114.6'](NO GLUE) [TTL=3600]
ns2.rumahweb.com. ['172.232.249.206', '139.162.19.83'](NO GLUE) [TTL=3600]
ns4.rumahweb.net. ['103.253.213.4', '68.183.178.111'](NO GLUE) [TTL=3600] ns4.apnic.net was kind enough to give us that information. |
| TLD Parent Check | Good.ns4.apnic.net, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check. |
| Your nameservers are listed | Good. The parent server ns4.apnic.net has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers. |
| DNS Parent sent Glue | The parent nameserver ns4.apnic.net is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.) |
| Nameservers A records | Good. Every nameserver listed has A records. This is a must if you want to be found. |
| NS | | NS records from your nameservers | NS records got from your nameservers listed at the parent NS are: ns1.rumahweb.com['64.131.65.219'] [TTL=86400]
ns2.rumahweb.com['206.214.211.55'] [TTL=86400]
ns3.rumahweb.net['178.128.207.174', '45.32.114.6'] [TTL=86400]
ns4.rumahweb.net['157.245.115.90', '45.77.245.133'] [TTL=86400] |
| Recursive Queries | Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. |
| Same Glue | Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For ns1.rumahweb.com the parent reported: ['103.253.213.4', '68.183.178.111'] and your nameservers reported: ['64.131.65.219']
For ns2.rumahweb.com the parent reported: ['103.253.213.4', '68.183.178.111'] and your nameservers reported: ['206.214.211.55']
For ns3.rumahweb.net the parent reported: ['103.253.213.4', '68.183.178.111'] and your nameservers reported: ['178.128.207.174', '45.32.114.6']
For ns4.rumahweb.net the parent reported: ['103.253.213.4', '68.183.178.111'] and your nameservers reported: ['157.245.115.90', '45.77.245.133']
|
| Glue for NS records | OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records. |
| Mismatched NS records | OK. The NS records at all your nameservers are identical. |
| DNS servers responded | ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
68.183.178.111 |
| Name of nameservers are valid | OK. All of the NS records that your nameservers report seem valid. |
| Multiple Nameservers | Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me. |
| Nameservers are lame | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. |
| Missing nameservers reported by parent | OK. All NS records are the same at the parent and at your nameservers. |
| Missing nameservers reported by your nameservers | OK. All nameservers returned by the parent server ns4.apnic.net are the same as the ones reported by your nameservers. |
| Domain CNAMEs | OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. |
| NSs CNAME check | OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. |
| Different subnets | OK. Looks like you have nameservers on different subnets! |
| IPs of nameservers are public | Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like |
| DNS servers allow TCP connection | OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default. |
| Different autonomous systems | OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down. |
| Stealth NS records sent | Ok. No stealth ns records are sent |
| SOA | | SOA record | The SOA record is:
Primary nameserver: ns1.rumahweb.com
Hostmaster E-mail address: notroot.rumahweb.co.id
Serial #: 2024072607
Refresh: 3600
Retry: 1800
Expire: 1209600 2 weeks
Default TTL: 86400
|
| NSs have same SOA serial | OK. All your nameservers agree that your SOA serial number is 2024072607. |
| SOA MNAME entry | OK. ns1.rumahweb.com That server is listed at the parent servers. |
| SOA Serial | Your SOA serial number is: 2024072607. This appears to be in the recommended format of YYYYMMDDnn. |
| SOA REFRESH | OK. Your SOA REFRESH interval is: 3600. That is OK |
| SOA RETRY | Your SOA RETRY value is: 1800. Looks ok |
| SOA EXPIRE | Your SOA EXPIRE number is: 1209600.Looks ok |
| SOA MINIMUM TTL | Your SOA MINIMUM TTL is: 86400. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 86400 is OK. |
| MX | | MX Records | Your MX records that were reported by your nameservers are: 0 rumahcintara.id 103.247.8.53 [These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ] |
| Different MX records at nameservers | Good. Looks like all your nameservers have the same set of MX records. This tests to see if there areany MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs |
| MX name validity | Good. I did not detect any invalid hostnames for your MX records. |
| MX IPs are public | OK. All of your MX records appear to use public IPs. |
| MX CNAME Check | OK. No problems here. |
| MX A request returns CNAME | OK. No CNAMEs returned for A records lookups. |
| MX is not IP | OK. All of your MX records are host names. |
| Number of MX records | OK. Looks like you only have one MX record at your nameservers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time. |
| Mismatched MX A | OK. I did not detect differing IPs for your MX records. |
| Duplicate MX A records | OK. I have not found duplicate IP(s) for your MX records. This is a good thing. |
| Reverse MX A records (PTR) | Your reverse (PTR) record:
53.8.247.103.in-addr.arpa-> mamuju.dua.rumahweb.net
You have reverse (PTR) records for all your IPs, that is a good thing. |
| WWW | | WWW A Record | Your www.rumahcintara.id A record is:
www.rumahcintara.id -> rumahcintara.id -> [ 103.247.8.53 ] [Looks like you have CNAME's] |
| IPs are public | OK. All of your WWW IPs appear to be public IPs. |
| WWW CNAME | OK. You do have a CNAME record for www.rumahcintara.id.Your CNAME entry also returns the A record for the CNAME entry, which is good. |
