Computing.Net > Forums > Networking > DNS and Forward Lookup Zone

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

DNS and Forward Lookup Zone

Reply to Message Icon

Name: Paul at IPS
Date: February 23, 2009 at 12:45:10 Pacific
OS: WINDOWS Server 2003
CPU/Ram: 2 gig
Product: Dell / Poweredge 1750
Subcategory: Servers
Comment:

Good Afternoon All,

I need some advice as to why my DMZ zone keeps needing to be reloaded each morning, and periodically through the day. We recently changed IPS carriers. This was not an issue before the change. I am fairly new at IT, server, AD, DNS, DHCP administration. I am not sure what configuration is messed up and causing the Forward Lookup Zone that points to my DMZ keeps getting lost.

BTW: This is occurring from within my internal domain. Can someone advise me to what I need to change?

Regards,
Paul

Regards,
Paul



Sponsored Link
Ads by Google

Response Number 1
Name: Curt R
Date: February 23, 2009 at 14:04:08 Pacific
Reply:

I suspect this will have to do with the DNS entries in your forward lookup zone. I wager when you changed providers, your external IP address changed and this could be the issue. Check your DNS records. Any showing the old IP would likely need to be changed to reflect your new external IP. I'm not sure which entries in particular you would have to check (it's been a while since I administered a Windows domain and it's DNS) so you'll likely have to go through all of them unless somebody else who does know speaks up and tells you where to look.

Incorrect DNS configuration will definately affect LAN users accessing external resources but shouldn't affect their ability to access internal unless you have more wrong with your DNS than I think you have.


0

Response Number 2
Name: Paul at IPS
Date: February 23, 2009 at 14:55:17 Pacific
Reply:

Hi Curt R,

Thanks for your reply. The forward lookup zones have been thoroughly gone over and cleaned from all old IP's address and stale DNS records.

The issue is this: I have two domains. The DMZ (public) and our internal domain; on the DMZ domain, I just have that domain in the forward and reverse lookups, they are "type" primary for this domain.

In the internal domain; I have the internal domain as "type" primary and the DMZ as "type" secondary domain with zone transfers allowed ONLY to the two internal domain servers, using their IP address.

Last week I noticed that I could not hit my DMZ servers from my laptop and a little research reveled that the DMZ forward lookup zone was NOT being loaded, so I "re-loaded" the zone and all was fine. Until I noticed that it was happening each day. The DMZ zone seems to get lost, requiring me to re-load the zone again. Advice?

Regards,
Paul


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: DNS and Forward Lookup Zone

dns issures + host headers www.computing.net/answers/networking/dns-issures-host-headers/14212.html

DNS Reverse Lookup Zones www.computing.net/answers/networking/dns-reverse-lookup-zones/17678.html

DNS WAN and IIS WebSite www.computing.net/answers/networking/dns-wan-and-iis-website/34832.html