North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: broken DNS proxying at public wireless hotspots

  • From: Roy
  • Date: Sun Feb 04 02:11:23 2007
  • Domainkey-signature: a=rsa-sha1; c=nofws;; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=diIqB2m6Oub/TIZH2mBbOy0o5D0/52elKcQgCc0ENKf0jxx97KtOtSDpU5DYr9ir5UPytYQrGaYsm2K/qkPycCZop3gnQhsta60IjUWxzbjw6YQfYevYYp6zZqu8jxFvPY7hZv/qnfWWXfflwmFdn+zoHJ5/0aLqf5wAsaBs+vQ=

Trent Lloyd wrote:
On Sat, Feb 03, 2007 at 09:22:30PM -0800, Lasher, Donn wrote:
If so, how do you configure your client operating system of choice to
use the novel, un-proxied ports instead of using
port 53?
* Set up the profile, to your house/work/etc, of your favorite SSH
client to forward port 53 local to port 53 on your remote machine.


Same type of config works great for HTTP (with squid, and browser proxy
settings) etc..

The flaw here is that DNS operates over 53(UDP), last time I checked SSH doesn't do UDP port forwarding?


Looks like someone already has this exact case figured out