Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Alternative DNS port available on public server

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Alternative DNS port available on public server


Chronological Thread 
  • From: Alex Hanselka <alex AT hanselka.me>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] Alternative DNS port available on public server
  • Date: Wed, 1 Jun 2011 01:42:30 -0500
  • List-archive: <http://lists.darkdna.net/pipermail/discuss>
  • List-id: <discuss.lists.opennicproject.org>

So you have to use firewall rules to use a DNS server on a different port?

Sorry if I am just dumb :)

On Sun, May 29, 2011 at 10:55:28PM -0400, Zach Gibbens wrote:
> I wanted to mention that 2 other servers run on 5353, according to a
> march email (for a current total, to my knowledge, of 3 servers)
> and those same iptables rules work on a rooted android smartphone with
> iptables support.
>
> Also, I think I can get a set of ipfw rules for apple and *bsd
> systems, however, I cannot test it on a mac personally, I'll be on the
> latest FreeBSD.
> Still unsure of how to apply this to Windows, all I can say is stay tuned.
>
> Slightly Unrelated note, Things are starting to work in my favor
> again, with this I should have a server running shortly, listening on
> 53 & 5353, and I'll be working towards another method for this,
> primarily for those lacking administrative rights to use this method,
> or windows (at least until I can get a smoother solution for windows)
> Glad to be able to help OpenNIC again.
>
> On Mon, May 9, 2011 at 2:03 AM, Zach Gibbens <infocop411 AT gmail.com> wrote:
> > I have tested this with Jeff tonight, I only have IPv4 access tonight,
> > but I presume substituting one address for the other will work. For a
> > Linux machine with iptables, run two commands
> >
> > sudo iptables -t nat -A OUTPUT -p udp --dport 53 -j DNAT --to
> > 216.87.84.211:5353
> > sudo iptables -t nat -A OUTPUT -p tcp --dport 53 -j DNAT --to
> > 216.87.84.211:5353
> >
> > I ran this on my linux-based router, and it applied for my whole network.
> > I'll see what methods I can do for other systems, no promises though.
> >
> > On Mon, May 9, 2011 at 12:16 AM, Jeff Taylor <shdwdrgn AT sourpuss.net>
> > wrote:
> >> I just wanted to let everyone know that I have opened up port 5353 on my
> >> public DNS server.  You can reach me at 216.87.84.211, or
> >> 2001:470:8388:10:0:100:53:20.
> >>
> >> There has been periodic discussion that some ISPs block users from making
> >> use of OpenNic because they block or redirect any traffic on port53.  I
> >> wanted to make this option available for anyone who wishes to experiment
> >> with it, to see if this gives you the ability to bypass any such
> >> blockades.
> >>
> >> Please let us know of any successes or failures with this option, and we
> >> will make the information available on the wiki to help others.
> >> _______________________________________________
> >> discuss mailing list
> >> discuss AT lists.opennicproject.org
> >> http://lists.darkdna.net/mailman/listinfo/discuss
> >>
> >
> _______________________________________________
> discuss mailing list
> discuss AT lists.opennicproject.org
> http://lists.darkdna.net/mailman/listinfo/discuss



  • Re: [opennic-discuss] Alternative DNS port available on public server, Alex Hanselka, 06/01/2011

Archive powered by MHonArc 2.6.19.

Top of Page