مشکل در ست شدن dns نمی دونم مشکل از کجاست ؟ directadmin یا nic

من الان این مشکل رو دارم

مشکل اینه که ای پی هایی که سرور من داره اصلا اینی نیست که اینجا نشون میده

ضمنا اسم dns ها رو عوض کردم به خاطر حفظ مسائل امنیتی

الان من مشکل رو کجا باید بررسی کنم و دقیقا مشکل از کجا می تونه باشه ؟

child host و dns ها رو بر روی دامینی که قراره کامل ست کردم

توی دایرکت ادمین هم همینطور در تمامی قسمت ها dns ست شده

در پنل کاربری nic برای دامین مربوطه هم dns ها ست شده

دسترسی به روت سرور دارم

الان مشکل دقیقا چی هست ؟

ممنون از دوستان

Category Status Test name Information send feedback

Parent http://www.intodns.com/static/images/info.gif Domain NS records Nameserver records returned by the parent servers are:

ns2.kidns.website. ['85.158.203.190'] (NO GLUE) [TTL=300]
ns1.kidns.website. ['85.158.203.190'] (NO GLUE) [TTL=300]

d.ns.tk was kind enough to give us that information.

TLD Parent Check Good. d.ns.tk, 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 d.ns.tk 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.

http://www.intodns.com/static/images/info.gif DNS Parent sent Glue The parent nameserver d.ns.tk 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 http://www.intodns.com/static/images/info.gif NS records from your nameservers NS records got from your nameservers listed at the parent NS are:
Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly.

Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.

Same Glue Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers.

Glue for NS records OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors!

http://www.intodns.com/static/images/error.gif Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records.

http://www.intodns.com/static/images/error.gif DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
85.158.203.190

Name of nameservers are valid OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green!

http://www.intodns.com/static/images/error.gif Multiple Nameservers ERROR: Looks like you have less than 2 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.

http://www.intodns.com/static/images/error.gif Missing nameservers reported by your nameservers You should already know that your NS records at your nameservers are missing, so here it is again:

ns2.kidns.website.
ns1.kidns.website.

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 http://www.intodns.com/static/images/error.gif SOA record
No valid SOA record came back!

MX http://www.intodns.com/static/images/error.gif MX Records Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!

WWW http://www.intodns.com/static/images/error.gif WWW A Record ERROR: I could not get any A records for www.kidns.tk!

(I only do a cache request, if you recently added a WWW A record, it might not show up here.)

Category	Status	Test name	Information send feedback
Parent	http://www.intodns.com/static/images/info.gif	Domain NS records	Nameserver records returned by the parent servers are: ns2.kidns.website. ['85.158.203.190'] (NO GLUE) [TTL=300] ns1.kidns.website. ['85.158.203.190'] (NO GLUE) [TTL=300] d.ns.tk was kind enough to give us that information.
	TLD Parent Check	Good. d.ns.tk, 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 d.ns.tk 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.
http://www.intodns.com/static/images/info.gif	DNS Parent sent Glue	The parent nameserver d.ns.tk 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	http://www.intodns.com/static/images/info.gif	NS records from your nameservers	NS records got from your nameservers listed at the parent NS are: Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly.
	Recursive Queries	Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
	Same Glue	Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers.
	Glue for NS records	OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors!
http://www.intodns.com/static/images/error.gif	Mismatched NS records	WARNING: One or more of your nameservers did not return any of your NS records.
http://www.intodns.com/static/images/error.gif	DNS servers responded	ERROR: One or more of your nameservers did not respond: The ones that did not respond are: 85.158.203.190
	Name of nameservers are valid	OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green!
http://www.intodns.com/static/images/error.gif	Multiple Nameservers	ERROR: Looks like you have less than 2 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.
http://www.intodns.com/static/images/error.gif	Missing nameservers reported by your nameservers	You should already know that your NS records at your nameservers are missing, so here it is again: ns2.kidns.website. ns1.kidns.website.
	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	http://www.intodns.com/static/images/error.gif	SOA record	No valid SOA record came back!
MX	http://www.intodns.com/static/images/error.gif	MX Records	Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!
WWW	http://www.intodns.com/static/images/error.gif	WWW A Record	ERROR: I could not get any A records for www.kidns.tk! (I only do a cache request, if you recently added a WWW A record, it might not show up here.)