Re: How to ask a DNS resolver listening on a different port than the tcp/udp 53

2013-09-29 Thread Laurent SALIN
Hi,
for the list archive, here's how I solved my problem.
Some on the thread tell me to run BIND on the 1rst VPS, as DNS
autoritative server and as caching resolver who let only hosts from my
network send him queries.

Well I'm quite happy my setup with NSD as DNS autoritative and UNBOUND
as caching resolver so I don't really want to change them for BIND, but
i'd do it if this is the only way.

I descide to focus on the 2nd VPS, the one who can't send queries
directly to tcp/udp 5353, I configure UNBOUND to forward all queries to
my 1rst VPS with few dedicated lines in the
/usr/local/etc/unbound/unbound.conf:

file
...snip...

forward-zone:
   name: .
   forward-addr: public_ip_v4@5353  # forward to port 5353.
   forward-first: yes
/file

and modify my /etc/resolv.conf to only have localhost as nameserver.

The system footprint of UNBOUND is very small so it's just fine to me.

Thanks all for the help.

Laurent SALIN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: How to ask a DNS resolver listening on a different port than the tcp/udp 53

2013-09-28 Thread Laurent SALIN
Le 28.09.2013 18:32, Terje Elde a écrit :
 Not sure if I misunderstood what you're trying to do, but the way I recall 
 it, you have two boxes, one running with one recursive and one authoritative 
 nameserver, and you wanted a second box to quey the recursive nameserver on 
 the first box, which is running on another port than 53?

You just right

 Given your setup, that's a valid question. 

that's why I submit it to the FreeBSD-Question list :-)

 It's getting down to patching the resolver I felt was a bit overkill, and a 
 possible source of future pain. 
 
 How to solve it is a perfectly valid question. 

I was hoping it'll be possible to map destination port with Packet
Filter from nameserver:53 to nameserver:5353 for exemple.

 Personally I'd just think it cleaner to solve it by running a caching 
 resolver on the second host (on port 53), that could forward queries where 
 you'd like, rather than patching or usik firewall redirects. 

I guess that's how I'll fix my problem

Thanks,
Laurent SALIN

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: How to ask a DNS resolver listening on a different port than the tcp/udp 53

2013-09-28 Thread Laurent SALIN
Le 28.09.2013 21:28, Mike. a écrit :
 The way I solved this problem on my setup, I assigned another IP
 address to the network interface via ifconfig alias.
 
 I put the authoritative namesever on one IP address, and the
 recursive nameserver on the other IP address.
 
 They both are still listening on port 53, but on different IP
 addresses.

hi,
If I could it would be just fine.
I got only one public IPv4 with each VPS. I've got a IPv6 too but I'm
not easy with IPv6 yet.

The provider (Tilaa) where I rent one of the 2 VPS, the one who may need
2 IPv4, is a bit short about his range of IPv4 and I guess it's not
raisonable to ask for a second IPv4 just for my personal use in case of
studying *BSD and networking stuff, I don't have a professional use here.

Thanks.

Laurent SALIN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


How to ask a DNS resolver listening on a different port than the tcp/udp 53

2013-09-27 Thread Laurent SALIN
Hello,
I wondering how i can send queries to a dns resolver listening on a
different port than the normaly 53 tcp/udp ?

The situation:
I've got a vps who running NSD as a autoritative nameserver, listening
on tcp/udp 53 and unbound as personnal resolver, listening on a
different tcp/udp port. It work very well on his own or with my OpenBSD
gateway at home as DNS cache.

Recently i've got a new FreeBSD VPS and I want to use the first VPS as
DNS nameserver for the second VPS but FreeBSD is unable to send queries
to nameserver on a different port as the normal one (tcp/udp 53).

I've got a bad solution, use unbound on the second VPS and maybe tell
him to ask the 1rst VPS on the unusual tcp/udp port, but I wonder myself
if is it possible with Packet Filter to change the destination port of
the queries forwarded to my 1rst VPS from tcp/udp 53 to tcp/udp 5353 for
exemple ?

Or maybe anybody got a other solution ?

I hope you'll understand me :-/

Laurent SALIN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org