Yep, that's it. The MASQ entry will nat all outbound traffic to the primary IP
of the interface. If you want to be playing with secondary IPs this is almost
certainly not right.
--
Sent from my mobile device, please excuse brevity and typos___
Please v
Thank you, Phil - that might be the answer. I'm not super knowledgeable
about iptables, and I certainly didn't configure it this way
(specifically), but the one problematic node does seem to have a
postrouting chain. I'll have to investigate how this came about and how to
remove, but perhaps this
On 19/07/16 00:38, Ian Veach wrote:
Negative Ghostrider...:
[root@foo:~]# iptables -t raw -nvL
Might want to check "-t nat" as well.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailin
> From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of
> Ian Veach
> Sent: Tuesday, 19 July 2016 8:09 AM
> To: Barry Margolin; comp-protocols-dns-b...@isc.org
> Subject: Re: weird transfer-source problems with one DNS node
>
>
>
t; device
>
> Thanks!
>
> Sent via the Samsung Galaxy Note® 4, an AT&T 4G LTE smartphone
>
>
> Original message
> From: Barry Margolin
> Date: 07/18/2016 12:12 (GMT-08:00)
> To: comp-protocols-dns-b...@isc.org
> Subject: Re: weird transfe
In article ,
Ian Veach wrote:
> So unless I'm crazy (possible, regardless)... named is reporting using 230,
> but OS is showing 240 (and remote host logs confirm 240)!?
Could something in iptables be transforming it at a lower level?
--
Barry Margolin
Arlington, MA
___
Der, sorry. Machines are all RHEL 6.8, running the BIND provided by RH:
9.8.2rc1-RedHat-9.8.2-0.47.rc1.el6
Restarting BIND (or even the OS) doesn't seem to change anything. I don't
seem to have scan as an option for rndc. I assume it's in a newer version
that RH doesn't yet provide for RHEL 6.
Ian Veach wrote:
>
> So, any ideas on why I would see that slave initiate transfers on it's OS
> IP versus the transfer-source IP... especially when the other three work
> fine?
What does the log say about interface addresses? Which version of BIND are
you running? Has the xfer interface been rec
I'm having a weird problem where one of our DNS servers is not
communicating on the expected transfer-source IPs (but the rest are).
They're generally configured exact/similar, but there's obviously something
causing a difference on the one node.
We run four slave DNS as public NS (with private ma
9 matches
Mail list logo
