منتدى الدعم العربي لمنتديات أحلى منتدى
مرحبا بك في منتدى دعم منتديات AhlaMontada

لتتمكن من الإستمتاع بكافة ما يوفره لك هذا المنتدى من خصائص, يجب عليك أن تسجل الدخول الى حسابك في المنتدى. إن لم يكن لديك حساب بعد, نتشرف بدعوتك لإنشائه.

انشاء منتدى مجاني شبيه بهذا المنتدى

SSLمشكلة

استعرض الموضوع السابق استعرض الموضوع التالي اذهب الى الأسفل

SSLمشكلة

مُساهمة من طرف mhalbaba في الثلاثاء 14 يناير 2014 - 15:39

السلام عليكم و رحمة الله
شكرا لكم على خدمات أحلى منتدى في الحقيقة أنا أستطيع شراء و تجديد SSL CERTIFICATE إلى منتداي و حاولت أن أضع واحدة بإستخدام II7 لأن هذا سيسهل عملي في خدمات أخرى كFACEBOOK APPLICATION API و خدمات أخرى في غوغل و صراحة تطبيق الفيسبوك الخاص بي لن يعمل إلا بهذه الخاصية و ما أريده من شركة أحلى منتدى هو تفعيل خدمة SSL على حساب godaddy الذي تم شراء الدومين منه وأنا سأتكفل بوضع SSL

[th]Category[/th][th]Status[/th][th]Test name[/th][th][/th]
ParentDomain NS recordsNameserver records returned by the parent servers are:

ns1.dnspro.org   ['74.86.194.136'] (NO GLUE)   [TTL=172800]
ns2.dnspro.org   ['174.36.123.110'] (NO GLUE)   [TTL=172800]

m.gtld-servers.net. was kind enough to give us that information.
TLD Parent CheckGood. m.gtld-servers.net., the parent server I interrogated, has information for your TLD.
Your nameservers are listedGood. The parent server m.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 GlueThe parent nameserver m.gtld-servers.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 recordsGood. Every nameserver listed has A records. This is a must if you want to be found.
NSNS records from your nameserversNS records got from your nameservers listed at the parent NS are:

ns1.dnspro.org  ['74.86.194.139']   [TTL=172800]
ns2.dnspro.org  ['75.126.156.14']   [TTL=172800]
Recursive QueriesGood. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Same GlueHmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers
Glue for NS recordsOK. 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 recordsOK. The NS records at all your nameservers are identical.
DNS servers respondedGood. All nameservers listed at the parent server responded.
Name of nameservers are validOK. All of the NS records that your nameservers report seem valid.
Multiple NameserversERROR: Looks like you have 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 lameOK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Missing nameservers reported by parentOK. All NS records are the same at the parent and at your nameservers.
Missing nameservers reported by your nameserversOK. All nameservers returned by the parent server m.gtld-servers.net. are the same as the ones reported by your nameservers.
Domain CNAMEsOK. 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 checkOK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Different subnetsOK. Looks like you have nameservers on different subnets!
IPs of nameservers are publicOk. 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 connectionOK. 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 systemsOK. 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 sentOk. No stealth ns records are sent
SOASOA recordThe SOA record is:
Primary nameserver: ns1.dnspro.org
Hostmaster E-mail address: postmaster.forumotion.com
Serial #: 2014011413
Refresh: 10800
Retry: 3600
Expire: 1209600   14 days
Default TTL: 21600
NSs have same SOA serialOK. All your nameservers agree that your SOA serial number is 2014011413.
SOA MNAME entryOK. ns1.dnspro.org That server is listed at the parent servers. ns1.dnspro.org That server is listed at the parent servers.
SOA SerialYour SOA serial number is: 2014011413. This appears to be in the recommended format of YYYYMMDDnn.
SOA REFRESHOK. Your SOA REFRESH interval is: 10800. That is OK But recomended range is 1200-43200
SOA RETRYYour SOA RETRY value is: 3600. Looks okBut recomended range is 180-900
SOA EXPIREYour SOA EXPIRE number is: 1209600 seconds.Looks ok
SOA MINIMUM TTLYour SOA MINIMUM TTL is: 21600 seconds. 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 21600 seconds is OK.
MXMX RecordsYour MX records that were reported by your nameservers are:

2   mx.fakemx.net    [46.4.167.9]
1   mx.hm-arab.com    [75.126.156.26]

[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 nameserversThe MX records that are not the same at all your nameservers:

ns1.dnspro.org returned the following:
mx.hm-arab.com [173.192.5.218]
mx.fakemx.net [75.126.245.178]

ns2.dnspro.org returned the following:
mx.fakemx.net [173.192.5.218]
mx.hm-arab.com [75.126.245.178]
It is better to have the same MX records at all your nameservers!
MX name validityGood. I did not detect any invalid hostnames for your MX records.
MX IPs are publicOK. All of your MX records appear to use public IPs.
MX CNAME CheckOK. No problems here.
MX A request returns CNAMEOK. No problems here.
MX is not IPOK. All of your MX records are host names.
Number of MX recordsOK. Looks like you have multiple MX records. However some of your MX records are not common at all your nameservers. This seems bad but if you know what are you doing it's ok.
Mismatched MX AOK. I did not detect differing IPs for your MX records. --not doen
Duplicate MX A recordsOK. 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:
9.167.4.46.in-addr.arpa ->  mx.fakemx.net
26.156.126.75.in-addr.arpa ->  mail.illimail.com
You have reverse (PTR) records for all your IPs, that is a good thing.
WWWWWW A RecordYour www.hm-arab.com A record is:
hmarab.forumaroc.net->www.hm-arab.com ->[67.228.47.101 75.126.208.162 75.126.208.163 67.228.47.98 67.228.47.99 67.228.47.100]

[Looks like you have CNAME's]
IPs are publicOK. All of your WWW IPs appear to be public IPs.
WWW CNAMEOK. You do have a CNAME record for www.hm-arab.com.Your CNAME entry also returns the A record for the CNAME entry, which is good.


mhalbaba



ذكر
عدد المساهمات : 11
معدل النشاط : 1082

http://www.hm-arab.com

الرجوع الى أعلى الصفحة اذهب الى الأسفل

رد: SSLمشكلة

مُساهمة من طرف بنوته كول..! في الثلاثاء 14 يناير 2014 - 17:12

هلا اخوي 


ما فهمت وضح اكثر عشان نساعدك

بنوته كول..!
 
 

انثى
عدد المساهمات : 130
معدل النشاط : 1314

http://ahlabnat11.forumarabia.com/

الرجوع الى أعلى الصفحة اذهب الى الأسفل

رد: SSLمشكلة

مُساهمة من طرف mhalbaba في الثلاثاء 14 يناير 2014 - 17:38

موقع GODADDY.COM يتيح لك العديد من الخصائص خاصة الخدمات الأمنية مثلا يمكنني أن أعرف الخدمات المفعلة و الغير مف على دوميني مثلا
Starting Nmap 6.00 ( http://nmap.org ) at 2014-01-14 16:13 CET
Nmap scan report for f13.dnspro.org (67.228.47.100)
Host is up (0.11s latency).
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
25/tcp open smtp
43/tcp filtered whois
53/tcp closed domain
69/tcp filtered tftp
80/tcp open http
110/tcp closed pop3
116/tcp filtered ansanotify
143/tcp closed imap
194/tcp filtered irc
443/tcp closed https
465/tcp filtered smtps
585/tcp filtered unknown
587/tcp filtered submission
3306/tcp filtered mysql
8443/tcp filtered https-alt
10000/tcp filtered snet-sensor-mgmt

Nmap done: 1 IP address (1 host up) scanned in 1.66 seconds

بالأحمر الخدمات غير المفعلة و أنا فقط أطلب تفعيل البورت الخاص ب https لأنه سيتيح لي الإستفادة من خدمات أخرى

mhalbaba



ذكر
عدد المساهمات : 11
معدل النشاط : 1082

http://www.hm-arab.com

الرجوع الى أعلى الصفحة اذهب الى الأسفل

استعرض الموضوع السابق استعرض الموضوع التالي الرجوع الى أعلى الصفحة

- مواضيع مماثلة

 
صلاحيات هذا المنتدى:
لاتستطيع الرد على المواضيع في هذا المنتدى