View Single Post
  #3  
Old 8th February 2006, 02:18
VinceDee VinceDee is offline
Junior Member
 
Join Date: Feb 2006
Posts: 9
Thanks: 4
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by falko
If I understand you right, the DNS records for mydomsin.com are managed by godaddy. So there's no point in creating the DNS records for this domain again on the ISPConfig server. Remove them.

Do the DNS records for mydomain.com at godaddy point to your router's public IP address? If so, did you forward port 80 from your router to your ISPconfig box?
They are managed by godaddy so I'll remove any reference to DNS records under the ISPConfig DNS Manager for these two sites.

By "the DNS records for mydomain.com at godaddy" are you referring to the "A records"? It currently does not point to my public IP address for one of the sites, it points to what I presume is their own nameserver (64.202.189.170). I can easily make it do so. The other site does have it pointing toward my public address. And forwarding port 80 to the ISPConfig box is no problem.

So basically you're saying that if I have a company managing my domains (like godaddy) that I should just:

1. Change their A record to point to my public IP address.
2. Make sure my router is pointing port 80 toward my ISPConfig box
3. Don't create DNS records for my sites in ISPConfig
4. Don't do "domain forwarding" from godaddy for my domains

Thanks
Reply With Quote