127.0.0.1 and when it should be used.

Hi,

Whilst checking some network settings on a server configured as AD and DNS servers I noticed that the setup wizard for AD had set the IP details for the DNS server as 127.0.0.1 (loop back adapter i believe) which I hadn't seen before, at least as far as the wizard was concerned.

Everything seems to work ok (well apart from the other posts i've out up!!!). Has anyone come across this before and if so does it make any difference using 127.0.0.1 instead of its actual IP address?

Regards
Maximus

I have never seen this before. I would use the actual IP address for DNS setup.

Quote:

---

Originally Posted by Maximus

Hi,

Whilst checking some network settings on a server configured as AD and DNS servers I noticed that the setup wizard for AD had set the IP details for the DNS server as 127.0.0.1 (loop back adapter i believe) which I hadn't seen before, at least as far as the wizard was concerned.

Everything seems to work ok (well apart from the other posts i've out up!!!). Has anyone come across this before and if so does it make any difference using 127.0.0.1 instead of its actual IP address?

Regards
Maximus

---

It's fine, and as you noticed is set by the MS wizard. If you have a second DC you can always add the ip of that as the secondary if you want.

127.0.0.1 is not specifically the loopback adapter (although it can be) - it just means "me"

I suspect it saves a few CPU cycles for AD - instead of having to go out on the network to say "where is 10.0.0.1" or whatever, it just immediately connects to localhost but it's no big deal.

Using 127.0.0.1 doesn't work on W2k DCs. Other than that, it's fine.

One thing it does seem to cause is constant logging of the following of event ID 3019 MrxSmb.

I changed it to the ip addresses of the server and the warnings stopped.

Any ideas?

Regards
Maximus

That error is generated because the loop back interface does not have a speed.

Error Message: The Redirector Failed to Determine the Connection Type