S
slemay
This one has really stumped me and I've finally decided to post and see if anyone else sees this happening. We had very few Windows 2012 server deployments, but now that we're deploying more and more 2016 servers, we're noticing that after a few days, weeks, months (random) that the DNS setting for the NIC card changes all by itself.
Typically, we have environments where that are two domain controllers (and thus two DNS servers) - so we'll always set the DNS to point to the other server first and then 127.0.0.1 second. But we'll come back a month later and check - and we'll typically see the first DNS entry is gone and the 127.0.0.1 is now the only entry remaining.
As I'm the only tech with authorization to make the change and it's occuring on multiple sites - I'm assuming Windows is doing something... I'm "GUESSING" that perhaps the other DNS server becomes unavilable for a brief time (reboot, maintenance???) and the first server sees it as an invalid DNS entry and deletes it.
I hate this action - if my theory is correct... is there a way to disable this from occuring? Am I speculating correctly here? I haven't been able to prove it (I reboot a server and watch - and nothing happens - but I'll come back a month later, and ta-da... it's done it again and I put it back). I find nothing in the logs either.
Anyone have any ideas? Thoughts? Suggestions on how to track this?
Thanks,
Shawn
Continue reading...
Typically, we have environments where that are two domain controllers (and thus two DNS servers) - so we'll always set the DNS to point to the other server first and then 127.0.0.1 second. But we'll come back a month later and check - and we'll typically see the first DNS entry is gone and the 127.0.0.1 is now the only entry remaining.
As I'm the only tech with authorization to make the change and it's occuring on multiple sites - I'm assuming Windows is doing something... I'm "GUESSING" that perhaps the other DNS server becomes unavilable for a brief time (reboot, maintenance???) and the first server sees it as an invalid DNS entry and deletes it.
I hate this action - if my theory is correct... is there a way to disable this from occuring? Am I speculating correctly here? I haven't been able to prove it (I reboot a server and watch - and nothing happens - but I'll come back a month later, and ta-da... it's done it again and I put it back). I find nothing in the logs either.
Anyone have any ideas? Thoughts? Suggestions on how to track this?
Thanks,
Shawn
Continue reading...