You are trying to ping an email address. You can't do that. Needs to be:
ping ns2.normanfournier.com I can ping it just fine. However, the IP address you are saying it has and what it is is different. You can adjust your hosts file to point correctly if needed. On Fri, Jun 14, 2013 at 11:11 AM, Norman Fournier <nor...@normanfournier.com > wrote: > On 2013-06-14, at 8:40 AM, David Guerra wrote: > > What you're saying is that you can't connect to any of the servers behind > the router. > So NS1 is not able to communicate at all (ping or anything) to NS2. > > This seems to be a routing issue that you need to resolve at the router > level. > > > > On Fri, Jun 14, 2013 at 1:44 AM, Norman Fournier < > nor...@normanfournier.com> wrote: > >> On 2013-06-13, at 11:28 PM, David Guerra wrote: >> >> Your network config isn't anywhere close to normal. It makes no logical >> sense. >> >> Aside from that if you replaced a network card then maybe your MAC >> address changed and you need to reconfigure the router. >> >> On Thursday, June 13, 2013, Norman Fournier wrote: >> >>> >>> On 2013-06-13, at 4:13 PM, Norman Fournier wrote: >>> >>> Hello, >>> >>> I have setup two webservers on my network, one connected directly to the >>> ISP with an ethernet card installed to bring it to the router where, it was >>> give an internal ip address and ports opened for ftp, smtp and pop. It is >>> ns1. ns2 is behind the router and handles http, dns and ssh. Mail is >>> currently being properly delivered although my smtp server going out is no >>> longer working for obvious reasons. >>> >>> I can't ping ns1 from ns2. apachectl say my configuration is correct. >>> The only change I made that I can see is the ethernet card in ns1 died. How >>> would this impact my DNS? >>> >>> None of the domains on ns2 are available on the web although the >>> websites on ns1 are. >>> >>> The attached diagram shows before and after. Any help would be greatly >>> appreciated. >>> >>> Norman >>> >>> http://www.normanfournier.com/nf-network-diagram-v9.jpg >>> >>> >>> It appears that the apache webserver is already loaded and that might be >>> the problem, although it is not serving any pages. The following is my >>> terminal output. >>> >>> ns2:~ norman$ apachectl -t >>> Syntax OK >>> ns2:~ norman$ apachectl restart >>> launchctl: >>> CFURLWriteDataAndPropertiesToResource(/System/Library/LaunchDaemons/org.apache.httpd.plist) >>> failed: -10 >>> ns2:~ norman$ apachectl start >>> launchctl: >>> CFURLWriteDataAndPropertiesToResource(/System/Library/LaunchDaemons/org.apache.httpd.plist) >>> failed: -10 >>> org.apache.httpd: Already loaded >>> ns2:~ norman$ >>> >>> Norman >>> >> >> Hello, >> >> I didn't replace a card, I lost a card. The old router was replaced with >> a new router and reconfigured and ports opened as per the diagram in the >> link. Aside from that, how should the network be logically setup? It looked >> logical enough to me in the old configuration. >> >> Norman >> > > ns1.normanfournier.com can't ping ns2.normanfournier.com, but it can ping > 192.70.190.126, which is the ip address of ns2. > > [mail:~] root# ping n...@normanfournier.com > ping: cannot resolve n...@normanfournier.com: Unknown host > [mail:~] root# ping 184.70.190.126 > PING 184.70.190.126 (184.70.190.126): 56 data bytes > 64 bytes from 184.70.190.126: icmp_seq=0 ttl=63 time=8.892 ms > 64 bytes from 184.70.190.126: icmp_seq=1 ttl=63 time=8.367 ms > 64 bytes from 184.70.190.126: icmp_seq=2 ttl=63 time=8.492 ms > 64 bytes from 184.70.190.126: icmp_seq=3 ttl=63 time=8.265 ms > 64 bytes from 184.70.190.126: icmp_seq=4 ttl=63 time=7.874 ms > 64 bytes from 184.70.190.126: icmp_seq=5 ttl=63 time=9.619 ms > ^C > --- 184.70.190.126 ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max/stddev = 7.874/8.585/9.619/0.552 ms > > Norman > -- Take Care, David Guerra http://frustratedtech.com/
