Author Topic: Problème de DNS  (Read 681 times)

Offline Spinacle

  • Revendeurs
  • Hero Member
  • ******
  • Posts: 993
  • Karma: 28
    • View Profile
    • Aubergedunet
Problème de DNS
« on: Mars 18, 2007, 10:19:48 pm »
Staff,

Ci-dessous les erreurs que j'ai sur les dns de mon domaine revendeur et sur les domaines que j'héberge.
Pourriez-vous faire le nécessaire pour les corriger.
Merci


Quote
FAIL : Open DNS Servers
ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are:

Server 85.17.101.1 reports that it will do recursive lookups. [test] Server 85.17.101.2 reports that it will do recursive lookups. [test] See this page for info on closing open DNS servers.

Quote
FAIL : Mismatched glue
ERROR: Your nameservers report glue that is different from what the parent servers report. This will cause DNS servers to get confused; some may go to the IP provided by the parent servers, while others may get to the ones provided by your authoritative DNS servers. Problem record(s) are:

ns2.aubergedunet.com.:
Parent server (a.gtld-servers.net) says A record is 85.17.101.2, but
authoritative DNS server (85.17.101.1) says it is 75.126.55.120
ns2.aubergedunet.com.:
Parent server (a.gtld-servers.net) says A record is 85.17.101.2, but
authoritative DNS server (85.17.101.2) says it is 75.126.55.120

Quote
WARN : Nameservers on separate class C's
WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C (technically, /24) address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.

Quote
WARN : Single Point of Failure
WARNING: Although you have at least 2 NS records, they may both point to the same server (neither of our two tests is sure; it appears that there are one or more firewall(s) that intercept and alter DNS packets), which would result in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.

Offline staff

  • Tech. EdelweissHosting
  • Administrator
  • Hero Member
  • *****
  • Posts: 6047
  • Karma: 50
    • View Profile
    • EdelweissHosting
Re : Problème de DNS
« Reply #1 on: Mars 19, 2007, 01:11:56 pm »
Bonjour

Envoyez un email avec les codes d'accès à votre VPS et on corrige.

Merci
Membre Staff EdelweissHosting
Site Principal: http://edelweisshosting.com
Votre IP: http://edelweisshosting.com/ip.php

Offline Spinacle

  • Revendeurs
  • Hero Member
  • ******
  • Posts: 993
  • Karma: 28
    • View Profile
    • Aubergedunet
Re : Problème de DNS
« Reply #2 on: Mars 19, 2007, 02:13:06 pm »
Mail envoyé :)

Offline staff

  • Tech. EdelweissHosting
  • Administrator
  • Hero Member
  • *****
  • Posts: 6047
  • Karma: 50
    • View Profile
    • EdelweissHosting
Re : Problème de DNS
« Reply #3 on: Mars 19, 2007, 02:20:51 pm »
C'est corrigé maintenant :)
Membre Staff EdelweissHosting
Site Principal: http://edelweisshosting.com
Votre IP: http://edelweisshosting.com/ip.php