Solved

Multiple Zone DNS Issue

Posted on 2007-11-15
6
230 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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
Why Off-Site Backups Are The Only Way To Go

You are probably backing up your data—but how and where? Ransomware is on the rise and there are variants that specifically target backups. Read on to discover why off-site is the way to go.

 

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 500 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 NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

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

If your business is like most, chances are you still need to maintain a fax infrastructure for your staff. It’s hard to believe that a communication technology that was thriving in the mid-80s could still be an essential part of your team’s modern I…
If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
Suggested Courses

724 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