Https and DNS Sam 5/17/2007 2:47:01 PM Hi All, If a website uses https for connectivity and has a Forward DNS entry resolving its domain name to a particular ip address e.g. Windsong.com to 217.65.1.1; however, the reverse DNS entry resolves the same ip address to a different domain name e.g. 217.65.1.1 to DanceSteps.com, and DanceSteps.com is not valid and does not have an associated forward DNS entry. Could that account for why some of the time users can connect to the website Windsong.com and some of the time they cannot?

Re: Https and DNS "Michael Dragone" <no.e-mail=less_spam> 5/17/2007 3:41:52 PM I don't see why, as long as the forward resolution of "windsong.com" always resolves to the correct IP address... "Sam" <Sam[ at ]discussions.microsoft.com> wrote in message news:27E5C8A4-2E71-49BD-9658-ED0BC5945E10[ at ]microsoft.com... [Quoted Text] > Hi All, > > If a website uses https for connectivity and has a Forward DNS entry > resolving its domain name to a particular ip address e.g. Windsong.com to > 217.65.1.1; however, the reverse DNS entry resolves the same ip address to > a > different domain name e.g. 217.65.1.1 to DanceSteps.com, and > DanceSteps.com > is not valid and does not have an associated forward DNS entry. Could > that > account for why some of the time users can connect to the website > Windsong.com and some of the time they cannot?

Re: Https and DNS "Mike Spike" <Mike[ at ]melted-Cpu-co.uk> 5/17/2007 3:49:30 PM I don't think reverse DNS will bother a Web browser as long a forward DNS works. I can't see a reason why a browser will need to do a reverse lookup. Regards, Mike. "Sam" <Sam[ at ]discussions.microsoft.com> wrote in message news:27E5C8A4-2E71-49BD-9658-ED0BC5945E10[ at ]microsoft.com... [Quoted Text] > Hi All, > > If a website uses https for connectivity and has a Forward DNS entry > resolving its domain name to a particular ip address e.g. Windsong.com to > 217.65.1.1; however, the reverse DNS entry resolves the same ip address to > a > different domain name e.g. 217.65.1.1 to DanceSteps.com, and > DanceSteps.com > is not valid and does not have an associated forward DNS entry. Could > that > account for why some of the time users can connect to the website > Windsong.com and some of the time they cannot? >

Re: Https and DNS "Herb Martin" <news[ at ]learnquick.com> 5/17/2007 7:31:16 PM "Sam" <Sam[ at ]discussions.microsoft.com> wrote in message news:27E5C8A4-2E71-49BD-9658-ED0BC5945E10[ at ]microsoft.com... [Quoted Text] > Hi All, > > If a website uses https for connectivity and has a Forward DNS entry > resolving its domain name to a particular ip address e.g. Windsong.com to > 217.65.1.1; however, the reverse DNS entry resolves the same ip address to > a > different domain name e.g. 217.65.1.1 to DanceSteps.com, and > DanceSteps.com > is not valid and does not have an associated forward DNS entry. Could > that > account for why some of the time users can connect to the website > Windsong.com and some of the time they cannot? It could but probably does NOT account for it. That is pretty normal. (The only way it would interfere is if the CLIENT was unwilling or complaining about that -- perhaps in the case of Certificates or a custom app, i.e., not a standard "browser".) Nslookup gives only one answer for Windsong.com so you only have to make sure this location works: Name: windsong.com Address: 209.133.21.201 This number does NOT however agree with the number you gave above which is a more serious issue if this happens regularly. Why did you include "HttpS" in the title of your posting? What does HTTPS have to do with it? (You never mentioned SSL in the rest of your post.) -- Herb Martin, MCSE, MVP http://www.LearnQuick.Com (phone on web site)