Hi,
Thanks for posting here.
If you only have a single Domain Controller/DNS server, you can safely ignore this issue. If you have more than one, you should be setting the primary DNS server to the IP of the other Domain Controller and setting the secondary DNS server to the loopback interface and vice versa on the other DC.
You get this error with all of your configurations, because the IP of DNS server is the local interface, so it's effectively the same as 127.0.0.1 as far as DNS and the BPA are concerned.
This is the best practice so that a DNS server isn't reliant on itself for name resolution, which would affect replication in a multi-DC environment. If you only have a single Domain Controller, you'll continue to get this error because, well, only having 1 DC isn't best practice.
You can refer to the following article on IP settings:
https://social.technet.microsoft.com/wiki/contents/articles/18513.active-directory-replication-issues-basic-troubleshooting-steps-single-ad-domain-in-a-single-ad-forest.aspx
Hope my answer will help you. Thanks!
---Please Accept as answer if the reply is helpful---
Best Regards,
Sunny