Here is my problem.
When I try to change the DNS to ns9.sixserve.com and ns10.sixserve.com I get the following zone-check error:
ZONE : aderage.fr
NS <= : ns9.sixserve.com [209.105.255.163]
NS : ns10.sixserve.com [209.105.255.164]
Testing: illegal symbols in domain name
Testing: dash ('-') at start or beginning of domain name
Testing: double dash in domain name
Testing: one nameserver for the domain
Testing: at least two nameservers for the domain
Testing: identical addresses
Testing: nameserver addresses are likely to be all on the same subnet
Testing: address in a private network (NS=ns9.sixserve.com)
Testing: address shouldn't be part of a bogon prefix (NS=ns9.sixserve.com)
Testing: address in a private network (NS=ns10.sixserve.com)
Testing: address shouldn't be part of a bogon prefix (NS=ns10.sixserve.com)
Testing: ICMP answer (IP=209.105.255.163)
Testing: ICMP answer (IP=209.105.255.164)
Testing: UDP connectivity (IP=209.105.255.164)
Testing: UDP connectivity (IP=209.105.255.163)
Testing: TCP connectivity (IP=209.105.255.163)
Testing: TCP connectivity (IP=209.105.255.164)
Testing: behaviour against AAAA query (IP=209.105.255.163)
Testing: behaviour against AAAA query (IP=209.105.255.164)
Testing: SOA record present (IP=209.105.255.163)
Testing: SOA authoritative answer (IP=209.105.255.163)
Testing: SOA record present (IP=209.105.255.164)
Testing: SOA authoritative answer (IP=209.105.255.164)
Testing: given primary nameserver is primary (IP=209.105.255.163)
Testing: fully qualified master nameserver in SOA (IP=209.105.255.163)
Testing: illegal characters in SOA master nameserver (IP=209.105.255.163)
Testing: misused '@' characters in SOA contact name (IP=209.105.255.163)
Testing: illegal characters in SOA contact name (IP=209.105.255.163)
Testing: serial number of the form YYYYMMDDnn (IP=209.105.255.163)
Testing: SOA 'expire' between 1W and 100W (IP=209.105.255.163)
Testing: SOA 'minimum' between 3M and 1W (IP=209.105.255.163)
Testing: SOA 'refresh' between 1H and 2D (IP=209.105.255.163)
Testing: SOA 'retry' between 15M and 1D (IP=209.105.255.163)
Testing: SOA 'retry' lower than 'refresh' (IP=209.105.255.163)
Testing: SOA 'expire' at least 7 times 'refresh' (IP=209.105.255.163)
Testing: SOA master is not an alias (IP=209.105.255.163)
Testing: given primary nameserver is primary (IP=209.105.255.164)
Testing: fully qualified master nameserver in SOA (IP=209.105.255.164)
Testing: illegal characters in SOA master nameserver (IP=209.105.255.164)
Testing: misused '@' characters in SOA contact name (IP=209.105.255.164)
Testing: illegal characters in SOA contact name (IP=209.105.255.164)
Testing: serial number of the form YYYYMMDDnn (IP=209.105.255.164)
Testing: SOA 'expire' between 1W and 100W (IP=209.105.255.164)
Testing: SOA 'minimum' between 3M and 1W (IP=209.105.255.164)
Testing: SOA 'refresh' between 1H and 2D (IP=209.105.255.164)
Testing: SOA 'retry' between 15M and 1D (IP=209.105.255.164)
Testing: SOA 'retry' lower than 'refresh' (IP=209.105.255.164)
Testing: SOA 'expire' at least 7 times 'refresh' (IP=209.105.255.164)
Testing: SOA master is not an alias (IP=209.105.255.164)
Testing: coherence between SOA and ANY records (IP=209.105.255.164)
Testing: coherence between SOA and ANY records (IP=209.105.255.163)
Testing: coherence of serial number with primary nameserver (IP=209.105.255.164)
Testing: coherence of administrative contact with primary nameserver (IP=209.105.255.164)
Testing: coherence of master with primary nameserver (IP=209.105.255.164)
Testing: coherence of SOA with primary nameserver (IP=209.105.255.164)
Testing: coherence of serial number with primary nameserver (IP=209.105.255.163)
Testing: coherence of administrative contact with primary nameserver (IP=209.105.255.163)
Testing: coherence of master with primary nameserver (IP=209.105.255.163)
Testing: coherence of SOA with primary nameserver (IP=209.105.255.163)
Testing: NS record present (IP=209.105.255.163)
Testing: NS authoritative answer (IP=209.105.255.163)
Testing: NS record present (IP=209.105.255.164)
Testing: correctness of given nameserver list (IP=209.105.255.163)
_______________
,---------------.|
~~~~ | warning || ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
`---------------'
w> IP addresses are likely to be all on the same subnet
| Adv: ZoneCheck
| To avoid losing all connectivity with the authoritative DNS in case
| of network outage it is advised to host the DNS on different networks.
|
| Ref: IETF RFC2182 (Abstract)
| The Domain Name System requires that multiple servers exist for every
| delegated domain (zone). This document discusses the selection of
| secondary servers for DNS zones. Both the physical and topological
| location of each server are material considerations when selecting
| secondary servers. The number of servers appropriate for a zone is also
| discussed, and some general secondary server maintenance issues
| considered.
`----- -- -- - - -
: All the servers are likely to be on the subnet 209.105.255.160/28,
: try moving some of them to another subnet.
`..... .. .. . . .
=> generic
_____________
,-------------.|
~~~~ | fatal || ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
`-------------'
f> The nameserver list doesn't match the given one
: The given nameserver list (ns10.sixserve.com, ns9.sixserve.com) is
: not consistent with the one retrieved from the zone (ns7.sixserve.com,
: ns8.sixserve.com).
`..... .. .. . . .
=> ns9.sixserve.com/209.105.255.163
==> FAILURE (and 1 warning(s))Do you know why I get such an error ?
Best regards,
Gabin

Sign In »
Register Now!
Help
Twitter
Flickr
This topic is locked

Back to top












