Monday, November 18, 2013

Network Solutions = AOL Email. If you want to be respected in the 21st century switch to another provider.

Worked on a server environment migration to a datacenter yesterday. Everything went smoothly except for DNS was not working for the client. I spent an extra 2 hours troubleshooting DNS. I repeatedly attempted to update DNS in the Network Solutions webpage, and it would not show the updated entries. Tried with IE, Chrome, and multiple OSes. Nada. Turns out it was a bug in the NetSol system. A call to support indicated that. So, I was assured it would be resolved on Sunday, almost 24 hrs later on Monday, still not working. DNS A records are showing up web page with one entry, and the result is not showing up on the NetSol NS query responses. So, if you updated with and do a DNS query the original IP pre-Sunday.

Just to be CLEAR.... if I query & which are the client's NS entries PER Network Solutions, they respond with the wrong entries. How nice. Call to support, and the script reading call rep, didn't understand the issue and kept repeating it takes 24 hours to propagate. Another favorite is you delete or change an entry on the NetSol "advanced DNS" page and the changes aren't displayed. Logout and log back in, same info. This happens on the main webpage and DNS as well. What a joke of a system. I tried to switch to a 3rd party DNS system, and the NetSol NS are not following the DNS spec for NS lookups at point of entry (I added my NS entries, etc). NetSol claimed they cant' be found, but even the native Windows DNS finds them. Sigh.... So sad the founding internet's domain name provider has failed so badly similar to AOL.

DNS Tool I like since it allows me to query against any NS and for any record


Wednesday, February 27, 2013

BES 5 & BES 10 Server Consolidation Coming...

Currently, users running BB 4-7 need BES 5 and BB 10 requires BES 10. So, you need to run 2 separate servers for BES 5 & BES 10. This will be changing once an update is released to BES 10 (ETA is May 2013). This update will be "managed using a single fully featured management console". Then BES 10 & BES 5.0.3+ will be able to run on the same server. Very helpful.


Exchange 2010 & 2013 Compatible Not There Yet...

With the recent release of Service Pack 3 for Exchange Server 2010 compatibility with Exchange Server 2013, we are getting closer, but NOT yet. Now Exchange Server 2013 needs an update. The update is tentatively called Exchange Server 2013 CU1. That will then allow integration between 2010 & 2013. ETA should be available "shortly". I would guess March or April of 2013.


Wednesday, February 13, 2013

Apple Screws Up iOS EAS Implementation AGAIN! - Exchange Suffers

Has your Exchange 2010 CAS recently started experiencing heavy CPU, insane transaction logs growth (aka DoS), Apple might be the cause. Apple released iOS 6.1 last week (beginning of Feb) and it has a "slight" EAS bug in it. ;-) Another bonus... it drained iOS batteries and wasted data bandwidth. So bad... Vodafone txted all iPhone users to NOT upgrade to 6.1. Oops.... and 6.1.1 doesn't fix it...

You would think a large company (aka Apple) that prides itself on releasing "amazing products" would not repeat their mistakes in the past (iOS 4), but sadly history is repeating itself. iOS 6.1.1 fixed another problem. This is why I am not a fan of EAS. It's buggy since vendors don't have a real incentive or pressure to make sure EAS works well. Sure, Microsoft releases "guidelines" and crosses it's fingers vendors follow, but it's a frequent problem. I know, since I see the EAS connections logs and the Exchange problems they cause. I'll post in the future, how to look this up in your Exchange logs. I'm leaving EAS soon enough... I'll be happy to return to the BlackBerry ecosystem when the Q10 is released. That's another post...

See the Microsoft KB article, but to summarize, there are is a quick fix:

- delete the Exchange account from the iOS device and re-add

iOS 6.1 EAS Bug - Workarounds

iOS 4 EAS Bug (walk down memory lane)