Hey

On my System I can do pretty much anything in regards to the Inernet...
I can PING any IP on the LAN with success.
I can PING yahoo.com with success.
I can PING my Router with success.
I can NOT PING my Routers Static IP
I can NOT PING my Domain Name.

From outside my System(remotely) I can PING My Static IP (The Router) and I can PING my Domain with Success.

Also, from outside, I can SSH to the Domain and the IP and get inside my Linux.

I am beginning to suspect mabe my Router has a setting restricting this?

I ask because I get sound results from Slackware as I do Lubuntu.

CenturyLink C2100T. It is a Bonded vDSL Router.

I have done my Google searches and verified several settings... Waiting on some responses on a forum with the Router.

Okay, some networking essentials...
Consider this
they can ping each other...
watch...
192.168.1.*
see the pattern? The two hosts are in the same subnet...
Now, consider this
They...will not be able to ping each other...they exist in different networks, no matter if they are connected with a wire, you need a bridge to "connect" them...
I bet...your router's static IP is on a different network...
You may not be able to ping your domain for several reasons. Either the server is set up as such that it ignores a ping, or...your domein is co-hosted on the same "box" with other domains...
Hope this helps somewhat...
Melissa

2 members found this post helpful.

I understand what you mean.. But

My Linux IP - 192.168.0.69 and my Gateway Router LAN is 192.168.0.1. My Static IP is 1.1.1.1 (let's say).
My Linux can Ping yahoo.com and Yahoo's IP (different network as you mention) so why am I not getting a Ping Result when I Ping my Domain (hosted out 3rd Party (Dotster)) or my Static IP.

It is not even the Ping I care about; It is when I am setting up my Postfix that I can 'telnet localhost 25' but when I 'telnet <domain.org> 25' it times out. Even when I 'telnet <static ip> 25' it tims out.

It seems like it will send out but not back in.. Like, on itself.

This is normal for most routers, unless they have a feature to make the external ip available on the internal interface (name of option varies by router (maybe "loopack" or "external passthrough").
You can run a local DNS to properly resolve your domain to the correct LOCAL ip.

3 members found this post helpful.

Wait wait wait...what I read worries me...you HAVE to stay inside the class network you chose...
I noticed the 1.1.1.1 ... that does not really fall inside a LAN IP range
Maybe you've been pinging someone all the way accross the globe and not know it LOL
Melissa

This is the right answer... (to be more explicit than voting)...

(And yes subnet etc, but it IS NOT your problem in this case, even if your sample IP is bad that's another point).

1 members found this post helpful.

The 1.1.1.1 is obviously not my Static.

My whole misunderstanding is; forget "I" own the static IP or DOMAIN... I can't ping "it" but I can conveniently ping any other pingable address except the 1 that happens to be mine. Just not sure if it's my Router blocking incoming ping (as I leave my network only to come back and get a response) or if I am being blocked outgoing.
It's really not hindering any issues as I could care less if I could ping.

This all stemmed from my setting up Postfix and I can 'telnet localhost 25' but I can't telnet my ip or domain so clearly(?) some sort of loopback type setting (Linux (both distros I use)) or my router is not routing correctly.

I have assumed that you have a public DNS record that resolves your domain to the public ip of your router.

It is completely normal that you cannot communicate with that external IP from the LAN attached to the internal interface of said router.

Some routers have a feature to work around this limitation, if yours doesn't then you have the options in my previous post.

I'm not sure that this will help but you ought to be able to ping anything on your LAN from anywhere on your LAN, including the gateway and the modem.

I have HughesNet (satellite), the modem is 192.168.0.1, the router is 192.168.1.1 (it's a Linksys with a 4-port switch). The systems on the LAN are all 192.168.1.something, including an H-P Ethernet printer and an occasional H-P Ethernet plotter. Everybody "knows" everybody else and I connect to the systems with SSH (got one keyboard and one display) and everybody can ping each other and themselves and everything is fixed-IP.

I can ping the modem from any system, I can ping the router from any system, I can ping the outside world from any system but there is no way in from the outside (HughesNet won't let you do a web site). I can also SSH to the system I'm on at any time (which is kind of useless). Ping the gateway, ping the modem, ping anything connected.

I've always done fixed-IP with system name and address entries in /etc/hosts (every system has the same /etc/hosts file):
Those public servers are listed so that there's no DNS lag (TCP/IP looks at /etc/hosts first) and the printer and plotter share the same name and address because only one will be connected at a time.

I use external DNS servers (can't see any reason to have bind running ), right now /etc/resolv.conf looks like this:
Everything works.

Occasionally a second router is connected to the Linksys that provides wireless service to guests with Kindles and pads, pods or whatever the heck those things are including my laptop (which is normally connected via Ethernet); it's pita on the list. Every so often I plug in a Linksys switch when I need additional connections for some reason or other.

It comes up on boot with Ethernet or I can connect wireless with WICD after boot -- nothing interferes with anything else and, well, everything communicates with everything else in the building.

Don't know if this sort of thing would fit your needs but it works for me (and has for a couple of decades).

Hope this helps some.

Absolutely, and I appreciate that. I will look into this.

BAcidEvil, this is normal behavior. See this post on serverfault for some background information on what is happening.

To fix your problem, you need to have a look at your router's settings. You'll want to look for something like NAT Reflection, NAT loopback, NAT hairpinning, or possibly some other name (googling those terms with your router information might provide you some insight on the option). Once enabled, you should be able to use your domain within your internal network.

Another option is to just edit your /etc/hosts file to prevent the DNS from even being used.

3 members found this post helpful.

Quite interesting.

Would this by any chance coincide with my Postfix not sending outside of my localhost because it simply can't resolve my ip/domain or would this not have anything to do with that?

I will mention this; from my Windows machine on the same LAN I can indeed ping my domain and IP so I would assume that this would have something to do within Linux, such as /etc/hosts, as you mention.

If it is trying to contact an external IP that is assigned to your modem/router (or the domain associated with it), it absolutely could. If it is just using internal IPs or the loopback, it is likely unrelated.

Yeah from outside (remotely(my iphone)) I can receive emails from anywhere but only send emails to localhost (or the domain, but only back on itself (if i have 2 accounts on my domain and emailing 1 to another but using my @domain.org)) but when I send OUTSIDE of my Box to [any] address and not just mine I get a relay access denied.. I am wondering if this may be part of it. Although, I would think not because my other email is @yahoo.com and I can PING yahoo.com so that may not be related at all.

No, that is a separate misconfiguration of your postfix setup.

Without wanting to sound rude, you seem to be conflating multiple issues, misunderstanding basic networking principles and confusing anecdote with evidence (of which you have supplied precious little).

If you want your problems solved you will need to apply a bit more effort (maybe see the "how to get help with your problem" sticky post).

If you just want to chat, then good luck and see you later.