• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 437
  • Last Modified:

How to enable Short URLS in AD DNS

Strange problem.

We recently migrated our public web site to a hosted web site, that is both accessible to internal users via a VPN connection to our hosting partner as well as from the public internet.

Prior to doing this, internal users could connect to the short URL for the site using http://domain.com/subpage versus http://www.domain.com/subpage.

The public can access http://domain.com/subpage just fine, DNS is hosted by Nuestar and there is a wildcard that allows this.

Internally, our clients use AD DNS for resolution, and this ONLY WORKS FOR FIREFOX USERS.

IF an IE or Chrome client tries to connect to http://domain.com - that works, but http://domain.com/subpage does not.  Firefox works for both situations.

I tried adding *.domain.com as both an A and CNAME record pointing to our internal IP and also to our public IP, but neither work.

It sounds like an issue with AD DNS but it's weird that it works with Firefox so I'm not sure if there is a client issue on top of that.

Suggestions?
0
netbones
Asked:
netbones
1 Solution
 
donnkCommented:
its an IIS setting rather than DNS, I've got it in the 'big book of usefull stuff' at work will look it up later.
0
 
masnrockCommented:
It is an IIS setting, but there is some DNS to be done as well. You need to making a binding for domain.com to your existing IIS site. Also, in DNS you need to make sure there is a CNAME entry for domain.com
0
 
MaheshArchitectCommented:
if http://domain.com is working from internal network, means base url is resolving properly

What versions of IE and firefox you are using..

It might be the browser issue.

Mahesh
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
netbonesAuthor Commented:
Versions of IE and Chrome vary - it's happening to everyone on the internal network, but Firefox works for everyone, regardless of version.

IIS shouldn't come into play, our web site, when internal, was hosted on Apache/Linux and still is at the co-lo.
0
 
masnrockCommented:
Is domain.com the name of the AD domain?
0
 
netbonesAuthor Commented:
No, it's not.  The name of the local domain is domain.local, and "domain" is a completely separate name from the .com one.

As an example. The website address is www.domain.com, the local AD domain is something.local.

I have AD DNS setup for the .local zone and also for the domain.com zone.
0
 
masnrockCommented:
OK, great. Well, in that case, you could actually get rid of the domain.com zone and delete domain.com related entries, but I'm also assuming that there is nothing onsite that you need it for anymore. That way, proper lookups would occur, and that should eliminate the problem for ALL browsers.
0
 
netbonesAuthor Commented:
Interesting answer, let me think about what dependencies we have onsite that require it to be there, it could be we don't and that will fix the problem, I'll report back on Monday and let you know!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

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