Comrades.

This has been bugging me for a while. But now enough is enough.

Here's the setup. There are several systems on my home network. Most importantly, a headless Linux server, and my gaming comp that I'm using right now.

czaralex.com is set to resolve to my home IP (which only changes like twice a year so its all good). I have the DMZ setting on the router set to forward to 192.168.1.30, the internal IP of my Linux box. It works great and I've enjoyed the beauty of a home web server for a couple years now.

However.. my gaming comp cannot open a web browser (FF, IE, Opera, Whatever) and resolve czaralex.com in any way. I cannot ping it, I cannot nslookup it, I cannot do anything that would involve me using czaralex.com BUT i can do 192.168.1.30 and it works just fine. Any other computer on my network resolves czaralex.com without a problem. I tried different router ports. no luck.

After some digging around, it turns out that whenever I try to access czaralex.com from the gaming comp, it tries to resolve to 192.168.1.103 .. the internal IP assigned to the gaming comp itself.

Now.. I have a new system here, only a few months old. With a fresh XP install, it did this. On my old system where I first noticed the problem, it did it for the last 24 months. So I doubt its the XP install (well I suppose it could be). I cannot find anything on the router that I've done to cause this either. I do have many ports forwarded but nothing that I can see would cause an issue.

its only an annoyance now because I want to update my blog from home which won't allow me to 192.168.1.30/blog as it wants the domain name (damn wordpress)

Suggestions? Any other info I can provide? (router is a belkin 54g er something)

almost sounds like you need to setup a local DNS server so that when you put in czaralex.com it resolves to 192.168.1.30.  Or edit your hosts file.

Is the hosts file something in winblows or on the linux server?

omg it works perfectly. THANK YOU!