We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

IIS Website VERY slow when accessed via DNS name; fast when accessed via IP

netmergence
netmergence asked
on
Medium Priority
2,856 Views
Last Modified: 2013-12-14
I have a website that is running on IIS 6. The site is built in Visual Studio 2008 using the Crystal Reports plug-in.

When I access it via the DNS A-record, it runs at least 10 time slower than when I access it via the IP address.

When I resolve the A-record with nslookup or something, it resolves quickly, so it is not actually a DNS resolution problem.

I am completely stumped as to what could be causing this. Any ideas?

Thanks!
Comment
Watch Question

Commented:
Slow on all computers or just one?
Do you have more than one IP address? Do you have more than one interface? If so, what interface\IP is in DNS?
 

Author

Commented:
In response to the first comment, it is slow everywhere outside of the building. I do not have login access to any other internal machines, so I cannot test it from within their LAN.

The server technically has two IP addresses, because it has it's own private IP, then it has the public IP where 80 and 443 are just forwarded to it. However, the server itself only has the one, private IP assigned to its interface. There is just that one interface, and each IP address is only registerred in its corresponding DNS. (Internal DNS resolves the internal IP; external DNS shows the external IP.)

Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Commented:
Will you close the question and refund yourself points by accepting

07/10/09 02:13 PM, ID: 24828424

as your answer.

I am glad to see this is fixed for you. I am now reviewing IWA to see the ramifications of it.

Commented:
I also wanted to tell you from what I read, by disabling IWA, you are going to NTLM and LM hash authentication. This is an outdated protocol. We are now on NTLMv5 (Kerberos). So, I can't figure out for the life of me, why enabling the older authentication protocols works best for you.

Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.