Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Cannot ping external IP/web address from LAN, yet can access site fine

Posted on 2009-03-31
6
Medium Priority
?
441 Views
Last Modified: 2012-08-13
Embarking on a trip down the rabbit hole that started with Wordpress but is ending up with crazy DNS issues - hoping someone can help! My LAN network is set up with a Windows 2003 box which hosts DNS, a 10.5.6 Mac server which hosts our website, DHCP, and other various things, all behind a Netgear FVX538 firewall box.

The Mac server hosts our Wordpress website - recently I had been trying to start hosting a podcast for the Wordpress blog. Wordpress normally supports auto enclosures of media files, but that wasn't working, which I thought was strange. After much searching and testing, I realized that something was amiss with DNS that was most likely causing the issue.

I can ACCESS my website from the LAN (both on the server it's being hosted from and other computers in the LAN) but PINGING either the external IP or the domain name doesn't work. It pings for one entry, spits back the IP address, then stops with no other error message or notification of any kind. I can ping other external sites just fine, and can ping internal IP addresses just fine as well.

I'm not sure if this is a DNS problem, although it seems safe to say that it is. And because I've noticed no other issues, I'm not really sure where to begin in figure out what the problem is. It seems that there's some issue going on with internal DNS, so if anyone has advice of what I should look for, please let me know!
0
Comment
Question by:topher1078
  • 3
  • 3
6 Comments
 
LVL 71

Expert Comment

by:Chris Dent
ID: 24030512

If you're getting the correct IP Address back in response to a request for a name then DNS is done and out of the picture.

However, your server is hosted inside your network in this scenario?

That is you have something like this:

Internet   -----   Router   -----   Switch   -----   Clients
                                                     |
                                                Server

And you use NAT to get a public IP address from outside your network to your Server?

If so, then  no, clients will not be able to access the server using the public IP (and therefore also won't be able to using the public name which presumably resolves to that IP). If that is true, do you have a DNS server inside your network as well?

Chris
0
 

Author Comment

by:topher1078
ID: 24030635
That diagram is basically what we have. I have the router/firewall box set up with the ISPs DNS server, then an internal DNS server hosted on the Windows 2003 box. And yes, my firewall is using NAT to get outside the server.
0
 
LVL 71

Accepted Solution

by:
Chris Dent earned 2000 total points
ID: 24030743

Okay, so clients inside won't be able to access on the public IP because it just gets horribly confused trying to route the requests.

The traditional answer is to create a zone on the internal DNS server that will provide clients inside the network with a private IP address for the domain name in question. This only works if all your internal clients use that internal DNS server.

I've blogged about this in the past, so I hope you'll forgive me pasting the link rather than rewriting my instructions for it :)

http://www.highorbit.co.uk/?p=459

Chris
0
New Tabletop Appliances Blow Competitors Away!

WatchGuard’s new T15, T35 and T55 tabletop UTMs provide the highest-performing security inspection in their class, allowing users at small offices, home offices and distributed enterprises to experience blazing-fast Internet speeds without sacrificing enterprise-grade security.

 

Author Comment

by:topher1078
ID: 24030863
I will try those instructions - thanks - but I may have figured out something else. Tried switching out the Netgear firewall to our old Symantex VPN/100 and lo and behold, everything started working again - enclosures, pinging, the whole nine yards. So I guess when I was setting up the Netgear I missed a setting, any thoughts as to what that might be, or should I do your DNS suggestions first (with the Netgear) and see if that works first?
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 24036842

Some routers will handle it, some won't. It also depends if your server is set up in a DMZ.

The most important part is that it works from the public networks, it is possible to work around any issues internally.

Chris
0
 

Author Comment

by:topher1078
ID: 24040592
Followed your DNS instructions and everything now works great, with the new router. Thanks so much!
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Introduction This article explores the design of a cache system that can improve the performance of a web site or web application.  The assumption is that the web site has many more “read” operations than “write” operations (this is commonly the ca…
BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (https://kb.isc.org/article/AA-01272), affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…
Screencast - Getting to Know the Pipeline

971 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