Solved

Debian - Inside local network

Posted on 2004-09-22
3
166 Views
Last Modified: 2010-03-18
I just installed debian and apache and everything is up and running on 192.168.1.102...  However, when i type my domain name inside my local network, for some reason, it keeps trying to hit 192.168.1.103, instead of 102...   Even when i try to ping my domain name inside my local network, it tries to hit .103.  I have no computers on my network assigned with an IP of .103.   When i am outside my network, such as work or some other place, i can get to my website just fine...  When i do type in .102 inside my local network in IE, it does take me to my website/server...   Anyone got any clue?
0
Comment
Question by:ivirdi
  • 2
3 Comments
 
LVL 40

Accepted Solution

by:
jlevie earned 500 total points
ID: 12130045
What's in the hosts file on your debian box?

When one hasn't made hosts file records for an externally visble domain and tries to got to that site via name from inside of a NAT'ing firewall one finds that they "can't get there from here". And that's because the FQDN, using DNS, resolves to the outside IP. Most firewalls won't allow an inside machine to "go out and come back in" so the attempt times out.  I've never heard of a firewall changing the ouside IP to some other, so I suspect that you might have a hosts file record that equates the FQDN for the site to the wrong IP.

The final solution here, once we figure out what's happening, is to create a hosts file record on the Debian box that equates the FQDN to the correct inside IP.
0
 

Author Comment

by:ivirdi
ID: 12139698
Here's how my etc/hosts file looks:
127.0.0.1       localhost
192.168.1.102   www.website.com  doom

# The following lines are desirable for IPv6 capable hosts
# (added automatically by netbase upgrade)

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts


This is how my resolv.conf files looks:
search www.website.com
nameserver 192.168.1.1
0
 
LVL 40

Expert Comment

by:jlevie
ID: 12139752
In your hosts file "192.168.1.102   www.website.com  doom" should really be "192.168.1.102   www.website.com  www doom". And in resolv.conf you should have "search website.com".

If you do 'host www.website.com' or 'nslookup www.website.com' what is the result?
0

Featured Post

Master Your Team's Linux and Cloud Stack!

The average business loses $13.5M per year to ineffective training (per 1,000 employees). Keep ahead of the competition and combine in-person quality with online cost and flexibility by training with Linux Academy.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
linux dns for internal resolve 2 59
Cant reach dockers repository (pull command) 11 92
LDAP setup? 9 87
App holding yum lock unable to update my rpm package 1 72
I have seen several blogs and forum entries elsewhere state that because NTFS volumes do not support linux ownership or permissions, they cannot be used for anonymous ftp upload through the vsftpd program.   IT can be done and here's how to get i…
Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question