DNS resolve issues - Dont know where to look
 

Strange issue:
My domain is forwarded from NO-IP.com to my box. NO-IP is configured for a port 80 workaround and was working great until I reinstalled Slackware on my system. When you entered my domain in a browser, the webpage came up without an issue.

Now, when you enter the domain name it wont resolve correctly in my box, but will find apache if you add :8090 after the domain. I just dont know what I did to configure it the first time, and now that I installed Dropline, so many things have changed in the /etc/rc.d directory, I dont know what could be going on.

I am also running Firestarter which has been configured to allow the directs to to port 8090.

So I guess I need to figure out whats going on and I just dont know where to start looking. The machine is set for a static IP and up to this point was working.... Oh well..

Ok first of all, Dropline Gnome has nothing to do with ports and Apache.

Secondly, firestarter is a firewall, if you're blocking everything but 8090 and using it to redirect to Apache on port 80, perhaps you need to open up your firewall to allow port 80 traffic. Check your httpd.conf file for the specific port and other configurations on how to get to your website.

Need anymore help, post more specific details about your setup. And if you need to post your httpd.conf file or any other file, try to remove the # commented areas in the file as they're junk to us for the actual configuration..

cat /etc/apache/httpd.conf | grep -v "^#"

I'll try to be more specific:
Port 80 is blocked by my ISP, like many others here.
Before I re-installed Slack, the port forwarding and port 80 work around I was using worked fine, and people could access my page by the domain without having to enter anything extra.
Opening the firewall to port 80 traffic wouldn't do me a whole lot of good seeing as how it is blocked by my ISP.

The firewall is already opened to incoming TCP traffic looking for port 8090, which Apache is already configured to listen on. My router is already configured to forward that port.
When the request comes in to my server it is getting lost somewhere.
I can veiw the page on my local network, but cant see it from outside, even when I go to a proxy site and enter the domain name.

I have looked at my httpd.conf. I have looked at my resolv.conf. I have looked at my /etc/hosts, I have looked at my rc.inetd, my rc.inet1, my rc.inet1.conf, my firewall settings, my Bind files, my logs and anywhere else I can think of. I have tried to figure out if it is an issue with how I have named my machine.

If I knew what to post here as far as config files I would. I just dont know where to start. Thats all I was asking.

The Dropline stuff in /etc/rc.d/ is strictly for starting daemons like HAL, avahi, and Dbus, and likely are unrelated to the issue here. It utilizes Slackware's Sysvinit scripts so that it doesn't have to modify existing files where possible (the exception is the stale pam lockfile line in rc.local, which will probably be moved to a dedicated init script later on, though Slackware's init system is quite unfriendly to third-party packages).

Have you tried letting down your IPTables (Firestarter) and seeing if it works with only the router? Have you verified that you haven't banned outside access via any of the /etc/hosts* files? In particular, many people make serious errors in hosts.deny. Have you verified that you can establish a local connection on http://localhost:8090 (or port 80)? It would be optimal to set your apache standalone port via the http.conf, rather than using redirects through two separate layers of NAT (the router and the IPTables).

One thing I did verify is that http://localhost wont work and is refused, though localhost:8090 is not. I set my httpd.conf to have apache listen on 8090 which worked during the last install.

I have made some mods to host.deny that apply (I thought) to sshd for .jp, .de, .cn and derivatives of that. Also in there is HOST: UNKNOWN which might need some looking into.

The only thing done on the router was to make it recognise that 8090 was a valid port.

I have not let down the wall, but I'll give that a try..

One other odd thing is that on every reboot, something keeps writing an eth_up command to the top of my rc.inet1 file... Makes no sense to me..

Also when I drop the firewall the localhost request still gets refused..

Ugh. That is unfortunately a known problem in GNOME's system-tools-backends. It affects any GNOME distributions that are installed on Slackware systems, because the authors of that program didn't write that correctly. We're working on a fix for that right now, and we're going to send a patch to the folks at gnome.org to correct that. We've fixed it in Dropline GNOME 2.16.0, but we're working on a more permanent solution where it does this stuff correctly (the method that was used was totally stupid). We only have one person that is a perl programmer, so that's why this has sat by the wayside (he hadn't noticed the discussion previously, or he probably would have patched it sooner).

I would suggest that you don't use GNOME's network configuration tool if you use Dropline, Freerock, or Gware (or any GNOME on Slackware). At least until we come up with a patch to correct that annoying issue.

If it helps, I commented out some stuff in various files the rc.d directory and it stopped happening..I would be hard pressed to tell you exactly what I did, but I know that stopped it from happening over and over again..

Might you be suggesting that a switch back to KDE might help me diagnose the issue? I have tried everything in the book.

Update:
 

To this point, if I enter 8090 after the domain, the page loads, however NO-IP is supposed to prevent you from having to enter the port after the domain name. I can ping the site and get a reply. DIG shows the basic stuff..

From here, any ideas on where to start looking?

Nope. I doubt it has anything to do with KDE or GNOME. The ethernet interface problem in the system-tools-backends is a totally different issue.

The issue sounds like a configuration with no-ip. If you do not enter a port number, then there is no way that your browser will know what to use (and will default to port 80). If no-ip isn't specifying 8090 correctly, then you'll simply get port 80. The fact that you can type it with :8090 after the address name indicates to me that your PC is fine.

I went back to NO-IP and checked things out. As it turns out, the port 80 redirect was set for mydomain.com, less the www - but there wasn't a work around for www.mydomain.com so I added the workaround.. Who knows if it will work or not..

BINGO!!! That was the ticket.. The fact there wasn't a workaround for the www is what was messing me up.. Belive it or not, you helped me just be simply telling me to look there rather than at my box... Many thanks..

No prob. Glad you got it ironed out.

For most of us,...after re-installing the Distro, "Firestarter" needs to be configured at that point after rebooting. IF YOU saved "Firestarter" in YOUR "/home" partition, than it is configured as YOU have me believing. Thanks for posting the whole story. The problem, the actions, observations and corrections, many kudos.