[aharrison]

Just thought I'd post this here in case anyone else noticed issues. I was having a good deal of trouble resolving blackberryforums.com and www.blackberryforums.com this morning. It wasn't affecting all of my name servers, 3 out of 4. It was just coming back with a SERVFAIL message:

$ dig www.blackberryforums.com 

; <<>> DiG 9.4.3-P3 <<>> www.blackberryforums.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25074
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.blackberryforums.com.      IN      A

;; Query time: 1 msec
;; SERVER: 65.175.128.181#53(65.175.128.181)
;; WHEN: Thu Mar  4 08:34:27 2010
;; MSG SIZE  rcvd: 42

Fortunately I run the name servers at my isp. I just did a flushname on all of my name servers for both of those names and it came back fine. Probably just a bit of cache corruption problems on my end, but just a heads up in case anyone notices trouble.

[dc/dc]

I had no problems here in Afghanistan.

[NJBlackBerry]

I'd be betting on the cache corruption.

[devnull]

same problem here... I run my own DNS server and had to flush the cache. I'm wondering if it has something to do with this:

https://www.verisign.com/domain-name...on-center/dns-
behavior/index.html

[aharrison]

I see what the problem is now. Definite misconfiguration on blackberryforum.com's side, but is also related to the verisign behavior changes.

# dig +trace blackberryforums.com @8.8.4.4 | grep black
; <<>> DiG 9.5.0-P2 <<>> +trace blackberryforums.com @8.8.4.4
blackberryforums.com.   172800  IN      NS      ns1.blackberrycenter.com.
blackberryforums.com.   172800  IN      NS      ns2.blackberrycenter.com.
blackberryforums.com.   14400   IN      A       74.86.254.234
blackberryforums.com.   86400   IN      NS      dns1.blackberryserver.com.
blackberryforums.com.   86400   IN      NS      dns2.blackberryserver.com.

Notice the dns[12].blackberryserver.com NS records. These records can't be resolved. Also, the NS records for blackberryserver.com are ns[12].blackberryserver.com, which also can't be resolved, so I believe this falls under the behavior described in the verisign notice.

So, basically, blackberryforums.com needs to drop those bogus extra NS records.

[devnull]

Originally Posted by aharrison

I see what the problem is now. Definite misconfiguration on blackberryforum.com's side, but is also related to the verisign behavior changes.

# dig +trace blackberryforums.com @8.8.4.4 | grep black
; <<>> DiG 9.5.0-P2 <<>> +trace blackberryforums.com @8.8.4.4
blackberryforums.com.   172800  IN      NS      ns1.blackberrycenter.com.
blackberryforums.com.   172800  IN      NS      ns2.blackberrycenter.com.
blackberryforums.com.   14400   IN      A       74.86.254.234
blackberryforums.com.   86400   IN      NS      dns1.blackberryserver.com.
blackberryforums.com.   86400   IN      NS      dns2.blackberryserver.com.

Notice the dns[12].blackberryserver.com NS records. These records can't be resolved. Also, the NS records for blackberryserver.com are ns[12].blackberryserver.com, which also can't be resolved, so I believe this falls under the behavior described in the verisign notice.

So, basically, blackberryforums.com needs to drop those bogus extra NS records.

I would agree there is a misconfiguration. I just had to flush my cache again to get to this site. I am wonder how many others are experiencing the same.

[JSanders]

I've not had a problem today -- I have a couple other times over the past couple years.

I'll pass this along to the clowns that run this joint.

[Dubdub]

I could not log on from my hotel in Rye NY this morning. Kept getting a page not found error.

[arieltf]

I have been having problems connecting to the forums for the past two evenings (after 7:00 pm MST) from my home. I use the Comcast DNS servers.

Last night, I tried accessing the forums from my BB, using Bolt, and got the same error.

During the day (at work) it was fine.

And, now this morning from home it is fine, too.

--Ariel

[lilin82]

I am having troubles accessing this site from my PC but not on my BB. It has been happening since Thursday. I could access for a few minutes but when I would go to another page I got the error. Today I tried to get on and I did but then I got the error again.

Any Ideas? I tried clearing my history, cache, etc and nothing.

[Dubdub]

I have had trouble since about 10 AM EST today. Couldn't get on using Safari and Firefox on the Mac, Firefox or IE8 on the PC or via wap on the BB. Did the flushdns trick several times but no joy. Just now getting on tonight.

[devnull]

when you are having issues, open a command prompt window and type this:

C:\>nslookup www.blackberryforums.com

I suspect you will get a result something like this:

"can't find www.blackberryforums.com: Server failed".

[Dubdub]

Can't do that on a Mac though, or at least I don't know the command in OS X.

[devnull]

Wirelessly posted (I'm mobile)

Hmm. I thought nslookup was available on every OS.

[Dubdub]

Tried to get it to run in Terminal and it wouldn't.

Just tried it on my other Mac and it did. Some days, it doesn't pay to get outta bed and play 'puters, does it?

[aharrison]

Everyone will continue to get the spotty performance until they fix the glue records for blackberryforums.com.

For a temporary workaround, you can add an entry in your hosts file. On a mac, open up a terminal and type all on one line:

echo "74.86.254.234 blackberryforums.com www.blackberryforums.com" | sudo tee -a /etc/hosts

(it will prompt you for your password because you need elevated privileges to edit that file)


On windows, edit the file c:\windows\system32\drivers\etc\hosts and add the line:

74.86.254.234 blackberryforums.com www.blackberryforums.com

[Dubdub]

Thanks

[ifonline]

Originally Posted by Dubdub

Can't do that on a Mac though, or at least I don't know the command in OS X.

On a Mac, all you need to do is run Network Utility and select the Lookup tab.

[Dubdub]

Thanks for the info.

[John Clark]

I was unable to access this site (and only this site) from a hotel the other day too. This has happened before from home as well.