http://living.freetcp.com/main/blogs/it_gargenning/archive/category/1120.aspxInformation and articles for network and system stuffen-USCommunityServer 2.0 (Build: 60210.2610)http://living.freetcp.com/main/blogs/it_gargenning/archive/2009/11/16/12969.aspxMon, 16 Nov 2009 17:15:00 GMTe5871194-9507-42f4-ac11-7c4055381520:12969Johnz2http://living.freetcp.com/main/blogs/it_gargenning/comments/12969.aspxhttp://living.freetcp.com/main/blogs/it_gargenning/commentrss.aspx?PostID=12969http://living.freetcp.com/main/blogs/rsscomments/12969.aspxThe company also has a couple of application servers which have private IP addresses and unregistered DNS entries, and are inside the firewall. The application servers are visible within the network - including the webserver, as "internal1.example.com" and "internal2.example.com", But because they have no public DNS entries, anyone looking at internal1.example.com from outside the company network will get a "no such host" error. ...(<a href="http://living.freetcp.com/main/blogs/it_gargenning/archive/2009/11/16/12969.aspx">read more</a>)<img src="http://living.freetcp.com/main/aggbug.aspx?PostID=12969" width="1" height="1">Network and SystemTricky stuff