از کجا میدونید که Web Server در حال کار هست؟
پاسخ : مشکل خطای The connection was reset
از کجا میدونید که Web Server در حال کار هست؟
پاسخ : مشکل خطای The connection was reset
اگه شما اطلاع بیشتری دارید راهنمایی کنید
تا بفهمم Web Server در حال کار هست
پاسخ : مشکل خطای The connection was reset
Parent Domain NS records Nameserver records returned by the parent servers are:
ns3.dletresib.ir. ['88.150.193.168'] [TTL=1440]
ns4.dletresib.ir. ['88.150.193.168'] [TTL=1440]
a.nic.ir was kind enough to give us that information.TLD Parent Check Good. a.nic.ir, 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 a.nic.ir 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:
ns4.dletresib.ir ['88.150.193.168'] [TTL=3600]
ns3.dletresib.ir ['88.150.193.168'] [TTL=3600]Recursive Queries I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
88.150.193.168Same Glue The A records (the GLUE) 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 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 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 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 a.nic.ir 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 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 Ok. No stealth ns records are sent SOA SOA record The SOA record is:
Primary nameserver: paradise-31f191
Hostmaster E-mail address: hostmaster
Serial #: 8
Refresh: 900
Retry: 600
Expire: 86400 1 days
Default TTL: 3600NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 8. SOA MNAME entry WARNING: SOA MNAME (paradise-31f191) is not listed as a primary nameserver at your parent nameserver! SOA Serial Your SOA serial number is: 8. The recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision.
Your SOA serial appears to be the number of seconds since midnight 01 Jan 1970 when the last DNS change was made. That seems to be 1969/12/31 18:0:8SOA REFRESH WARNING: Your SOA REFRESH interval is: 900. That is not so ok SOA RETRY Your SOA RETRY value is: 600. Looks ok SOA EXPIRE Your SOA EXPIRE number is: 86400. That is NOT OK SOA MINIMUM TTL Your SOA MINIMUM TTL is: 3600. 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 3600 is OK. MX 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 WWW A Record Your www.dletresib.ir A record is:
www.dletresib.ir [88.150.193.168]IPs are public OK. All of your WWW IPs appear to be public IPs. WWW CNAME OK. No CNAME
من توی سایت متوجه این خطا در دامینم شدم
کسی میتونه راه حل این خطا رو بگه.
پاسخ : مشکل خطای The connection was reset
با سلام
لطفا سرویس های سرور را restart نمایید.
در صورت عدم رفع مشکل ما میتوانیم مشکل را برطرف کنیم
09151894104
ضمنا پینگ سایت dletresib.ir بی نتیجه می باشد.
بهترین سرویس های میزبانی را ازما بخواهید.
iran-hosting.ir
پاسخ : مشکل خطای The connection was reset
آقا هرکی بلده توروخدا کمک کنه
این خطا چه جوری حل میشه؟
Recursive Queries I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
88.150.193.168
پاسخ : مشکل خطای The connection was reset
کسی نیست راهنمایی کنه؟
یعنی هیچ کس به این مشکل بر نخورده؟
هرچقدر هزینه این کار بشه میپردازم اگه سایت درست بشه.
پاسخ : مشکل خطای The connection was reset
Web Server:
دوباره تنظیمات IIS رو بررسی کنید بعد تو VPS، مرورگر رو باز کنید و http://127.0.0.1 رو بزنید. اگر این خطا رو دیدید، احتمالاً برنامه سایت مشکل داره.
DNS:
DNS Server شما فقط باید به درخواست IP برای Domainهای که شما در اون تنظیم کردید پاسخ بده. ولی الان بازه برای هر Domainی و این خطر رو ایجاد میکنه که Server شما مورد استفاده برای DNS DDoS Amplification Attack قرار بگیره، به علاوه مشکلات دیگه.
راه حل: How do I disable recursive DNS queries on my Windows Dedicated or Virtual Private Server? | Go Daddy Help | Go Daddy Support
پاسخ : مشکل خطای The connection was reset
من تو مرورگر زدم خطا دادنوشته اصلی توسط hamid.jafary
برا dns هم که شما گفتی من چیزی نفهمیدم
سایتی که دادی خرابه
پاسخ : مشکل خطای The connection was reset
میتونید مشخصات بدید بررسی کنیم؟
پاسخ : مشکل خطای The connection was reset
ما که بیخیال سرور مجازی شدیم
رفتم هاست دانلود خریدم.
ولی اینو فهمیدم که سرور ارزان بی دلیل ارزون نیست.
صحبتم با سرور قبلی ام هست که خودش میدونه نمیخوام اسم بیارم که ضایع بشه!!!! خودش میدونه
من نمی فهمم چرا وقتی کاری بلد نیستی چرا سرور مجازی ارایه میدی و نمیتونی پشتیبانی کنی....
در حال حاضر 1 کاربر در حال مشاهده این موضوع است. (0 کاربران و 1 مهمان ها)
مجوز های ارسال و ویرایش
پاسخ با نقل قول
