OK, when you said they had static IPs I didn't think about that many of them.
The flip side is that could probably scripted and if your environment has that
many static assignments it might be worth it.
As to the why part, I can't answer that. I fight that battle occasionally here
as well. We'll have machines that have been on the network for months and
suddenly they disappear from DNS.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
-----Original Message-----
From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On
Behalf Of Michael Leone
Sent: Monday, June 15, 2015 9:05 AM
To: ntsys...@lists.myitforum.com
Subject: Re: [NTSysADM] DNS errors after installing Win2012 R2 DCs
On Mon, Jun 15, 2015 at 8:48 AM, Melvin Backus <melvin.bac...@byers.com> wrote:
> It sounds like they're getting tombstoned. If they're static IPs try setting
> the DNS entries statically as well.
Manually entering them into DNS, you mean? I am really trying to avoid entering
hundreds of IPs statically into DNS ..
And why would they be tombstoning so soon?
>
> --
> There are 10 kinds of people in the world...
> those who understand binary and those who don't.
>
> -----Original Message-----
> From: listsadmin@lists.myitforum.com
> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Michael Leone
> Sent: Monday, June 15, 2015 8:41 AM
> To: ntsys...@lists.myitforum.com
> Subject: [NTSysADM] DNS errors after installing Win2012 R2 DCs
>
> I have installed 3 new Win2012 R2 DCs, which will be the replacements for my
> Win2008 R2 DCs. I have repointed everything to use one of the new Win2012 DCs
> for DNS, rather than the Win2008 R2. And now I am seeing DNS errors.
>
> Specifically, hosts will just drop out of DNS. (these are servers with static
> IPs). An nslookup will fail, and examining the zone will show no record at
> all for that server (even though that server has been in existence for
> years). Doing a "ipconifg /registerdns" on the missing server does make it
> show back up in DNS. But why is it dropping out in the first place?
>
> Event log on the DNS server (the server listed first in DNS settings for all
> my hosts) is showing occasional warnings of event 7062, finding a packet
> addressed to itself. Can't imagine what is doing that, I have checked and
> this DNS server doesn't have itself as a forwarder, and is on the notify list
> of the primary zone (notification is set to all servers on the NS tab, and
> this one is).
>
> So I am not sure what's going on, or what is causing it.
>
> Zone is set for "Secure only" dynamic updates, aging is set to scavenge stale
> records every 7 days (no-refresh and refresh interval) . These should be the
> defaults (we haven't changed the zone since we installed the Win2012 DCs.
>
> There is 1 wrinkle - we use SolarWinds, and their IPAM (IP Address
> Management). That software sets itself to receive zone transfers (so it can
> track DNS and DHCP), and so it is listed on the "Zone Transfers" tab, as an
> allowed server. But the "Notify" button is set to automatically notify only
> servers on the Name Servers tab.
>
> I know that there is zone transfer working from the SolarWinds server, I see
> event log entries showing zone transfer from that server.
>
> Anybody use this IPAM?
>
> I am going to try changing the notification list to be manual, and include
> the SolarWinds server.
>
>
