07-07-2004, 01:41 AM
I am recently unable to connect to battle.net. This had never happened before. Everyone else I know is able to do so with the exception of my family's computer. So I used blizzard's support pages and it told me it was probably a DNS problem. So I went wondering about what was DNS and I found a DNS checker :S I tried using it and this was the info it told me:
DNS Report for battle.net
Generated by www.DNSreport.com at 02:27:42 GMT on 07 Jul 2004.
Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:
eur-guard.battle.net. [213.248.106.251] [TTL=172800] [EU]
kor-guard.battle.net. [211.233.0.123] [TTL=172800] [KR]
use-guard.battle.net. [63.240.202.178] [TTL=172800] [US]
usw-guard.battle.net. [63.241.83.59] [TTL=172800] [US]
[These were obtained from h.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there, with 4 entries.
PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
NS INFO NS records at your nameservers Your NS records at your nameservers are:
usw-guard.battle.net. [TTL=43200]
blz-test01.battle.net. [TTL=43200]
use-bna-router.battle.net. [TTL=3600]
usw-bna-router.battle.net. [TTL=43200]
eur-guard.battle.net. [TTL=43200]
use-guard.battle.net. [TTL=43200]
kor-bna-router.battle.net. [TTL=43200]
eur-bna-router.battle.net. [TTL=43200]
kor-guard.battle.net. [TTL=43200]
bur-guard.battle.net. [TTL=43200]
PASS All nameservers report identical NS records OK. The NS records at all your nameservers are identical.
PASS All nameservers respond OK. All of your nameservers listed at the parent nameservers responded.
PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASS Number of nameservers OK. You have 4 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
FAIL Missing (stealth) nameservers FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly.
blz-test01.battle.net.use-bna-router.battle.net.usw-bna-router.battle.net.kor-bna-router.battle.net.eur-bna-router.battle.net.bur-guard.battle.net.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
PASS Missing nameservers 2 OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.
PASS No CNAMEs for domain OK. There are no CNAMEs for battle.net. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. Note that I only checked battle.net, I did not check the NS records, which should not have CNAMEs either.
PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS Nameservers on separate class C's OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
INFO Nameservers versions Your nameservers have the following versions:
213.248.106.251: No version info available (CHAOS not implemented).
211.233.0.123: No version info available (CHAOS not implemented).
63.240.202.178: No version info available (CHAOS not implemented).
63.241.83.59: No version info available (CHAOS not implemented).
PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.
SOA INFO SOA record Your SOA record [TTL=43200] is:
Primary nameserver: kor-guard.battle.net.
Hostmaster E-mail address: support.blizzard.com.
Serial #: 2003071320
Refresh: 3600
Retry: 600
Expire: 1209600
Default TTL: 43200
FAIL NS agreement on SOA Serial # ERROR: Your nameservers disagree as to which version of your DNS is the latest! 2003071314 versus 2003071320! This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 2003071320 is the correct serial #.
PASS SOA MNAME Check OK. Your SOA (Start of Authority) record states that your master (primary) name server is: kor-guard.battle.net.. That server is listed at the parent servers, which is correct.
PASS SOA RNAME Check OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: support@blizzard.com. (techie note: we have changed the initial '.' to an '@' for display purposes).
PASS SOA Serial Number OK. Your SOA serial number is: 2003071320. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.
PASS SOA REFRESH value OK. Your SOA REFRESH interval is : 3600 seconds. This seems normal (about 3600-7200 seconds is good; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). This value determines how often secondary/slave nameservers check with the master for updates.
PASS SOA RETRY value OK. Your SOA RETRY interval is : 600 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
PASS SOA EXPIRE value OK. Your SOA EXPIRE time: 1209600 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
PASS SOA MINIMUM TTL value OK. Your SOA MINIMUM TTL is: 43200 seconds. This seems normal (about 60 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
MX INFO MX Record Your 1 MX record is:
10 mail.battle.net. [TTL=43200] IP=12.41.72.204 [TTL=43200] [US]
PASS Invalid characters OK. All of your MX records appear to use valid hostnames, without any invalid characters.
PASS All MX IPs public OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
PASS MX records are not CNAMEs OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
PASS MX A lookups have no CNAMEs OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).
PASS MX is host name, not IP OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
WARN Multiple MX records WARNING: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you.
PASS Duplicate MX records OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site. The problem MX records are:
204.72.41.12.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 1)]
Mail FAIL Connect to mail servers ERROR: I could not complete a connection to any of your mailservers!
mail.battle.net: Timed out [Last data sent: None]
If this is a timeout problem, note that the DNS report only waits about 30 seconds for responses, so your mail may work fine in this case but you will need to use testing tools specifically designed for such situations.
WWW INFO WWW Record Your www.battle.net A record is:
www.battle.net. A 63.236.3.71 [TTL=3600] [US]
PASS All WWW IPs public OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.
PASS CNAME Lookup OK. Some domains have a CNAME record for their WWW server that requires an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. There are no CNAMEs for www.battle.net, which is good.
If anyone can help me , I would be really grateful.
DNS Report for battle.net
Generated by www.DNSreport.com at 02:27:42 GMT on 07 Jul 2004.
Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:
eur-guard.battle.net. [213.248.106.251] [TTL=172800] [EU]
kor-guard.battle.net. [211.233.0.123] [TTL=172800] [KR]
use-guard.battle.net. [63.240.202.178] [TTL=172800] [US]
usw-guard.battle.net. [63.241.83.59] [TTL=172800] [US]
[These were obtained from h.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there, with 4 entries.
PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
NS INFO NS records at your nameservers Your NS records at your nameservers are:
usw-guard.battle.net. [TTL=43200]
blz-test01.battle.net. [TTL=43200]
use-bna-router.battle.net. [TTL=3600]
usw-bna-router.battle.net. [TTL=43200]
eur-guard.battle.net. [TTL=43200]
use-guard.battle.net. [TTL=43200]
kor-bna-router.battle.net. [TTL=43200]
eur-bna-router.battle.net. [TTL=43200]
kor-guard.battle.net. [TTL=43200]
bur-guard.battle.net. [TTL=43200]
PASS All nameservers report identical NS records OK. The NS records at all your nameservers are identical.
PASS All nameservers respond OK. All of your nameservers listed at the parent nameservers responded.
PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASS Number of nameservers OK. You have 4 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
FAIL Missing (stealth) nameservers FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly.
blz-test01.battle.net.use-bna-router.battle.net.usw-bna-router.battle.net.kor-bna-router.battle.net.eur-bna-router.battle.net.bur-guard.battle.net.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
PASS Missing nameservers 2 OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.
PASS No CNAMEs for domain OK. There are no CNAMEs for battle.net. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. Note that I only checked battle.net, I did not check the NS records, which should not have CNAMEs either.
PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS Nameservers on separate class C's OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
INFO Nameservers versions Your nameservers have the following versions:
213.248.106.251: No version info available (CHAOS not implemented).
211.233.0.123: No version info available (CHAOS not implemented).
63.240.202.178: No version info available (CHAOS not implemented).
63.241.83.59: No version info available (CHAOS not implemented).
PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.
SOA INFO SOA record Your SOA record [TTL=43200] is:
Primary nameserver: kor-guard.battle.net.
Hostmaster E-mail address: support.blizzard.com.
Serial #: 2003071320
Refresh: 3600
Retry: 600
Expire: 1209600
Default TTL: 43200
FAIL NS agreement on SOA Serial # ERROR: Your nameservers disagree as to which version of your DNS is the latest! 2003071314 versus 2003071320! This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 2003071320 is the correct serial #.
PASS SOA MNAME Check OK. Your SOA (Start of Authority) record states that your master (primary) name server is: kor-guard.battle.net.. That server is listed at the parent servers, which is correct.
PASS SOA RNAME Check OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: support@blizzard.com. (techie note: we have changed the initial '.' to an '@' for display purposes).
PASS SOA Serial Number OK. Your SOA serial number is: 2003071320. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.
PASS SOA REFRESH value OK. Your SOA REFRESH interval is : 3600 seconds. This seems normal (about 3600-7200 seconds is good; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). This value determines how often secondary/slave nameservers check with the master for updates.
PASS SOA RETRY value OK. Your SOA RETRY interval is : 600 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
PASS SOA EXPIRE value OK. Your SOA EXPIRE time: 1209600 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
PASS SOA MINIMUM TTL value OK. Your SOA MINIMUM TTL is: 43200 seconds. This seems normal (about 60 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
MX INFO MX Record Your 1 MX record is:
10 mail.battle.net. [TTL=43200] IP=12.41.72.204 [TTL=43200] [US]
PASS Invalid characters OK. All of your MX records appear to use valid hostnames, without any invalid characters.
PASS All MX IPs public OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
PASS MX records are not CNAMEs OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
PASS MX A lookups have no CNAMEs OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).
PASS MX is host name, not IP OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
WARN Multiple MX records WARNING: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you.
PASS Duplicate MX records OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site. The problem MX records are:
204.72.41.12.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 1)]
Mail FAIL Connect to mail servers ERROR: I could not complete a connection to any of your mailservers!
mail.battle.net: Timed out [Last data sent: None]
If this is a timeout problem, note that the DNS report only waits about 30 seconds for responses, so your mail may work fine in this case but you will need to use testing tools specifically designed for such situations.
WWW INFO WWW Record Your www.battle.net A record is:
www.battle.net. A 63.236.3.71 [TTL=3600] [US]
PASS All WWW IPs public OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.
PASS CNAME Lookup OK. Some domains have a CNAME record for their WWW server that requires an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. There are no CNAMEs for www.battle.net, which is good.
If anyone can help me , I would be really grateful.
Raz