DNS - Listen On IP

[gblue]

After both a MS Server 2016 update and a restart, I found the admin portal not working. I checked the log file and found port 53 was blocked. I checked the cfg properties and indeed the listen_IP port is correct. I then looked at the DNS server properties for the listen to port as we already have a primary DNS server on this DC. I attached the image below of what I found after MS update and restart of the DC. I only want to listen on the primary DNS, 10.1.1.6. I installed NXF as an alternative DNS, 10.1.1.4. Therefore, I manually selected, Only the following IPs, and check 10.1.1.6 only. Though as stated, following MS update and restart, DNS properties reverted back to listen to all IP addresses. End result, NXF admin portal was not working. This is problematic, if every time I install an update and/or restart the DC, I will have to verify this DNS property. Anyone else seen this issue? My guess, this is not an NXF issue but perhaps an MS issue. I don't know if an MS update caused this or not. Any comments?

[gblue]

Reply to my own question, and what I learned from outside help:
1. Create a .bat file to run at via Task Scheduler to run 'after' DNS Server has started.
Run this command from a .bat file: dnscmd "server name" /resetlistenaddresses "IP Address"
This command will set the listen to address as specified.
2. To allow extra time for DNS Server to start and Task to run, need to set, NXF Service to run 'delayed automatic'. (See Services, NXFilter)
This will allow extra time and ensure the DNS Server and Listen to DNS is set before NXF tries to run.

Testing of reboot/restart of server:

16:21:10 - restart of server
16:21:53 - DNS Started
16:22:23 - Task Event Started (this is with 30 secs delay after DNS started)
16:23:41 - NXF (nxwrapper) started with loads the startup.bat file for NXF to start
16:23:53 - NXF Started (ready)

Hope this might be helpful to others. Cheers.