• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

web domain issues

mattg1981

Senior member
Dont know if this is right forum for this sort of question but here goes. I've been wanting to host my own website for my own personal images, learning php, etc. I bought a domain through godaddy.com. I am running Ubuntu 9.10 server with apache2 with a setup roughly equivalent to this guide (http://www.howtoforge.com/perfect-server-ubuntu-9.10-ispconfig-3 .... minus the email, dns, ispconfig, etc). Here are a list of some issues im having.

1. When you go to address (http://www.giantbluebox.com), it goes to my site just fine but the address bar turns into my actual IP address (http://67.11.62.219/). Is this a godaddy setting or is this because I dont have a DNS server running on my machine?

2. If I try to FTP(sftp only at the moment) or SSH to my machine using http://www.giantbluebox.com it translates the address to 64.202.189.170 which is some godaddy.com parked site, and obviously I cannot connect.

Like I said, I dont know if its because I dont have correct DNS entries or something along those lines .. or do I not have the right settings set up in the godaddy admin portal. Anyone ever experience this before? I've never dealt with DNS before (never learned about it in college) and its pretty intimidating at first glance .. thats why I skipped those steps in the howtoforge setup guide.
 
Last edited:
It sounds like you have configured your domain name at godaddy to forward to your IP address. What you really need to be doing is changing your NS records so that you domain name resolves to your IP.

When you're in the Domain Manager at Godaddy, click Total DNS control. You need an A(host) record that points to host @ with your IP and a CNAME with host WWW that points to @.
 
yeap, that was exactly the issue down to the t. everything appears to be working properly now. I havnt tried to set up a subdomain but I assume that is just a new cname.

Thanks for your help,
Matt
 
Back
Top