We are experiencing a very strange problem with our ADFS Environment.
When we connect to our ADFS Landing Page at https://adfs.mydomain.com and click the “Sign In” Button, something happens to make our workstations query DNS for a server other than adfs.mydomain.com.
This is shown in Fiddler in the highlighted portion at the lower right (shown below) where I see <h2> Object moved to <a href=’https://server-119.mydomain.com/adfs.ls/?SAMLRequest=…
See the fiddler analysis below.
How all of our 100+ websites behave
User enters the URL https://mywebsite.mydomain.com into their web browser to access the one of our websites.
User successfully arrives at the website using that URL.
User signs into the website, or clicks some links to go to other parts of the website.
The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename1.htm
User clicks more links on the website.
The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename2.htm
User clicks more links on the website and performs some complex tasks on the website.
The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename3.htm
How our ADFS Website Behaves - which is totally different than all our other websites
User enters the URL https://adfs.mydomain.com/adfs/ls/IdpInitiatedSignOn.aspx into their web browser to access the ADFS Landing Page.
User successfully arrives at the ADFS Landing page via that URL.
User clicks the "Click Continue to Sign In Button" on the ADFS Landing Page.
Something, most likely code on that landing page or somewhere else inside the ADFS Server, sends back information to the web browser with the name http://server-119.mydomain.com.
The User's computer then queries DNS for http://server-119.mydomain.com
The User's web browser then access http://server-119.mydomain.com directly and no longer goes through the load balancer.
This is my problem.
I have a feeling that ADFS has done something to IIS that is making IIS behave differently when ADFS sits inside of it, when compared to every other IIS website we have.
That’s what I need to get to the bottom of .