|
Other common DNS setup errors
|
# of zones (N=5000)
|
Percentage
|
|
One or more name servers that were registered as
being authoritative for the zones, but did not
contain authoritative data (lame delegations)
|
1496
|
30%
|
|
Effect: Lame delegations are
very common on the Internet and cause unnecessary
DNS traffic, slow down DNS lookups and may cause
DNS lookup failures.
|
|
Delegation data and zone data do not match
|
1236
|
24.7%
|
|
Effect: Incorrect delegation
can lead to long resolution times, and in some
cases it can cause information within the domain to
be inaccessible.
|
A PTR record is missing for an A (address)
record
|
964
|
19.3%
|
|
Effect: If a PTR record is
missing for a host, a client running on that host
may have problems getting access to some services
on the Internet (FTP for example).
|
|
None of the authoritative name server
answered
|
877
|
17.5%
|
|
Effect: It was not possible to
get information about the zone from any of the
servers that were listed as being authoritative for
the zone which causes lookup failures when name
servers try to look up data for the zone.
|
|
No MX record
|
469
|
9.4%
|
|
Effect: Having no MX records
will cause mail delivery problems.
|
|
MX record refers to a CNAME record instead of an
A record
|
318
|
6.4%
|
|
Effect: This can cause mail
delivery problems.
|
|
One of the mail servers that handle mail for the
zone is not working properly
|
268
|
5.4%
|
|
Effect: A mail server that is not working properly can cause mail delivery problems.
|
|
One or more records in the zone refer to hosts
whose names cannot be resolved
|
255
|
5.1%
|
|
Effect: It is not possible to
access the referred hosts as they probably do not
exist.
|