View Single Post
  #4  
Old 19th July 2011, 10:43
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,735 Times in 2,571 Posts
Default

Quote:
Originally Posted by midcarolina View Post
Ok, this is the part that gets me. Port forwarding is on in the router for a number of ports that I would need for the server to operate (i.e., 21-ftp,22-ssh,25-smtp, etc. this includes 80 for http:// and 8080) Still no go? So this I am still stumped on.
Check your router's firewall. It is also possible that your ISP blocks some ports.

Quote:
Originally Posted by midcarolina View Post
The answer for DNS helped a bit, except one item. Do I use the two DNS ips assigned by my ISP for DNS? They are of course the same, except one ends in 51 and the other 52. Or do I use the single public modem IP, in which case their is only one. My nameservers I created myself at my domain registrar, godaddy.
They are accepted (by godaddy) using the public modem ip and the ISP provider's two DNS ips, using ns1.example.com, and ns2.example.com.
If you refer to /etc/resolv.conf, you can put your ISP's DNS servers there (but you don't have to if name resolution is working already).
For your zones, you must use the public modem IP, and as the nameservers in your zones, you use ns1 and ns2.example.com.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote