Accès bloqué à certains sites par Free ?

doumé

24/11/2008 à 22:05

Dans son message précédent, Albert ARIBAUD a écrit :

Ai-je dit que mon explication est celle de la suspension de ce site ?
J'ai expliqué en quoi ce qu'on sait avoir mis sur un site peut différer
de ce qui s'y trouve.

Ben non , comme d'habitude , tu n'expliques rien et surtout pas les
raisons de free de suspendre l'accès à ce site et qui plus est ,
pourquoi free est le seul fai à agir de la sorte ...

--
Je dis de belles choses dit le vieux Sénèque en défilant ...

Albert ARIBAUD

24/11/2008 à 22:10

Le Mon, 24 Nov 2008 22:05:15 +0100, doumé a écrit :

Dans son message précédent, Albert ARIBAUD a écrit :

Ai-je dit que mon explication est celle de la suspension de ce site ?
J'ai expliqué en quoi ce qu'on sait avoir mis sur un site peut différer
de ce qui s'y trouve.

Ben non , comme d'habitude , tu n'expliques rien et surtout pas les
raisons de free de suspendre l'accès à ce site

Et pour cause : il n'est pas démontré qu'il y ait suspension -- tout
juste suspicion, ce qui est suffisamment proche apparemment pour faire un
amalgame. :)

et qui plus est, pourquoi free est le seul fai à agir de la sorte ...

Agir ? En quoi ? Tout ce qu'il y a objectivement, c'est un routeur après
Bordeaux qui fait glouglou.

Amicalement,
--
Albert.

mryeti

25/05/2009 à 21:13

Denis a écrit le 23/11/2008 à 18h53 :

Je dispose d'un petit site hébergé chez Strato
Hébergement.
Ce site est totalement anodin et comporte seulement quelques indications
pour des cours informatiques.

Depuis le 8 novembre ce site n'est plus accessible via Free, alors qu'il est
toujours accessible via Neuf, Orange, Cegetel, et Numéricâble.
Après plusieurs demandes les techniciens Free m'ont parlé de site

"Blacklisté".
Je savais que la Chine bloquait l'accès à certains sites via les

fournisseurs d'accès, mais je ne savais que cela se pratiquait en
France.

Est-ce quelqu'un a déjà rencontré des problèmes
similaires et inexpliqués
pour accéder à un site ?

Merci de vos avis.

Bonjour à tous,
je viens de lire tous les posts, et du coup ce forum vient de me faire bcp de bien car depuis une semaine je me sens seul au monde.

J'ai exactement le même problème je suis hébergé chez Strato, avec 2 noms de domaine, dont un qui fonctionne parfaitement (www.paysagiste-furon.com) et l'autre (www.aej-du-var.com) qui est mort complet pourtant il renvoit vers le serveur strato et vers le même fichier index l'un comme l'autre.
Mais comme vous je suis chez Free et mes amies chez d'autre Fai l'ouvrent sans soucis except Alice qui déconne également

Aprés avoir essayer ces bidouilles:
_Créer différentes redirections vers d'autre si à moi à partir du panneau de config Strato "Marche pas"
_Changer les DNS pour renvoyer vers un autre serveur d'un pot "Marche pas"

J'ai analysé le routage de mon nom de domaine:
_J'ai pingé les IP des serveurs de nom et l'un d'entre eux répond un peu quand il veut
docks17.rzone.de
_ Analyse complete via un site dédié

Voila le résultat:
Status Test name Information send feedback

Domain NS records Nameserver records returned by the parent servers are:

docks17.rzone.de. ['81.169.146.27'] (NO GLUE) [TTL2800]
shades06.rzone.de. ['85.214.0.236'] (NO GLUE) [TTL2800]

c.gtld-servers.net was kind enough to give us that information.
TLD Parent Check Good. c.gtld-servers.net, the parent server I interogated, 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 c.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 The parent nameserver c.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 happends 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 records from your nameservers NS records got from your nameservers listed at the parent NS are:

shades06.rzone.de ['85.214.0.236'] [TTL�400]
docks17.rzone.de ['81.169.146.27'] [TTL�400]
Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Same 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 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:
81.169.146.27
85.214.0.236
You 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 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 c.gtld-servers.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 usefull 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 carefull 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 record The SOA record is:
Primary nameserver: shades06.rzone.de
Hostmaster E-mail address: hostmaster.strato-rz.de
Serial #: 2009052200
Refresh: 86400
Retry: 7200
Expire: 604800 1 weeks
Default TTL: 86400
NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2009052200.
SOA MNAME entry OK. shades06.rzone.de That server is listed at the parent servers.
SOA Serial Your SOA serial number is: 2009052200. 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: 604800.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 recommands a value of 1-3 hours. Your value of 86400 is OK.
MX Records Your MX records that were reported by your nameservers are:

10 mailin.rzone.de 81.169.145.99 81.169.145.102 81.169.145.100 81.169.145.101 (no glue)

[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 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 but that MX record has multiple IPs. You should be carefull about what you are doing but overall it's ok.
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:
101.145.169.81.in-addr.arpa -> mailin.rzone.de
99.145.169.81.in-addr.arpa -> mailin.rzone.de
100.145.169.81.in-addr.arpa -> mailin.rzone.de
102.145.169.81.in-addr.arpa -> mailin.rzone.de
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW A Record Your www.aej-du-var.com A record is:
www.aej-du-var.com [81.169.145.81]
IPs are public OK. All of your WWW IPs appear to be public IPs.
WWW CNAME OK. No CNAME

Que puis-je faire SVP? Aidez moi? Je suis grave dans la m...

Cordialement

Denis a écrit le 23/11/2008 à 18h53 :

Je dispose d'un petit site hébergé chez Strato
Hébergement.
Ce site est totalement anodin et comporte seulement quelques indications
pour des cours informatiques.

Depuis le 8 novembre ce site n'est plus accessible via Free, alors qu'il est
toujours accessible via Neuf, Orange, Cegetel, et Numéricâble.
Après plusieurs demandes les techniciens Free m'ont parlé de site

"Blacklisté".
Je savais que la Chine bloquait l'accès à certains sites via les

fournisseurs d'accès, mais je ne savais que cela se pratiquait en
France.

Est-ce quelqu'un a déjà rencontré des problèmes
similaires et inexpliqués
pour accéder à un site ?

Merci de vos avis.

Bonjour à tous,
je viens de lire tous les posts, et du coup ce forum vient de me faire bcp de bien car depuis une semaine je me sens seul au monde.

J'ai exactement le même problème je suis hébergé chez Strato, avec 2 noms de domaine, dont un qui fonctionne parfaitement (www.paysagiste-furon.com) et l'autre (www.aej-du-var.com) qui est mort complet pourtant il renvoit vers le serveur strato et vers le même fichier index l'un comme l'autre.
Mais comme vous je suis chez Free et mes amies chez d'autre Fai l'ouvrent sans soucis except Alice qui déconne également

Aprés avoir essayer ces bidouilles:
_Créer différentes redirections vers d'autre si à moi à partir du panneau de config Strato "Marche pas"
_Changer les DNS pour renvoyer vers un autre serveur d'un pot "Marche pas"

J'ai analysé le routage de mon nom de domaine:
_J'ai pingé les IP des serveurs de nom et l'un d'entre eux répond un peu quand il veut
docks17.rzone.de
_ Analyse complete via un site dédié

Voila le résultat:
Status Test name Information send feedback

Domain NS records Nameserver records returned by the parent servers are:

docks17.rzone.de. ['81.169.146.27'] (NO GLUE) [TTL=172800]
shades06.rzone.de. ['85.214.0.236'] (NO GLUE) [TTL=172800]

c.gtld-servers.net was kind enough to give us that information.
TLD Parent Check Good. c.gtld-servers.net, the parent server I interogated, 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 c.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 The parent nameserver c.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 happends 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 records from your nameservers NS records got from your nameservers listed at the parent NS are:

shades06.rzone.de ['85.214.0.236'] [TTL=86400]
docks17.rzone.de ['81.169.146.27'] [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 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 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:
81.169.146.27
85.214.0.236
You 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 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 c.gtld-servers.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 usefull 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 carefull 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 record The SOA record is:
Primary nameserver: shades06.rzone.de
Hostmaster E-mail address: hostmaster.strato-rz.de
Serial #: 2009052200
Refresh: 86400
Retry: 7200
Expire: 604800 1 weeks
Default TTL: 86400
NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2009052200.
SOA MNAME entry OK. shades06.rzone.de That server is listed at the parent servers.
SOA Serial Your SOA serial number is: 2009052200. 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: 604800.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 recommands a value of 1-3 hours. Your value of 86400 is OK.
MX Records Your MX records that were reported by your nameservers are:

10 mailin.rzone.de 81.169.145.99 81.169.145.102 81.169.145.100 81.169.145.101 (no glue)

[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 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 but that MX record has multiple IPs. You should be carefull about what you are doing but overall it's ok.
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:
101.145.169.81.in-addr.arpa -> mailin.rzone.de
99.145.169.81.in-addr.arpa -> mailin.rzone.de
100.145.169.81.in-addr.arpa -> mailin.rzone.de
102.145.169.81.in-addr.arpa -> mailin.rzone.de
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW A Record Your www.aej-du-var.com A record is:
www.aej-du-var.com [81.169.145.81]
IPs are public OK. All of your WWW IPs appear to be public IPs.
WWW CNAME OK. No CNAME

Que puis-je faire SVP? Aidez moi? Je suis grave dans la m...

Cordialement

Vous avez filtré cet utilisateur ! Consultez son message

Denis a écrit le 23/11/2008 à 18h53 :

Je dispose d'un petit site hébergé chez Strato
Hébergement.
Ce site est totalement anodin et comporte seulement quelques indications
pour des cours informatiques.

Depuis le 8 novembre ce site n'est plus accessible via Free, alors qu'il est
toujours accessible via Neuf, Orange, Cegetel, et Numéricâble.
Après plusieurs demandes les techniciens Free m'ont parlé de site

"Blacklisté".
Je savais que la Chine bloquait l'accès à certains sites via les

fournisseurs d'accès, mais je ne savais que cela se pratiquait en
France.

Est-ce quelqu'un a déjà rencontré des problèmes
similaires et inexpliqués
pour accéder à un site ?

Merci de vos avis.

Bonjour à tous,
je viens de lire tous les posts, et du coup ce forum vient de me faire bcp de bien car depuis une semaine je me sens seul au monde.

J'ai exactement le même problème je suis hébergé chez Strato, avec 2 noms de domaine, dont un qui fonctionne parfaitement (www.paysagiste-furon.com) et l'autre (www.aej-du-var.com) qui est mort complet pourtant il renvoit vers le serveur strato et vers le même fichier index l'un comme l'autre.
Mais comme vous je suis chez Free et mes amies chez d'autre Fai l'ouvrent sans soucis except Alice qui déconne également

Aprés avoir essayer ces bidouilles:
_Créer différentes redirections vers d'autre si à moi à partir du panneau de config Strato "Marche pas"
_Changer les DNS pour renvoyer vers un autre serveur d'un pot "Marche pas"

J'ai analysé le routage de mon nom de domaine:
_J'ai pingé les IP des serveurs de nom et l'un d'entre eux répond un peu quand il veut
docks17.rzone.de
_ Analyse complete via un site dédié

Voila le résultat:
Status Test name Information send feedback

Domain NS records Nameserver records returned by the parent servers are:

docks17.rzone.de. ['81.169.146.27'] (NO GLUE) [TTL2800]
shades06.rzone.de. ['85.214.0.236'] (NO GLUE) [TTL2800]

c.gtld-servers.net was kind enough to give us that information.
TLD Parent Check Good. c.gtld-servers.net, the parent server I interogated, 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 c.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 The parent nameserver c.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 happends 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 records from your nameservers NS records got from your nameservers listed at the parent NS are:

shades06.rzone.de ['85.214.0.236'] [TTL�400]
docks17.rzone.de ['81.169.146.27'] [TTL�400]
Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Same 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 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:
81.169.146.27
85.214.0.236
You 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 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 c.gtld-servers.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 usefull 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 carefull 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 record The SOA record is:
Primary nameserver: shades06.rzone.de
Hostmaster E-mail address: hostmaster.strato-rz.de
Serial #: 2009052200
Refresh: 86400
Retry: 7200
Expire: 604800 1 weeks
Default TTL: 86400
NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2009052200.
SOA MNAME entry OK. shades06.rzone.de That server is listed at the parent servers.
SOA Serial Your SOA serial number is: 2009052200. 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: 604800.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 recommands a value of 1-3 hours. Your value of 86400 is OK.
MX Records Your MX records that were reported by your nameservers are:

10 mailin.rzone.de 81.169.145.99 81.169.145.102 81.169.145.100 81.169.145.101 (no glue)

[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 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 but that MX record has multiple IPs. You should be carefull about what you are doing but overall it's ok.
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:
101.145.169.81.in-addr.arpa -> mailin.rzone.de
99.145.169.81.in-addr.arpa -> mailin.rzone.de
100.145.169.81.in-addr.arpa -> mailin.rzone.de
102.145.169.81.in-addr.arpa -> mailin.rzone.de
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW A Record Your www.aej-du-var.com A record is:
www.aej-du-var.com [81.169.145.81]
IPs are public OK. All of your WWW IPs appear to be public IPs.
WWW CNAME OK. No CNAME

Que puis-je faire SVP? Aidez moi? Je suis grave dans la m...

Cordialement

doumé

25/05/2009 à 22:29

mryeti a présenté l'énoncé suivant :

Bonjour à tous,
je viens de lire tous les posts, et du coup ce forum vient de me faire bcp de
bien car depuis une semaine je me sens seul au monde.

J'ai exactement le même problème je suis hébergé chez Strato, avec 2 noms de
domaine, dont un qui fonctionne parfaitement (www.paysagiste-furon.com) et
l'autre (www.aej-du-var.com) qui est mort complet pourtant il renvoit vers le
serveur strato et vers le même fichier index l'un comme l'autre.
Mais comme vous je suis chez Free et mes amies chez d'autre Fai l'ouvrent
sans soucis except Alice qui déconne également

Aprés avoir essayer ces bidouilles:
_Créer différentes redirections vers d'autre si à moi à partir du panneau de
config Strato "Marche pas"
_Changer les DNS pour renvoyer vers un autre serveur d'un pot "Marche pas"

Que puis-je faire SVP? Aidez moi? Je suis grave dans la m...

Cordialement

Je suis chez orange et j'ouvre ton site sans soucis .Il est super !
Peut être qu'en changeant de fournisseur d'accès qui n'impose pas de
restriction ?

--
Je dis de belles choses dit le vieux Sénèque en défilant ...

Dominique ROUSSEAU

26/05/2009 à 18:28

Le lun, 25 mai 2009 at 19:13 GMT, mryeti a écrit :

J'ai exactement le même problème je suis hébergé chez Strato, avec 2 noms de
domaine, dont un qui fonctionne parfaitement (www.paysagiste-furon.com) et
l'autre (www.aej-du-var.com) qui est mort complet pourtant il renvoit vers le
serveur strato et vers le même fichier index l'un comme l'autre.

Ca n'arrive pas du tout sur la meme ip :

$ dig +short www.paysagiste-furon.com
81.169.145.90
$ dig +short www.aej-du-var.com
81.56.133.93

Floris

27/05/2009 à 19:57

Dominique ROUSSEAU a écrit :

Le lun, 25 mai 2009 at 19:13 GMT, mryeti a écrit :
J'ai exactement le même problème je suis hébergé chez Strato, avec 2 noms de
domaine, dont un qui fonctionne parfaitement (www.paysagiste-furon.com) et
l'autre (www.aej-du-var.com) qui est mort complet pourtant il renvoit vers le
serveur strato et vers le même fichier index l'un comme l'autre.

Ca n'arrive pas du tout sur la meme ip :

$ dig +short www.paysagiste-furon.com
81.169.145.90
$ dig +short www.aej-du-var.com
81.56.133.93

Z'ont des pbs dns chez free "en ce moment".

Ya plusieurs msg sur les newsgroups proxad, apparemment complètement
ignorés du support.

Ya un mec qui les a joins par plusieurs méthodes, il s'est fait refouler
dans tout les cas "le problème vient de votre pc".
On a pourtant clairement établi "la source du problème".

--
Floris Dubreuil

doumé

27/05/2009 à 20:49

Floris a présenté l'énoncé suivant :

Z'ont des pbs dns chez free "en ce moment".

Oh ?!?

Ya plusieurs msg sur les newsgroups proxad, apparemment complètement ignorés
du support.

Tu me surprends beaucoup , là ... Le support de free ignorent les
problèmes des clients ?

Ya un mec qui les a joins par plusieurs méthodes, il s'est fait refouler dans
tout les cas "le problème vient de votre pc".
On a pourtant clairement établi "la source du problème".

Free fait preuve de mauvaise foi ? Tu me surpreds beaucoup , là ...

Finalement , après 3 ans , RIEN n'a changé chez free . Content de ne
plus en être !!!

--
Je dis de belles choses dit le vieux Sénèque en défilant ...

mryeti

28/05/2009 à 07:58

Denis a écrit le 23/11/2008 à 18h53 :

Je dispose d'un petit site hébergé chez Strato
Hébergement.
Ce site est totalement anodin et comporte seulement quelques indications
pour des cours informatiques.

Depuis le 8 novembre ce site n'est plus accessible via Free, alors qu'il est
toujours accessible via Neuf, Orange, Cegetel, et Numéricâble.
Après plusieurs demandes les techniciens Free m'ont parlé de site

"Blacklisté".
Je savais que la Chine bloquait l'accès à certains sites via les

fournisseurs d'accès, mais je ne savais que cela se pratiquait en
France.

Est-ce quelqu'un a déjà rencontré des problèmes
similaires et inexpliqués
pour accéder à un site ?

Merci de vos avis.

Merci pour ton Post Doumé, ça me fait plaisir!!!

Bon toujours pareil impossible d'ouvrir le site même en essayant tout plein de choses, sytle transformer mon pc en serveur avec IP fixe et renvoyer le site vers mon serveur résultat identique, pourtant mon serveur marche trés bien enfin quand ma pc est allumé d'ou le fait que Dominique Rousseau du post précédent à vu que les IP étaient différentes et ne répondaient pas.

J'ai remis comme cela devait être renvois vers le serveur ftp de STrato:

Réponse au ping Ping 81.169.145.81
[www.aej-du-var.com]

Round trip time to 81.169.145.81: 153 ms
Round trip time to 81.169.145.81: 142 ms
Round trip time to 81.169.145.81: 140 ms
Round trip time to 81.169.145.81: 138 ms
Round trip time to 81.169.145.81: 158 ms
Round trip time to 81.169.145.81: 179 ms
Round trip time to 81.169.145.81: 150 ms
Round trip time to 81.169.145.81: 134 ms
Round trip time to 81.169.145.81: 144 ms
Round trip time to 81.169.145.81: 144 ms

Helppppp!!!!!!!!!

Average time over 10 pings: 148.2 ms

Accès bloqué à certains sites par Free ?

8 réponses

Veuillez sélectionner un problème