Thanks for the tip.
Adding
query-source address binded (lan) IP; port 53;
to named.conf.options .
According to preliminary tests, this is it is !
пт, 18 окт. 2019 г. в 15:41, CpServiceSPb . :
> > Have you tried the query-source option? (You might also need
> > transfer-source and notify-so
CpServiceSPb . wrote:
> So how is to change Bind9 , what and where is to set up and waht setting
> that Bind9 would send forwarding packet via wan interface but would use
> address what it is binded to or internal, if it is binded to 127.0.0.1 and
> 192.168.0.1 ?
Have you tried the query-source
May be I posted my question too complicated.
So, let' s try with examples.
As I wrote I have Asterisk as well at the server binded only to internal IP
with external trunks that is it connects time to time to external VoIP
provider, that is through wild Internet, via wan interface.
I have Iptables
On 10/17/19 3:16 PM, CpServiceSPb . wrote:
But when Bind9 forwards queries to external servers, it do it via wan
interface but uses at the first onset server external IP as sources,
I'm not surprised by this.
which is not changed by SNAT or MASQUERADE Iptables.
It can be, but it depends on
OK, it might be too early and i'm not getting your question, I'm only
half way through my first coffee of the day...
But if you have 192.168.0.1 as lan, and the wan, lets say is 1.1.1.1,
and needs to resolve a hostname, it has to go to the big wide world of
internets, and it can only do that usi
I have Bind9 on Ubuntu 18.04 x64 LTS working as a cache and forwarding one.
There are some forwarders IPs.
Server has 2 NICs (lan and wan) .
BInd9 binds strictly to localhost and lan NICs, that is to 127.0.0.1 and
192.168.0.1.
But when Bind9 forwards queries to external servers, it do it via wan
6 matches
Mail list logo
