Arkadaşlar intodns.com dan sitemi sorgulattıgımda şu hatayı alıyorum bilenler var ise hata nedendir? CategoryStatusTest nameInformationsend feedback Parent Domain NS records Nameserver records returned by the parent servers are:ns1. arealistikmanken.com. ns2. arealistikmanken.com. b. gtld-servers. net was kind enough to give us that information. TLD Parent Check Good. b. gtld-servers. 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 b. gtld-servers. 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 Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3) 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:web2. hsmservers.com.tr web1. hsmservers.com.tr Recursive Queries Good. Your nameservers do not report that they allow recursive queries for anyone. Same Glue The A records got from the parent zone check are the same as 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 according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below! Glue for NS records INFO: GLUE was not sent when I asked your nameservers for your NS records. This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are: 46.4.23.249You can fix this for example by adding A records to your nameservers for the zones listed above. Mismatched NS records OK. The NS records at all your nameservers are identical. DNS servers responded Good. All nameservers listed at the parent server responded. 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 FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working. If they are not working ok, you may have problems! web1. hsmservers.com.trweb2. hsmservers.com.tr Missing nameservers reported by your nameservers 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: This is listed as an ERROR because there are some cases where nasty problems can occur . Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS record is present. NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS record is present. Different subnets WARNING: Not all of your nameservers are in 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 WARNING: Single point of failure Stealth NS records sent Stealth NS records were sent: web1. hsmservers.com.trweb2. hsmservers.com.tr SOA SOA record The SOA record is:Primary nameserver: web1. hsmservers.com.trHostmaster E-mail address:Serial #: 2011021702 Refresh: 86400 Retry: 7200 Expire: 3600000 5 weeksDefault TTL: 86400 NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2011021702. SOA MNAME entry WARNING: SOA MNAME (web1. hsmservers.com.tr) is not listed as a primary nameserver at your parent nameserver! SOA Serial Your SOA serial number is: 2011021702. This appears to be in the recommended format of YYYYMMDDnn. SOA REFRESH OK. Your SOA REFRESH interval is: 86400. That is OK SOA RETRY Your SOA RETRY value is: 7200. Looks ok SOA EXPIRE Your SOA EXPIRE number is: 3600000. That is NOT 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 . 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 apenisbuyuten.com 46.4.23.249 Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any 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 for your MX records. This is a good thing. Reverse MX A records Your reverse record:249.23.4.46. in-addr. arpa -> static.249.23.4.46. clients. your-server. deYou have reverse records for all your IPs, that is a good thing. WWW WWW A Record Your www.apenisbuyuten.com A record is:www.apenisbuyuten.com -> apenisbuyuten.com -> 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.apenisbuyuten.com. Your CNAME entry also returns the A record for the CNAME entry, which is good. Ağırdır sevmelerim her yürek taşıyamaz, büyüktür umutlarım her omuz kaldıramaz

hocam; Domain NS records ile NS records from your nameservers taki domainler aynı olması gerekiyor, ufak bir problem var, domain panelinden alt name server oluşturup, panelden de bu name serverları girmen gerekiyor, bunları yaptın mı?

Yaptım şimdi düzeldi. Çok sağol dostum Ağırdır sevmelerim her yürek taşıyamaz, büyüktür umutlarım her omuz kaldıramaz