Avatar of IT Guy
IT Guy
Flag for United States of America asked on

Should DNS server address of "127.0.0.1" be used when specifying same server as primary DNS server?

When adding the DNS server address of a server (and the server itself is a DNS server), is it preferable to add the IP address as "127.0.0.1" or should the server's actual IP address of 192.168.10.20 be used?

I have seen both types of IP addresses used and am wondering if there is an advantage of using one over the other or if there are any problems with using one IP address format over the other one.

This is in a Server 2016 environment.
Windows OSDNSMicrosoft Server OSTCP/IPWindows 10

Avatar of undefined
Last Comment
Qlemo

8/22/2022 - Mon
M A

127.0.0.1 is better.
Your name resolution is happening within the server itself.
Make sense?

Do not forget to install additional domain controller and add that server IP as additional DNS in NIC.

Cheers
yo_bee

The transaction is so quick it really does not matter.
ASKER CERTIFIED SOLUTION
Greg Stringer

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
SOLUTION
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security Officer

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Qlemo

The MS article cited above is recommending not to use either address first. The first DNS server should be some other device. For the effect described, it doesn't matter if you have used a real or loopback IP.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
SOLUTION
M A

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security Officer

Just an FYI, that document is 7 years old and it specifically talks about the LOOPBACK address. Nowhere does it say not to use the server's own IP address.  

You should apply the information in this topic only to computers that have had the DNS Microsoft Baseline Configuration Analyzer or DNS Best Practices Analyzer run against them and are experiencing the issue addressed by this topic.

I have worked with many Microsoft engineers in the past that say to remove the loopback address and use the actual IP address.  If you use an SBS server, for example, you must use your own address. Again the document is only discussing the loopback address and NOT the actual IP address.
Qlemo

Steve, did you understand the reaon why? Because the DNS service on the own machine might not be ready at the stage when the server tries to register services. For that, it doesn't matter if loopback or real IP at all.