Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm bit of a newcomer when it comes to networking, firewalls and port forwarding - please bear with me:

I've just setup a dynamic DNS that points to my external IP and are handled through my Cisco router. Everything fine so far. When I visited my DNS through the browser,, I got redirected to the backend GUI of my router - kind of expected, but still not cool.

So to prevent my Router settings from being available on the interwebs, I did a port forward of port 80 to a non-existent IP on my LAN.

Is this a good practice or not?

share|improve this question
up vote 4 down vote accepted

Sure. This is an acceptable workaround.

Better would be to configure the router not to expose the web interface for external IPs, configure it to run on a separate port than 80, password-protect the web interface. But sometimes you have these very cheap routers that can't be configured that way. Buying a better one is recommended but not necessary.

share|improve this answer
Thanks for your answer! It's actually a quite expensive Cisco small-business-class router, so I expect that it should have this feature. Do you have any idea on what this setting might be called? – Industrial Aug 17 '11 at 18:58
Read the manual. I have never seen this box before. And others can't help unless you tell model an version. – mailq Aug 17 '11 at 19:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.