I've just run into a problem with my Slackware web server. In trying to fix it, I think I may have made it worse.

I've got a Slackware web server and a Windows box running behind a Linksys router.

The slackware server has been running our web site for several months now, no problem whatsoever. We launched a new website on Jan. 1, to correspond with a new company name. I was able to access the new site from work today without an issue, but when I try to access it from home, I am still seeing the "This domain is parked" page from GoDaddy. The domain is registered through GoDaddy and my DNS is through DynDNS. I've tried clearing my cache, tried clearing my cookies...nothing helped. That's problem #1.

Problem #2 came in when I tried to fix problem #1. (Go figure) I realized that the domain name on the linux server was still the old one. I ran netconfig to change the domain, and when I did, I lost my external network connection. BUT, even better - now I can get to the new domain site from the linux server. Still can't get to it from the Windows box.

I'm stuck...I have no clue what I did wrong, nor do I know how to fix it. I've never had this problem in the past. Any insight/suggestions would be GREATLY appreciated as I have no external net connection on the server, nor can I get to the new site from the Windows machine.

Any ideas???

Ok...I fixed my network connection issue - DNS resolution (DUH)

Anyway...I'm still left with one problem - the Windows box on my network can't see the new site. My slack server will now load the new site without a problem, and I can load the new site from outside the network, but when I try to load it on the Windows box, I get the parked page for GoDaddy.

I've tried clearing cache, clearing cookies, the infamous Windows reboot....NOTHING works....

Is it a resolution issue with my server, or should I try adding a host file to the System32 on the Windows machine??

Any advice would be much appreciated, as I'm absolutley stuck here...

Thanks!!!

-Tara

I have an identical setup: Slackware on one box, windows on the other, with Godaddy and Dyndns being used just as you are using them. It might simply be that your new domain name hasn't propogated through the DNS system yet, and the DNS being used by your ISPs are still pointing to GoDaddy's parked page. It might take a day or two for the new name to spread.

You can still get to the site from the local IP addr, right? (http://192.168....)

In my setup, I did eventually create a hosts file on Windows that uses my local IP - but this was more for being able to use the host name when using FTP or other services that I permit only on the local network.

On the Dyndns site, there is also a useful windows version of the dig command (look on their tools page). By running dig you can see how the new name is being resolved from your windows box.

Hope this helps!

Thanks Michael. I appreciate the info...I talked with GoDaddy support again, after they informed me earlier tonight that it must be a problem with my network and they pointed out that it does sometimes take a full 48 hours to fully update the DNS(I hadn't thought of that, since I was getting to it from a couple of places). It's only been a little over 24, so I'm gonna ride it out and see how it is tomorrow. If it's not better by tomorrow night, I'll be findin a brick wall to beat my head against