Multiple Zone DNS Issue

Posted on 2007-11-15
Last Modified: 2010-04-21
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 ( and setup an external DNS service to point traffic to our external ip. That part appears to be working correctly, when pinging 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 (, for this project I setup a 2nd zone ( 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 ( Our firewall's primary DNS server settings point to our internal primary DNS server.

When I point a browser, whether internally or externally, to 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 while on the LAN the responses would be from server1's ip rather than our external ip. Alternately, when I ping (1st zone) the results are from server1's ip and not our external ip. I appreciate any help. Thanks
Question by:Ryan_Jantz
  • 3
  • 3
LVL 70

Expert Comment

by:Chris Dent
ID: 20290614

> I would think if internal DNS was setup right, when pinging
> 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.



Author Comment

ID: 20290897
Thanks for the response.

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

LVL 70

Expert Comment

by:Chris Dent
ID: 20291716

Ahhh okay I'm with you.

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

Did you clear the client Cache already?

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails


Author Comment

ID: 20292006
Right, our Primary DNS server is hosting the zone

Yes, I have cleared browser cache.

LVL 70

Accepted Solution

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:

set type=ns

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


Author Closing Comment

ID: 31409369
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

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Mimecast Bounce 3 30
Old Cisco access point to act as Repeater 5 39
Can’t delete a file 14 86
LibreNMS - unable to connect. 2 24
Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
After creating this article (, 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…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

757 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

17 Experts available now in Live!

Get 1:1 Help Now