General discussion

Locked

Loop back address and DNS

By luv2bike2 ·
Our parent company just had a server installed and they do not have an IT person onsite. A consultant was hired to install the server and thats it. I have been asked to monitor the server. I went into TCP/IP settings and notice that the DNS server was set up with the IP Address as 127.0.0.1. I know that that address is a loop back address and I have never ever seen it being used as a DNS address. Could having the loop back address set as the DNS IP address be ONE of the reason why the server is running slow? Can one use the loop Back address as the primary DNS? this server is acting as the Gateway, DNS, email server, CA etrust for virus protection, etc. its all on this one server. It is running Windows 2003 SP1, on a 3 ghz processor with 3 gigs of RAM.
Thank you!

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to Loop back address and DNS

can one use the loop back address as the primary DNS IP address. In an Active Directory Environment, no. in any environment? no.

would it be the reason the server is running slow? maybe

Collapse -

by CG IT In reply to

loopback address is used for TCP/IP diagnostics.

Collapse -

by CG IT In reply to

if you want to know the function of the loop back address do a google search. heres a link to The TCP/IP Guide on IP addressing which includes a brief description of the function of the loop back address

http://tcpipguide.com/free/t_IPReservedPrivateandLoopbackAddresses.htm

Collapse -

by lowlands In reply to Loop back address and DNS

I don't completely agree with CG. 127.0.0.1 (or loopback) just refers to localhost. So basicly you TCP/IP properties tell the server to use itself as the DNS server. So yeah, it can be done. I am however not sure if it would be a recommended action. You can change it on the fly the the servers "normal" IP address and see if that makes things speed upa little.

Collapse -

by luv2bike2 In reply to Loop back address and DNS

I looked at the DNS in Active directory and it has an private ip address of 192.168.1.50. Should the TCP/IP settings for DNS be set to that IP address and not the LoopBack address?

Collapse -

by lowlands In reply to Loop back address and DNS

Just to be sure (DNS could be wrong) open a command prompt and type ipconfig. Use that IP as the DNS server in your TCP/IP settings window.

Collapse -

by lowlands In reply to

And like I said. Even though it will definately not hurt to do this, I don't think it will resolve the slowness issues.

Collapse -

by luv2bike2 In reply to

your answers are not unacceptable... they are helpful.. Thanks for the input.

I did do an IPCONFIG and the DNS was set to the loop back address. In AD though, the DNS has a private address. I changed the DNS address in the TCP/IP configuration and it did not speed up the server. Any suggestions as to what could be causing the slowness?

Collapse -

by luv2bike2 In reply to Loop back address and DNS

This question was closed by the author

Back to Networks Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums