All internally built and maintained. AD integrated zones. The external is part
of a separate DMZ domain. I hadn’t thought about something scripted at that
level but I’ll double check. Doubtful, but you never know what may have been
created as part of the Skype install. That’s our primary suspect at this
point, but as MBS said, since we have a work around it’s more being able to
explain what happened than anything else.
It did occur to me that perhaps the change to the register connection checkbox
might require a service restart, etc.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of Micheal Espinola Jr
Sent: Tuesday, July 11, 2017 11:22 AM
To: [email protected]
Subject: Re: [NTSysADM] Odd DSN behavior
Are the DNS servers known, aka something you or your staff would use? Any
possibility that there is a script using netsh, or similar, at play?
--
Espi
On Tue, Jul 11, 2017 at 6:40 AM, Melvin Backus
<[email protected]<mailto:[email protected]>> wrote:
We’ve run across a very strange DNS situation that we can’t explain. We have
suspicions and a temporary fix but I’m hoping someone on the list has seen it
already and give us some pointers.
Recently stood up 2 new Skype for Business servers to replace the existing Lync
2010 servers. One internal and one edge server in each case. We’ve successfully
migrated the topology and everything is running of the new servers. But now
for the weird part. Every day, the internal DNS entry for the edge server gets
changed. The static IPv4 entry for the internal interface (LAN facing) gets
removed and there are new entries for the external interface IPs (public
facing), both IPv4 and IPv6. The weird part is that the new entries are static
as well, no timestamps.
After much digging and churning we finally disabled the DNS Client service on
that server and it didn’t happen last night, but I’m trying to figure out how
it was happening even with the DNS Client running. DNS on that box points to a
DNS server on the public side, not the internal servers. DDNS updates should
create a dynamic / timestamped entry. I’ve never seen a static entry created
any way other than via manual intervention.
Any one care to solve the puzzle?
--------------------
Service Desk | 404-497-1599<tel:(404)%20497-1599> |
https://servicedesk.byers.com<https://servicedesk.byers.com/>
Melvin Backus | Sr. Systems Engineer | Byers Engineering Company |
404.497.1565<tel:(404)%20497-1565>
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
