I would at least restart the DNS client service on them if you can't reboot
them, but I've recently (just this morning in fact) seen some weird DNS related
stuff cleared up by a reboot. In particular, a DC that could find an
authentication server. Not much fun with a server that's half way across the
country.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Michael Leone
Sent: Monday, June 15, 2015 12:45 PM
To: [email protected]
Subject: Re: [NTSysADM] DNS errors after installing Win2012 R2 DCs
On Mon, Jun 15, 2015 at 12:28 PM, Susan Bradley <[email protected]> wrote:
> I haven't met an HP server that doesn't natively ship with Broadcom
> nics even though they are called HP network cards.
>
> You sure those suckers aren't evil Broadcoms?
Dunno, I didn't set up the hardware, one of the other guys did, I just
dcpromo'ed it. i suppose they could be ... one of them is a blade, using their
"FlexFabric 10G 2 port 534FLB" adapter.
I rolled out the VMs.
All the servers that dropped out of DNS all point to DC#5 (VM) and
DC#6 (HP physical, the blade mentioned above).
As a specific example:
DWB019 has a static IP address, and the above 2 servers as it's DNS settings.
No manually created A records created in DNS, we just let it register. Up until
this morning, all was well.
(last Thu, we changed the DNS settings to point to #5 and #6, it's current DNS
settings (both Win2012 R2), from the older DC#1 and #3 - a physical and virtual
Win2008 R2. Did not reboot, flush DNS, etc - we just changed the DNS settings
on the NIC)
DC #5 and DC #6 have been DCs for the last 2-3 weeks, and have been DNS
servers. We just hadn't pointed any clients directly at them, to use as their
DNS settings on their NICs.
This morning, there is no record of DWB19 in DNS at all. I go to DWB019, open
an elevated command prompt, do "ipcofig /registerdns", and then there is a
record in DNS, timestamped this morning at 10AM.
So why did it drop out of DNS over the weeked? And why didn't it renew itself,
especially if a manual register works just fine?
And how do I stop it from doing that again?
>
> MS wants feedback on patching: http://tinyurl.com/patchingsurvey On
> 6/15/2015 9:18 AM, Michael Leone wrote:
>>
>> On Mon, Jun 15, 2015 at 11:59 AM, Susan Bradley
>> <[email protected]>
>> wrote:
>>>
>>> Virtual or real metal?
>>
>> Both. 2 virtual, 4 physical. :-) The "main" DNS server, the ones
>> almost all the servers point at (and therefore should be registering
>> with), is virtual. The physicals are 2 Dell and 2 HP boxes.
>>
>>> Nics are Intel or Evil Broadcoms (TM)?
>>
>> The virtuals are all vmxnet3, the Dell physicals have teamed Broadcom
>> NICs and the HP has their NIC teamed.
>>
>>> (if virtual and if Evil Broadcoms (TM) ensure you have disabled
>>> rss/toe and VMQ on the parent)
>>
>> The parent. You mean on the vmhost? Ours is VMware 5.5 U2, running on
>> HP hardware, so they aren't using Broadcom NICs..
>>
>>
>>
>
>
>
