Junk

Ask something
Question Locked

Understanding Localhost.localdomain

0 helpful
10 replies

by dhuffine

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Ok, I've spent the last 2 days skimming through web page after web page after web page. Trying to get a better understanding of how this localhost.localdomain work.

Here's my objective>

I am trying to setup a DNS entry in my Windows 2003 Server, for my Linux OS. I've given up on trying to figure out how to join the Linux to the actual domain because I don't understand Samba and every walk through I have looked at has not been very helpful.

So I want to be able to ping lws from a windows command prompt and it return successfully.

Currently in my hosts file is:

127.0.0.1 localhost.localdomain localhost

Currently in my network file is:

NETWORKING=yes
GATEWAY= 1.1.1.250 (real ip's are hidden)
HOSTNAME=lws

I am setting up an Intranet Web server and I want the address to be http://lws.los.net/index.html

Right now all I can do is http://1.1.1.144/index.html and it comes up just fine

So how do I figure my host file, and network file, so that my FQDN comes up as lws.los.net
or com or whatever, and so that I can put in a DNS entry on my DNS server so that when I ping lws or lws.los.net(com) it will connect?

10 replies

by dhuffine

I edited the hosts file with the following information:

127.0.0.1 lws lws.los.net
1.1.1.144 lws lws.los.net
1.1.1.1 DC1 DC1.dc.com (DNS serv)
1.1.1.2 DC2 DC2.dc.com
1.1.1.100 MYPC MYPC.dc.com

I edit the Network file as such

HOSTNAME=lws.los.net

On Windows 2003 Server

I modified the A record pointing to 1.1.1.144 with the FQDN of lws.los.net

I can do a tracert on windows and it will resolve lws.los.net, I can ping 1.1.1.144, but I cannot ping lws.los.net

Any suggestions?

by cg it

127.0.0.1 is a loopback address and is for testing the local machine. you don't use it for anything else.

so assign your Linux server with an IP addresses. Use the TCP/IP protocol. if that doesn't work then try NetBIOS over TCP/IP [WINS]. you also might want to try a WINS server.

DNS is computer name [NetBIOS]name to IP address. so make an A record entry in DNS that says Linux box is IP address _________.

DNS will then resolve queries for your linux box name to the linux box IP address.

by dhuffine

Realized in the end I was over complicating it. This information helped.. Thanks!

by dhuffine

Alright so I setup the host name, yadda yadda, and put in the DNS entry in 2003. And I made sure that NetBios over TCP/IP was setup accordingly, but I have no wins server.

I have a DNS entry for 1.1.1.144 that points to lps.los.net, and I can ping 1.1.1.144, but I cannot ping lps, or lps.los.net via any computer on the network.

I can however ping the ENTIRE domain from Linux.

EDIT:

I can however do a tracert on 1.1.1.144 and it does resolve lps.los.net

Could linux be blocking FQDN pings but not IP pings?

by computech911

Are your linux boxes using your Windows2003 box as thier DNS server?

by cg it

unless it has a firewall on it that blocks UDP/TCP port 53.

so, I assume that lps is the linux box name and it resides on the los.net domain. I'll also assume that the ip address for the lps linux box is 1.1.1.144. On the W2003 Server DNS, you should have an A record that says lps = 1.1.1.144.

I'll also assume that the linux box uses the W2003 Server ip addresses as it's DNS addresses.

Another assumption is that you can ping the lps box using it's IP address, however you can not ping the lps box using its domain name.

Last assumption is that your ICMP testing is all on the LAN and not over the WAN and that you have forwarders enabled in DNS. Also that ping to los.net works.

Since your using the FQDN convention for your internal network, ICMP ping to a domain name requires DNS to resolve the domain name to an address. Without this resolution, you will time out.

Since your ping to lps.los.net doesn't work, your DNS server isn't resolving lps.los.net to 1.1.1.144 address.

you might want to put in an alias and ptr records in DNS of for your Linux box.

by dhuffine

(FYI I'm using PClinuxOS BE Server if that helps in any of this)

Orginally to ping anything on the Domain i had to enter the FQDN I wanted to be able to ping an IP by into the hosts file. But then I found the KDE Control Mondule and edited the WINS menu and chose "Use another WINS server" and put in my domain controler / DNS server's name in there after that point I was able to ping anything on the network by its FQDN or alias, but am still unable to ping my linux machine from the PC's on the domain via FQDN.

by dhuffine

You have most of those Assumptions correct.

Although i can't say 100% that the authenication to the los.net domain is working, I have the host name set specificly for lps.los.net but I don't know how to hceck that authenication is working. that was something I setup in the control pannel using Winbind or what not.

I have a PTR record for reverse lookup on the 2003 server, but im not sure how to setup an alias and ptr record or how to access that DNS stuff on the linux machine. That might be my problem there then.

by dhuffine

When I ping lps.los.net from the linux machine (which is the FQDN of the linux machine) it returns the IP address 127.0.0.1 the loopback address.

If I do a NSlookup of lps.los.net it returns this informaton:

Server: 1.1.1.8 (dns / domain controller)
Address: 1.1.1.8#53

** server can't find lps.los.net: NXDOMAIN

But if I nslookup vis IP address it returns:

Server: 1.1.1.8 (dns / domain controller)
Address: 1.1.1.8#53

144.1.1.1.in-addr.arpa name = lps.los.net

Also it wasnt went i entered the WINS stuff that I could start pinging the network, I am using something called Webmin 1.350 and it was when I setup the DNS server under "other DNS Servers" that I was able to start pinging the whole network.

This discussion is closed to new replies.