Solved

registering with dns

Posted on 2009-07-10
2
250 Views
Last Modified: 2012-05-07
when a client connects via vpn with their laptop from home, they get a 10.10.50.x address from the cisco asa dhcp server.  everything works fine.  ok.  they come into the office and plug into the network, and get a new address - 10.10.10.x or 10.10.20.x..

ok, the problem is that the dns server still has the 10.10.50.x address.  i have set the scavenging/aging down to 12 hours for the refresh interval, and 12 days for the non-refresh... the defaul is 7 days for each.

in order to resolve this, i have to delete the A record and do an ipconfig /registerdns in order for the dns server to update the database with the new ip address.

any idea how i can fix this problem?
0
Comment
Question by:cmourn
2 Comments
 
LVL 70

Accepted Solution

by:
Chris Dent earned 500 total points
ID: 24826383

First things first, the 12 hours refresh: I know why you've set it, but it'll cause you problems.

Your servers, and everything else with static IP addressing only Refresh once every 24 hours. If any miss the chance the record will be removed as Stale. Because of the long no-refresh you won't bump into this often, but when you do I'd say it'll be quite irritating. Also depends on your Scavenging Period, but eventually it'll get lucky.

In your situation I would head to the DHCP server, turn off dynamic updates there and let the client deal with it (unless you have pre-Windows 2000 stuff this won't be a problem). It'll take a while to swap over, the security on the existing records is all wrong for client update, but it'll get there eventually.

Update requests (when a client changes IP) will always be allowed, even during No-Refresh.

If you're after more specific Refresh / No-Refresh intervals it tends to be best to set No-Refresh + Refresh to match the Renewal Interval of DHCP (half the lease duration), avoiding values less than 24 hours for the Refresh for the reasons above.

For example, a 20 day DHCP lease works well with 5 days No-Refresh and 5 Days Refresh.

Chris
0
 

Author Comment

by:cmourn
ID: 24827067
ok, i have turned off dynamic updating on the dhcp server, so that the client can handle updating dns.  i change the refresh interval to 24 hours, and the non-refresh to 3 days.  the lease period is 6 days.  we'll see how this works.  thanks for the feedback.... will report back shortly...
0

Featured Post

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Router assigned IP addresses 18 88
Password managers 1 31
Windows DNS Server Caching 3 28
Additional DC vs Child Domain 12 17
Quality of Service (QoS) options are nearly endless when it comes to networks today. This article is merely one example of how it can be handled in a hub-n-spoke design using a 3-tier configuration.
Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
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.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

786 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