On Sun, 4 Feb 2007, Peter J. Cherny wrote:
At 04:58 PM 4/2/07, Trent Lloyd <[EMAIL PROTECTED]> wrote:
* 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.
The flaw here is that DNS operates over 53(UDP), last t
Hi Joe,
On Sun, Feb 04, 2007 at 01:30:58AM -0500, Joe Abley wrote:
>
> On 4-Feb-2007, at 00:58, Trent Lloyd wrote:
>
> >The flaw here is that DNS operates over 53(UDP), last time I
> >checked SSH
> >doesn't do UDP port forwarding?
>
> In the interests of dispelling a common myth, DNS operate
At 04:58 PM 4/2/07, Trent Lloyd <[EMAIL PROTECTED]> wrote:
>> * 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.
>The flaw here is that DNS operates over 53(UDP), last time I
checked >SSH doesn't do UDP port fo
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 favorit
On 4-Feb-2007, at 00:58, Trent Lloyd wrote:
The flaw here is that DNS operates over 53(UDP), last time I
checked SSH
doesn't do UDP port forwarding?
In the interests of dispelling a common myth, DNS operates over both
53/udp and 53/tcp. However, given that a substantial portion of most
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
>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.
* Make sure your SSH Profile c
anyone in toronto area, or arriving sunday morning, can loan us an
NPE 400 or G1 or G2 with 512MB?
thanks
randy
On Sat, 03 Feb 2007 13:29:13 -0600
Carl Karsten <[EMAIL PROTECTED]> wrote:
>
> > Sure I could route dns queries out through a ssh tunnel but the
> > latency makes this kind of thing unusable at times. instead of an
> > ssh tunnel, how about simple port forwarding?
>
> /etc/resolv.conf
> nameser
Sure I could route dns queries out through a ssh tunnel but the
latency makes this kind of thing unusable at times.
instead of an ssh tunnel, how about simple port forwarding?
/etc/resolv.conf
nameserver 127.0.0.1
And then whatever it takes to forward 127.0.0.1:53 to a dns that is listing o
My experience with swisscom's "eurospot" hotspots ended up involving my
tunneling everything over my VPN.
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Suresh Ramasubramanian
Sent: Friday, February 02, 2007 10:08 PM
To: nanog list
Subject: broken D
I am running djbdns and my own root-server (tinydns) on my laptop.
To axfr the root and some other zones, I use port 3001 (Cesidian
Root). With cloned (not actually slaved) zones I have no
problem at all but others might still get me.
I have seen the Mac can use things like
nameserver 192.168.2
12 matches
Mail list logo
