Talked to Dell support.
Was told the problem is a new interface that allows the iDRAC to be accessed through an USB port.
I decided not to use the new interface that allows the iDRAC to be accessed through an USB port. I went into Network & Internet Settings, Change adapter options, selected the Remote NDIS Compatible Device and disable it.
The disable did not remove all messages like Warning: Delegation of DNS server DC2.domain. is broken on IP:fde1:53ba:e9a0:de11:906e:5a09:5d53:ed19
Selected iDrac Settings, Management USB Settings, Disable USB Managment Port
What causes Summary of DNS Basc Warn?
Ran Dcdiag /v /c /d /e /s:DC3 >c:\dcdiag.log The DNS tests appear to pass but there is a warning.
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
DC3 PASS WARN PASS PASS PASS PASS n/a
How do I correct the warning?
-
techcoor 1,251 Reputation points
2021-05-24T22:13:21.94+00:00
11 additional answers
Sort by: Most helpful
-
techcoor 1,251 Reputation points
2021-05-14T02:46:26.907+00:00 Ran dcdiag /test:dns /v /s:DC3 /DnsBasic /f:dcdiagdnst.txt
This is more telling.
127.0.0.1 (DC3) [Valid].
dcdiag /test:dns /v /s:<DCName> /DnsBasic /f:dcdiagreport.txt
Therefore, DNS is ignoring the static ip address on NIC 2 and insisting going to NIC 1 which is not configured. -
techcoor 1,251 Reputation points
2021-05-14T03:33:23.17+00:00 To DSPatrick
I can not see any of your replies.
-
Candy Luo 12,656 Reputation points Microsoft Vendor
2021-05-14T06:55:28.177+00:00 Hi,
Therefore, DNS is ignoring the static ip address on NIC 2 and insisting going to NIC 1 which is not configured.
Did you configure two NIC on your DC/DNS server? If yes, please disable NIC 1(that you don't need to use) and then check DNS test results.
By the way, you can run Best Practices Analyzer to scan DNS role.
For more details about Best Practices Analyzer, you can refer to the following link:
Run Best Practices Analyzer Scans and Manage Scan Results
Best Regards,
Candy--------------------------------------------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
-
techcoor 1,251 Reputation points
2021-05-17T02:49:53.843+00:00 I can not see your last post on this page. The post did arrive by email.
This is where I am at:
- Therefore, DNS is ignoring the static ip address on NIC 2 and insisting going to NIC 1 which is not configured.
Did you configure two NIC on your DC/DNS server? If yes, please disable NIC 1(that you don't need to use) and then check DNS test results.
NIC 1 was disabled already.
My statement” insisting going to NIC 1” is probably inaccurate. I was trying to guess at where the 127.0.0.1 is coming from.
TEST: Basic (Basc)
The OS Microsoft Windows Server 2019 Standard (Service Pack level: 0.0) is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000001] Broadcom NetXtreme Gigabit Ethernet:
MAC address is 2C:EA:7F:99:AD:9D
IP Address is static
IP address: 192.168.1.220, fe80::e9b6:2818:92c2:cbba
DNS servers:
192.168.1.222 (DC1) [Valid]
192.168.1.214 (DC2) [Valid]
127.0.0.1 (DC3) [Valid]
Adapter [00000003] Remote NDIS Compatible Device:
MAC address is 2C:EA:7F:99:AD:99
Warning IP address is dynamic (can be a misconfiguration)
Warning: Adapter 2C:EA:7F:99:AD:99 has dynamic IP address (can be a misconfiguration)
IP address: 169.254.1.2, fe80::9d97:9275:531a:deb, fde1:53ba:e9a0:de11:9d97:9275:531a:deb
DNS servers:
127.0.0.1 (DC3) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not foundBut I see no 127.0.0.1 if I run the same command on DC1.
TEST: Basic (Basc)
The OS Microsoft Windows Server 2019 Standard (Service Pack level: 0.0) is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000003] Broadcom NetXtreme Gigabit Ethernet:
MAC address is D0:94:66:5F:9D:6A
IP Address is static
IP address: 192.168.1.222, fe80::c4ff:da78:48b3:4c18
DNS servers:
192.168.1.214 (DC2) [Valid]
192.168.1.220 (DC3) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found- The DFS Replication service is stopping communication with partner DC3 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information: Error: 1723 (The RPC server is too busy to complete this operation.) Connection ID: 3102F341-A9F9-469F-ACED-D8D4D6B4AF9B Replication Group ID: 678AF27B-4AC7-459A-84CD-C1C04A6BEB1F An error event occurred. EventID: 0xC0001390 Time Generated: 05/12/2021 19:34:07 Event String: The DFS Replication service failed to communicate with partner DC3 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
The DFS Replication service is stopping communication with partner DC1 for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 9036 (Paused for backup or restore) Connection ID: 92888B85-F6BD-4B62-BEB1-4EA4EA0046DD Replication Group ID: 678AF27B-4AC7-459A-84CD-C1C04A6BEB1F
Checking Windows Backup and it is not running a backup. Checked Retrospect and it is not running backup. Exit Retrospect and rerun test. Problem still listed. Removed Windows Server backup role and reran. Problem is still listed. Restarted Retrospect and added back Window Server backup role.
- By the way, you can run Best Practices Analyzer to scan DNS role.
For more details about Best Practices Analyzer, you can refer to the following link:
Run Best Practices Analyzer Manage Scan Results
I went to File and Storage Services, Servers, Best Practices Analyzer and selected Start BPA Scan.
It ended up generating 99 total comments. Apparently the problems are not listed and one has to click each item. It did complain about Warning Short file name creation should be disabled
How important is that registry edit? There does not seem to be anything for Summary of DNS problem. - Therefore, DNS is ignoring the static ip address on NIC 2 and insisting going to NIC 1 which is not configured.