Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

secondary DNS behavious when cutoff from primary DNS

Posted on 2013-01-04
1
Medium Priority
?
294 Views
Last Modified: 2013-01-04
Hi

One of my clients manages a central HQ, plus remote sites.

The HQ has a Windows 2008 acting as the primary DNS server,
while the Windows 2008 stand alone servers at the remote sites
all act as secondary DNS servers to the primary.  

The forwarding server of these secondary DNS servers is
set to the primary server, and not to the local ISP's DNS
- which to me seems wrong.

The remote site servers also run an in-house web app

When the remote site's Internet link goes down, the local
workstations continue to access the local web app unhindered.

Twenty four hours later, however, the workstations can't
access the web app anymore. The server hasn't been rebooted;
I'm not sure whether the workstation has been switched off
overnight, although I suppose it has.

The two solutions used up till now were connecting to the app
using the local server's IP address, or by inserting the local
server's FQDN and IP pair into the workstation's host file.

Obviously this type of situation doesn't happen too frequently.

What I'd like to know, the next time this happens, is what address
does the web app resolve to on the workstations when it fails ?

Any ideas ?
I'll add the responses asap to the two queries I formulated here
while writing my question.

thanks

yann
0
Comment
Question by:Yann Shukor
[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
1 Comment
 
LVL 15

Accepted Solution

by:
Frabble earned 2000 total points
ID: 38746030
I suspect the SOA record for the zone has the expiry time set to the default of 24 hours. After this time, if a secondary DNS cannot contact a primary name server, it will stop answering queries for this zone because it considers the data too old to be reliable.
You can fix this by changing the SOA Expire time value on the primary DNS for that zone to something else, for example, 3 days - something longer than a remote site link stays down for.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

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

In my time as an SEO for the last 2 years and in the questions I have assisted with on here I have always seen the need to redirect from non-www urls to their www versions. For instance redirecting http://domain.com (http://domain.com) to http…
If your site has a few sections that need to be secure when data is transmitted between the server and local computer, such as a /order/ section for ordering or /customer/ which contains customer data, etc it would of course be recommended to secure…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…
How to fix incompatible JVM issue while installing Eclipse While installing Eclipse in windows, got one error like above and unable to proceed with the installation. This video describes how to successfully install Eclipse. How to solve incompa…
Suggested Courses

715 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