On 2013-09-28 09:37, loran42o wrote:
Le 28.09.2013 00:08, Terje Elde a écrit :
On 28. sep. 2013, at 00:03, Frank Leonhardt fra...@fjl.co.uk wrote:
If I understand the way it works correctly, the resolver pulls a list of the NS
and hard-sets the port number for each to 53 (via a manifest
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
Le 28.09.2013 00:08, Terje Elde a écrit :
On 28. sep. 2013, at 00:03, Frank Leonhardt fra...@fjl.co.uk wrote:
If I understand the way it works correctly, the resolver pulls a list of the
NS and hard-sets the port number for each to 53 (via a manifest constant) .
See libc/resolv/res_init.c.
Le 27.09.2013 23:31, jb a écrit :
Well, I hope I understand you.
You use DNS Proxy server, like BIND or DNSMASQ.
hi,
actually I use two daemons,
one to serve as a autoritative DNS server : nsd
the other one to serve as a recursive DNS resolver with caching : unbound
I can't set them both
Le 28.09.2013 01:11, Frank Leonhardt a écrit :
It was more of an explanation as to /why/ it's not easy to do what asked
in the original reasonable-sounding question.
Hi,
Thanks for the explanation of how it works from the behind.
I don't think I'll compile and maintain my own libc just for DNS
On 28/09/2013 00:20, Michael Sierchio wrote:
On Fri, Sep 27, 2013 at 4:11 PM, Frank Leonhardt fra...@fjl.co.uk wrote:
On 27/09/2013 23:08, Terje Elde wrote:
On 28. sep. 2013, at 00:03, Frank Leonhardt fra...@fjl.co.uk wrote:
If I understand the way it works correctly, the resolver pulls a
On 28. sep. 2013, at 15:50, Frank Leonhardt fra...@fjl.co.uk wrote:
Given that BIND can happily listen on ports other than 53 and OpenBSD allows
a port to be specified against each nameserver in resolv.conf, it does not
seem an unreasonable question to me.
Just to avoid any
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
On 9/28/2013 at 7:16 PM Laurent SALIN wrote:
|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
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
On Sep 28, 2013, at 2:24 PM, Laurent SALIN salin.laur...@laposte.net wrote:
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
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
On Fri, Sep 27, 2013, at 13:20, Laurent SALIN wrote:
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
On 27. sep. 2013, at 20:20, Laurent SALIN salin.laur...@laposte.net wrote:
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
Why is that a bad solution?
You'd cache locally, which is often considered a good thing?
Is there any way to use multiple IPs?
hi,
no I can't. Each VPS got only one IPv4 and I'm really not aware yet
about how IPv6 works.
Laurent SALIN
___
freebsd-questions@freebsd.org mailing list
Le 27/09/2013 22:28, Terje Elde a écrit :
Why is that a bad solution?
You'd cache locally, which is often considered a good thing?
Granted, it's a bit of a weird setup, but still.
I hope it could be esay as put the ip of my resolver VPS in the
/etc/resolv.conf and let PF translate the
Laurent SALIN salin.laurent at laposte.net writes:
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
On 27/09/2013 19:20, Laurent SALIN wrote:
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
On 28. sep. 2013, at 00:03, Frank Leonhardt fra...@fjl.co.uk wrote:
If I understand the way it works correctly, the resolver pulls a list of the
NS and hard-sets the port number for each to 53 (via a manifest constant) .
See libc/resolv/res_init.c. All you need to do(!) is change this to a
On 27/09/2013 23:08, Terje Elde wrote:
On 28. sep. 2013, at 00:03, Frank Leonhardt fra...@fjl.co.uk wrote:
If I understand the way it works correctly, the resolver pulls a list of the NS
and hard-sets the port number for each to 53 (via a manifest constant) . See
libc/resolv/res_init.c. All
On Fri, Sep 27, 2013 at 4:11 PM, Frank Leonhardt fra...@fjl.co.uk wrote:
On 27/09/2013 23:08, Terje Elde wrote:
On 28. sep. 2013, at 00:03, Frank Leonhardt fra...@fjl.co.uk wrote:
If I understand the way it works correctly, the resolver pulls a list of
the NS and hard-sets the port number
21 matches
Mail list logo
