Solved

Help with DNS and local network routing to public address properly

Posted on 2012-03-29
4
466 Views
Last Modified: 2012-04-02
I have a new client with a specific set up needed and I am having a hard time working out exactly how to make it work.  Direction would be appreciated, I know it is a bit convoluted but I will do my best to explain.  Hopefully the diagram will help.  DomainConfigIssue.pdf.
The company's local network domain has been configured using their public domain name.  abc.com.  They have a web server that was running two different sites.  abc.com and myinfo.abc.com.  

The main public site, abc.com, has an option for their clients to log in and access their account information at myinfo.abc.com and that site works with a special application controlled by their software vendor.

They decided to have a web design company do their public site and host it on their servers.  Outside their office everything works fine because public DNS recs for abc.com is set to point to the new hosting company IP addresses and the subdomain myinfo still points to the office public IP.

The problem happens when they try to access any sites on the local domain.  Since the local domain is abc.com and they have configuration pointing to services and other servers using xxx.abc.com there is a lot of traffic flowing on the private network using the public domain name that never needs to leave the private network.  The only traffic that does need to leave is what is directed to the www public site.

When they were testing the new site I took the IIS config of abc.com on the local network web server and redirected it to the-hosting-IP-address/~abc.om and it worked perfectly.  Now, they went live and the hosting company changed the domain to mask so you don't see the IP address any longer, which they should.  However, that makes it unable to find the site from the local network now because abc.com redirects to the IP address which displays a 404 page because it isn't there any longer.

Without doing a lot of configuration changes on the network how can I get it to route just the www.abc.com to the public DNS but only www and no other names in that domain?  It is a fairly new client and we don't have everything sorted yet so we were hoping to not make too many changes to an environment we don't have fully evaluated.
0
Comment
Question by:dcgrindle
4 Comments
 
LVL 39

Accepted Solution

by:
footech earned 500 total points
Comment Utility
You should be able to find the IP of the web site at any time by running an nslookup query.  For example, nslookup www.abc.com 8.8.8.8
This will run the query against Google's public DNS (8.8.8.8), but you could run it against any DNS server's IP that you want.  Then just create a record for "www" in your forward lookup zone for your domain name on your internal DNS servers that points to the public IP for your website.  The IP shouldn't change so you shouldn't have to worry about that.

If you really need it to query the public DNS, a conditional forwarder configured for "www.abc.com" and pointing to the public nameservers *might* work, but I'm not certain.
0
 
LVL 5

Expert Comment

by:cdfs
Comment Utility
In your internal DNS either configure an A-record pointing to the new IP or if this is not possible by any means (DNS-loadbalancing e.x.), configure a CNAME-record, pointing to the new subdomain. This way your internal clients will querry your internal DNS and get either the correct new IP or if configured with CNAME get the proper subdomain, resolving it properly to the new IP-adress(es).
0
 
LVL 5

Expert Comment

by:abhishek1986
Comment Utility
Your server must have a internal IP Address as well as a global one?
For internal users, they need not go via the internet. They should be able to access the page locally, via the Local Network. All you need to do is to define a host name and a IP Address corresponding to it. Publish the link to the users and you are good to go.
0
 
LVL 2

Author Closing Comment

by:dcgrindle
Comment Utility
We were able to do it in a Forward lookup A record for www - the internal users must enter www and not use a naked domain but it works fine as long as they enter www.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

Suggested Solutions

Logparser is the smartest tool I have ever used in parsing IIS log files and there are many interesting things I wanted to share with everyone one of the  real-world  scenario from my current project. Let's get started with  scenario - How do w…
If you have a multi-homed DNS setup in windows, you can have issues with connectivity to the server that hosts the DNS services (or even member servers of your domain if this same DNS server is a DC). This is because windows registers all of its IPs…
It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now