[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 81
  • Last Modified:

Same domain name internal and external. Even with A Record, server and clients see IIS page

Server 2012
A record for WWW created pointing to external web server
Server and clients see IIS start page when browsing www.ourfirm.com
NSLOOKUP returns proper external IP
brain hurts...

I have done this several times with other clients. The only difference here is Server 2012. What am missing here?

Thank you!
Tom
0
Tom_Bombaci
Asked:
Tom_Bombaci
  • 6
  • 6
1 Solution
 
QlemoC++ DeveloperCommented:
What does ping tell? The resolving mechanism is slightly different from nslookup, so it might get different results. ipconfig /displaydns should also be checked.
0
 
Tom_BombaciAuthor Commented:
pinging www.ourfirm.com results in the correct IP responding

ipconfig /displaydns returns the proper IP for www.ourfirm.com


Thank you,
Tom
0
 
GauthierCommented:
IPV6 issues?
or a proxy?
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
Tom_BombaciAuthor Commented:
I am thinking IPv6 too. Ipconfig /didplaydns returns nothing under an AAAA record for www.ourfirm.com
0
 
GauthierCommented:
Try from an old windows XP client to be sure.
But if there is nothing in displaydns, then IPV6 is very unlikely, unless ping www would replay with AAAA.

That leave the proxy option, but you would know if there was one no?
0
 
GauthierCommented:
Is the internet gateway the 2012 server?
Normally that shouldn't be the case.
0
 
Tom_BombaciAuthor Commented:
No proxy. The gateway is the firewall.

Tom
0
 
GauthierCommented:
and ping www (without the .ourfirm.com) ?
0
 
GauthierCommented:
If that's not it, my last hypothesis is that your external website is really also currently displaying the IIS welcome page :)
or you forgot to clear the browser cache...
0
 
Tom_BombaciAuthor Commented:
Pinging "www" returns the external IP. :) Tried two browsers, clearing cache(s), three machines. I am at a serious loss here. I am contemplating renaming the domain....
0
 
Tom_BombaciAuthor Commented:
Well, it seems when I browse to the clients website from home, it resolves to ourfirm.com (dropping the www). Having said that, I would presume the A Record "WWW" is doing its job since "ourfirm.com" is indeed itself in DNS on the local server.

Renaming the domain seems like the best answer and the path of least resistance.
0
 
GauthierCommented:
The naked domain problem with AD, bad luck :(

Either disable the redirect on the external hosting.
It can be done with no problem regarding indexing so long as users do not mess up their communications and you add an canonical header tag to your html.
Or preferably (it avoid endless DNS problems) as you said, rename the domain to something like corp.ourfirm.com or another domain like ourfirm.local
0
 
Tom_BombaciAuthor Commented:
Tried my own suggestion
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now