thanks again.  we think the unknown domain issue may have been our custom phantomjs layer being spun down by heroku.  we upped the instances so they'll always be ready to answer.  also added some rel="canonical" in a few major places.