Data Loader

DNS Check Results for Domain: abarbanell.de

DNS Check for domain abarbanell.de
Print DNS Check Results for Domain: abarbanell.de
Section Status Lookup Test Name DNS Query Results
WWW
Info
WWW A Record
A Record / Server IP-Address for Domain www.abarbanell.de is: [ 81.169.145.164 ]
Pass
IP Addresses are public
All of your WWW IP Addresses appear to be public IPs.
Pass
Hostname FQDN
Server Hostname FQDN is: wa4.rzone.de
Parent
Info
Domain NS Records
Name Server Records returned by the parent servers are:
abarbanell.de. 86400 IN NS docks03.rzone.de.
abarbanell.de. 86400 IN NS shades09.rzone.de.

a.nic.de was kind enough to give us that information.
Pass
TLD Parent Check
Good. a.nic.de, the parent server I interrogated, has information for your TLD.
Pass
Name Servers listed
The parent server a.nic.de has your name servers 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 name servers.
Pass
DNS Parent send Glue
The parent nameserver might not sent your name servers as well as the IPs of your name servers. Glue Records are A Records that are associated with NS Records to provide bootstrapping information to the nameserver.
Pass
Nameserver A Records
Every nameserver listed probably has A Records. This is a must if you want to be found.
NS
Info
NS Records from your Name Servers
NS Records got from your nameservers listed at the parent NS are:
shades09.rzone.de  ['85.214.0.239']  [TTL=150]
docks03.rzone.de  ['81.169.146.13']  [TTL=150]
Pass
Mismatched NS Records
The NS Records at all your name servers are identical.
Recursive NS Queries
Recursive NS Queries
Nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Pass
DNS Servers responded
All name servers listed at the parent server responded.
Pass
Name of Nameservers are valid
All of the NS Records that your name servers report seem valid.
Pass
Multiple Name Servers
Domain abarbanell.de have multiple name servers. You must have at least 3 name servers, and no more than 7. Having 2 name servers is also ok.
Domain CNAMEs
Domain CNAMEs
RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
NS CNAME Checks
NS CNAME Checks
RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Nameservers are lame
Nameservers are lame
All nameserver listed at the parent servers answer authoritatively for your domain.
Missing Nameservers
Missing name servers reported by parent
All NS Records are the same at the parent and at your name servers.
Missing Nameservers
Missing Nameservers reported by your Nameservers
All nameservers returned by the parent server f.gtld-servers.net are the same as the ones reported by your nameservers.
Nameservers public
IPs of Nameservers are public
Looks like the IP addresses of your name servers are public. This is a good thing because it will prevent DNS delays and other problems.
Same Glue Lookup
Same Glue
The A Records (Same 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!
Same Glue NS Records
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:
85.214.0.239
81.169.146.13
You can fix this for example by adding A records to your nameservers for the zones listed above.
Different Subnets
Different Subnets
Looks like you have nameservers on different subnets.
DNS Servers TCP
DNS Servers allow TCP connection
Seems all your DNS Servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
Different Systems
Different autonomous systems
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
Stealth NS Records sent
No stealth NS Records are sent
SOA
SOA Record Info
SOA Record
The SOA record is:
Primary nameserver: shades09.rzone.de
Hostmaster eMail-Address: hostmaster.strato-rz.de
Serial #: 2017110712
Refresh: 86400
Retry: 7200
Expire: 604800
Default TTL: 7200
NSs SOA Serial Info
NSs have same SOA Serial
All nameservers agree that your SOA Serial Number is: 2017110712
SOA MNAME entry
SOA MNAME entry
shades09.rzone.de That server is listed at the parent servers.
SOA Serial No.
SOA Serial No.
SOA Serial Number is: 2017110712. This appears to be in the recommended format of YYYYMMDDnn.
SOA REFRESH
SOA REFRESH
SOA REFRESH interval is: 86400. That is OK.
SOA RETRY
SOA RETRY
SOA RETRY value is: 7200, these data are perfect.
SOA EXPIRE
SOA EXPIRE
SOA EXPIRE number is: 604800. That is OK.
SOA MINIMUM TTL
SOA MINIMUM TTL
SOA MINIMUM TTL is: 7200. 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). Recommended value is 1-3 hours. Value of 7200 is OK.
MX
MX Records
MX Records
Your MX records that were reported by your name servers are:

5   smtpin.rzone.de   81.169.145.97 
[All these MX Records were found. If there are some non common MX records at your nameservers you should see them below.]
Pass
MX Name Validity
Good. I did not detect any invalid hostnames for your MX records.
Pass
MX IPs are public
All of your MX records appear to use public IPs.
Pass
MX is not IP
All of MX records are host names.
Number of MX records Info
Number of MX Records
Looks like you only have one MX record at your name servers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
Different MX records at nameservers Info
Different MX Records at Nameservers
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
Mismatched MX A Info
Mismatched MX A
OK. I did not detect differing IPs for your MX records.
Duplicate MX A records Info
Duplicate MX A Records
OK. I have not found duplicate IPs for your MX records. This is a good thing.
MX A request returns CNAME Info
MX A request returns CNAME
OK. No CNAMEs returned for A records lookups.
MX CNAME Info
MX CNAME Check
DNS Query has not found any errors in MX CNAME.
Ping
Ping Test Info
PING abarbanell.de (81.169.145.164) 56(84) bytes of data.
64 bytes from wa4.rzone.de (81.169.145.164): icmp_seq=1 ttl=250 time=15.0 ms
64 bytes from wa4.rzone.de (81.169.145.164): icmp_seq=2 ttl=250 time=14.9 ms

--- abarbanell.de ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 14.995/15.008/15.022/0.123 ms
DNS Query for Domain abarbanell.de created in 6.65 seconds
Legend of Status
DNS configuration correctly
The DNS settings are server is correctly
Nameserver Information
Information for nameserver connection
DNS settings warning
Nameserver configuration warning, optimize settings!
Nameserver Error
DNS Error / Fail, contact the nameserver administrator!

Chief Terms & Types for DNS Lookup

NS: Is the short form for Name Server (Records)
DNS: Domain Name System
A Record: Address record maps a hostname to a 32-bit IPv4 address
AAAA Record: IPv6 address record maps a hostname to a 128-bit IPv6 address
CNAME Record: Canonical name record is an alias of one name to another
MX Record: Mail exchange record maps a domain name to a list of mail exchange servers for that domain
PTR Record: Pointer record maps an IPv4 address to the canonical name for that host. Setting up a PTR record for a hostname in the in-addr.arpa domain that corresponds to an IP address implements reverse DNS lookup for that address
NS Record: Name Server record maps a domain name to a list of DNS servers authoritative for that domain
SOA Record: Start of authority record specifies the DNS Server providing authoritative information about an Internet domain
SRV Record: It is a generalized service location record
TXT Record: This record is used to implement the Sender Policy Framework
TTL: Time to Live set limits (lifetime) of data in a server, computer or network
FQDN: Fully Qualified Domain Name of Hostname
TLD: Top Level Domain (eg. .com .net .org etc.)
IP Address: Internet Protocol Address
Ping: Is a specific method (network communication) for sending messages from one server to another. Ping Test is the measurement of the badwidth and latency time
Skip to Top