For problems such as can't resolve an internal webpage from outside your network try this:
Check 4 things once you are sure your DNS is resolving correctly: 1) are there RDR statements in your ipnat.conf file 2) are the pass statements for those ports in your ipf.conf file 3) is ipforwarding on 4) is there a services properly configured on the machines behind the firewall that are listening on the ports in the RDR clauses. For problem such as clients inside your network failing to be able to see the outside world, try the following: 1) make sure your ipnat.conf file has portmap and map clauses set up 2) make sure ipforwarding is on 3) make sure your block statements aren't preventing the traffic (log them and review the logs to see what rule might be breaking it) For both, make sure ipforwarding is on. A quick test to see if this is the issue, try connecting to a service running on the box from both inside and outside the network. If you succeed both times, but still can't get packets to traverse through the machine. This is probably the problem. Review the How-To listed on the homepage for syntax of the statements above and verify they're correct. > Hello, > When i originally set up my internal domain i did not have the > domain registered, it was my own use. Then i registered it and .com, .com > is not working, my internal dns resolves to my cable IP, which is where it > should go, then it stops, nothing internally can go to .com anything, > externally everything works fine. > Hope this helps clarify. > Thanks. > Dave. >
