similar to: [Bug 2029] New: ssh connection failure error message confusing when talking to dual IPv4/6 host

Hey guys! To make the adoption of IPv6 networks with Samba4 more smooth / robust, I think that it is vital to give to Samba4, the ability for it, to join a IPv4-Only Secondary DC, into a Dual-Stacked Primary DC. This doesn't work today. Otherwise, these days to enable IPv6 within a "Samba4 AC DC" network, it is a requirement to enable it, simultaneously, on each and every network

https://bugzilla.netfilter.org/show_bug.cgi?id=1117 Bug ID: 1117 Summary: Table ipv4-nat prerouting dnat doesn't accept dest IP:PORT Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft

On 10/15/20 2:02 PM, jeremy ardley wrote: >> how/where do I configure (just) the dovecot smtp-client -> submission_relay_host to only connect IPv4? > > It appears your host has A and AAAA records in your DNS. The clients will try IPV6 first if they see an AAAA record. > > If you don't need IPV6 for your host remove the AAAA record. All connections will then only use

On 16/10/2020 4:04 am, PGNet Dev wrote: > 2020-10-15 12:51:45 submission(mua at example.com)<8OJP+rqxuvho7Z95>: Info: Successfully relayed message: from=<test at remote.example.com>, size=84, id=LMe...Aw, nrcpt=1, reply=`247 2.0.0 Ok: queued as 4CC0KY1wXNzWf93' > > not fatal, but wasted effort, and noise in the logs. > > how/where do I configure (just) the dovecot

> On 16/10/2020 00:52 PGNet Dev <pgnet.dev at gmail.com> wrote: > > > On 10/15/20 2:02 PM, jeremy ardley wrote: > >> how/where do I configure (just) the dovecot smtp-client -> submission_relay_host to only connect IPv4? > > > > It appears your host has A and AAAA records in your DNS. The clients will try IPV6 first if they see an AAAA record. > >

On Fri, Jan 24, Richard W.M. Jones wrote: > However I don't understand why disabling IPv6 should be necessary. If > sites resolve to AAAA+A records, then presumably it's going to choose > the A (IPv4) route since no IPv6 route exists. If a site resolves to > only an AAAA record, then it's not reachable whatever we do. For me the code tries to reach the ipv6 address,

Hello, I am doing some tests with asterisk on a dual-stack environment. I have some doubts regarding asterisk binding addresses on a server with 2 network cards. According to asterisk documentation: /; With the current situation, you can do one of four things:/ /; a) Listen on a specific IPv4 address. Example: bindaddr=192.0.2.1/ /; b) Listen on a specific IPv6 address.

Hello! I am having a strange issue with CentOS 5.4 that I cannot seem to solve. Every DNS lookup results in AAAA records being requested first before A records. As a result, this causes a large amount of unnecessary DNS traffic on the network. IPv6 has been completely disabled on these servers: /etc/modprobe.conf, ipv6 off and net-pf-10 off /etc/sysconfig/network, NETWORKING_IPV6=no lsmod |

Bind_DLZ is not loaded Which makes sence if we see the errors.. Verify if this is loaded.. I have it in named.conf.local // adding the dlopen ( Bind DLZ ) module for samba, beware, if you using bind9.9 then you need to change this manualy include "/var/lib/samba/bind-dns/named.conf"; > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

There seems to be a problem with my local dns server resolving mirror.centos.org. I know something about dns but obviously not enough to figure out what might be wrong here or how to fix this in bind configs. The SERVFAIL errors below seem to be related to AAAA and MX queries for the domain. Please advise. TIA. # host mirror.centos.org 8.8.8.8 Using domain server: Name: 8.8.8.8 Address:

Hello all, I recently have a problem with multiple addresses and address families. Problem is simple, i have some hosts with IPv4 access only and some with IPv6 access. This wouldn't be big problem if I had a stable IP addresses. But sometimes I move to another network with complete different addresses. So I created patch which on option BindAddress accept list of addresses. With ip I solved

I can't get IPv6 routing to configure correctly despite everything I've read saying it should This is my network config on a fully-updated CentOS 5.8 system: # cat /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=yes HOSTNAME=my.hostname.com GATEWAY=aaa.bbb.ccc.ddd IPV6_DEFAULTGW=2a02:aaaa.bbbb::1 IPV6_DEFAULTDEV=eth0 # cat /etc/sysconfig/network-scripts/ifcfg-eth0

On Thu, Jan 23, 2014 at 11:44:52PM +0100, Olaf Hering wrote: > Signed-off-by: Olaf Hering <olaf@aepfle.de> > --- > > Untested in this environment. > > appliance/init | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/appliance/init b/appliance/init > index b25ea26..cc8c978 100755 > --- a/appliance/init > +++ b/appliance/init > @@ -71,6

On Fri, Jan 24, 2014 at 11:55:26AM +0100, Olaf Hering wrote: > On Fri, Jan 24, Richard W.M. Jones wrote: > > > However I don't understand why disabling IPv6 should be necessary. If > > sites resolve to AAAA+A records, then presumably it's going to choose > > the A (IPv4) route since no IPv6 route exists. If a site resolves to > > only an AAAA record, then

https://bugzilla.mindrot.org/show_bug.cgi?id=2037 Priority: P5 Bug ID: 2037 Assignee: unassigned-bugs at mindrot.org Summary: sshd Causing DNS Queries on ListenAddress when binding to IPV4 and IPV6 addresses on AIX Severity: normal Classification: Unclassified OS: AIX Reporter: caleblloyd at

the problem is that dnsupdate is not working becuase i use dlz. i cannot use dbsupdate with dnsupdate it fails. *Patrik* WWW <https://patrikx3.com> | GitHub <https://github.com/patrikx3/> | NPM <https://www.npmjs.com/~patrikx3> | Corifeus <https://corifeus.com> | +36 20 342 8046 On Sat, Aug 3, 2019 at 9:22 AM Rowland penny via samba < samba at lists.samba.org>

On 03/08/2019 03:01, Patrik via samba wrote: > My config is this: > # Global parameters > [global] > # bind interfaces only = Yes > # if this is turned on, always perfect > # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 > # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 > 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 > #

I must have something mis-configured in my bond setup. Things are working, but I'm getting TONS of this sort of stuff in my log: +2001:502:ad09::4#53: 1 Time(s) network unreachable resolving 'kns1.kuwaitnet.net/A/IN': +2001:503:231d::2:30#53: 1 Time(s) network unreachable resolving 'kns1.kuwaitnet.net/A/IN': +2001:503:a83e::2:30#53: 1 Time(s) network unreachable

Hi Bob, ? Ok, things are looking ok again? dpkg-reconfiure krb5.conf , doesnt do much expect installing and configuringing krb5.conf which basicly only sets the REALM.? "init administrator" will not connect to kerberos? If the DNS isnt running, its unable to resolv the servernames for the REALM. Resulting in, you not able to kinit. ? Greetz, ? Louis ? ? Van: Robert Wooden

Using CentOS 6.9 with IPv4 configured, and _not_ disabling IPv6 yet, we want this NFS client system to prefer the IPv4 address of a dual-stack remote NFS server, which has both A and AAAA records in DNS. Otherwise we get a minutes long pause while automounter tries to mount the IPv6 address -- I can see automounter's '/bin/mount' running, using the AAAA record of the server, until