Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Multiple Zone DNS Issue

Posted on 2007-11-15
6
Medium Priority
?
242 Views
Last Modified: 2010-04-21
Hello,
I am setting up a remote access solution on one of our internal servers (server1) that users will connect to via https in a browser. I have registered a new domain name (domain2.net) and setup an external DNS service to point traffic to our external ip. That part appears to be working correctly, when pinging domain2.net from internal and external sources the replies are from our external ip. In the past our Win2K primary DNS server has had just one Forward Lookup Zone (domain1.com), for this project I setup a 2nd zone (domain2.net). In the 2nd zone I created an A record pointing to the static ip of server1. There is an identical A record for server1 in the 1st zone (domain1.com). Our firewall's primary DNS server settings point to our internal primary DNS server.

When I point a browser, whether internally or externally, to https://server1.domain2.net we get a "server took too long to respond message". At this point, I'm not sure if it's an internal DNS issue or an issue with our firewall not resolving with our Primary DNS server. I would think if internal DNS was setup right, when pinging server1.domain2.net while on the LAN the responses would be from server1's ip rather than our external ip. Alternately, when I ping server1.domain1.com (1st zone) the results are from server1's ip and not our external ip. I appreciate any help. Thanks
0
Comment
Question by:Ryan_Jantz
  • 3
  • 3
6 Comments
 
LVL 71

Expert Comment

by:Chris Dent
ID: 20290614

> I would think if internal DNS was setup right, when pinging server1.domain2.net
> while on the LAN the responses would be from server1's ip rather than our external ip

It will only respond with the information you've told it to respond with. So if you gave it the External IP then it will respond with that. Windows 2000 (or 2003) DNS aren't capable of changing their response based on the requesting clients network range (NetMask Ordering doesn't really count in that as it's just not configurable enough to make it really useful).

Basically, if the Name Resolves to an IP Address then the work of DNS is done and it would be prudent to look at the Firewall as you were thinking.

Chris

0
 

Author Comment

by:Ryan_Jantz
ID: 20290897
Chris-Dent,
Thanks for the response.

It seems that if I have an A record in zone domain2.net that points to server1's static ip, when I ping server1.domain2.net the replies should be from server1's ip rather than our external ip. It looks like our Primary DNS server can't resolve server1.domain2.net and throws it out to our gateway which eventually gets resolved by an external DNS as our external ip.

Thanks
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 20291716

Ahhh okay I'm with you.

The Primary DNS Server is hosting the zone for domain2.com? Or do you use Forwarders to the system that does?

Did you clear the client Cache already?

Chris
0
Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

 

Author Comment

by:Ryan_Jantz
ID: 20292006
Right, our Primary DNS server is hosting the zone domain2.net.

Yes, I have cleared browser cache.

Thanks
0
 
LVL 71

Accepted Solution

by:
Chris Dent earned 2000 total points
ID: 20296987

And clients don't use any other Name Server in their configuration?

In NSLookup can you try:

nslookup
set type=ns
domain2.net

If the zone is correctly loaded it should respond with itself as name server for that domain.

Chris
0
 

Author Closing Comment

by:Ryan_Jantz
ID: 31409369
Chris,
I appreciate the info you provided and am awarding points. Ends up the DNS server I thought was the Primary was not. I've walked into a system with no thing documented. After I  added the zone to this other DNS server then all was well. Your info clued me in. Thanks
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Tech spooks aren't just for those who are tech savvy, it also happens to those of us running a business. Check out the top tech spooks for business owners.
LinkedIn blogging is great for networking, building up an audience, and expanding your influence as well. However, if you want to achieve these results, you need to work really hard to make your post worth liking and sharing. Here are 4 tips that ca…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

572 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