similar to: Samba AD with internal DNS on IPv4/IPv6 but only announcing IPv4 address

On Thu, 19 Jul 2018 15:26:28 +0200 Thomas Glanzmann via samba <samba at lists.samba.org> wrote: > Hello, > I use Samba AD in Version 4.8.3 and would like to run it on IPv4 und > IPv6 in order to be able to have Samba acting as IPv6 DNS Server. > However since I have problem with sysprep domain join as soon as Samba > advertises its own Domain Controller Hostname as IPv4 and

Hello, I noticed that samba internal dns allows recursive queries from everywhere. I wonder if it is possible to limit recursive queries to certain IPv4 and IPv6 network ranges? Cheers, Thomas

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 > #

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 |

Hey! How are you? I have two interfaces (192.168.78.20 / *2001:470:1f1b:5b3:21b:21ff:fea6:ce93* and 192.168.81.20 / *2001:470:1f1b:5b5:21b:21ff:fea6:ce92*) I have interfaces disabled i mean that i bind on everything on samba ac-dc... What here is what is weird, (via bind9 DLZ i am using it and is working), but on my clients i am getting some weird ipv6 addresses: patrikx3 at bitang:~$ ping

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.

On 02/03/2020 11:51, Paul Littlefield via samba wrote: > On 02/03/2020 10:49, Rowland penny via samba wrote: >> Does your DC have a fixed IP and if not, why not ? > > Yes, using netplan in Ubuntu 18.04... > > network: > ? ethernets: > ??? ens18: > ????? addresses: > ????? - 130.130.0.218/16 > ????? gateway4: 130.130.0.1 > ????? nameservers: > ???????

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,

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 +71,10 @@ for f in /sys/block/{h,s,ub,v}d*/queue/scheduler; do echo noop > $f; done # Update the system clock. hwclock -u -s

On 02/03/2020 13:36, Paul Littlefield wrote: > On 02/03/2020 13:16, Rowland Penny via samba wrote: >> >> Samba runs samba_dnsupgrade on a regular basis, using dns_update_list >> as a template. Amongst the list of dns entries is this: >> >> AAAA ${HOSTNAME}?????????????????????????????????????????? $IP >> > > Hi Rowland, > > Can I change any of

Hi there, Domaincontroller name: risky.home.schinz.de dig dig @risky -tANY risky.home.schinz.de. returns: ;; ANSWER SECTION: risky.home.schinz.de. 900 IN A 10.0.180.254 risky.home.schinz.de. 900 IN AAAA ::1 I have a strange behavior in my network. It's only concerning DNS, but maybe someone can help me. If a do a ssh on risky from another machine (exact command:

Hi, I keep getting entries like these in my logs: network unreachable resolving '0.centos.pool.ntp.org/AAAA/IN': 2001:500:40::1#53: 1 Time(s) network unreachable resolving '0.centos.pool.ntp.org/AAAA/IN': 2001:500:e::1#53: 1 Time(s) network unreachable resolving '0.centos.pool.ntp.org/AAAA/IN': 2001:dc3::35#53: 1 Time(s) I don't see any IPV6 parameters to

On 02/03/2020 09:54, Paul Littlefield via samba wrote: > Hello, > > I have some DNS weirdness for you folks to chew on and help me with... > > On Saturday I added this entry... > > $ samba-tool dns add dc3 mydomain.com V-RDS02 A 130.130.0.252 > > but this morning I've come in to the office and the A records have > disappeared to be replaced by AAAA records...

I have a Centos server that is running BIND and has IPv6 global addresses. I have entered a number of AAAA records into this copy of BIND in a local view and zone (tld is htt). Over IPv4, I have no trouble with nslookup ('nslookup - 127.0.0.1' and 'nslookup - 192.168.128.55'). I get the AAAA records back. But if I try to use the IPv6 address of the system I get a time out.

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>

In dovecot conf, for submission relay, I've config'd submission_relay_host = lan.example.com submission_relay_port = 465 hostname -- not IP -- must be used, to inform relay for cert verification match. Here, host lan.example.com lan.example.com has address 10.0.1.47 lan.example.com has IPv6 address fd80:25:01::47 The receiving smtp relay listens only on IPv4 -- no

Hello,     Installing bind9 on my Ubuntu 14.04 via. apt-get displays the following options.  #named -V BIND 9.9.5-3ubuntu0.16-Ubuntu (Extended Support Version) <id:f9b8a50e> built by make with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads'

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

> So, you are using Samba without problem, it is just that when you try > to use Bind9 instead of the internal dns server, your problems start. > > Let's just recap > > You have run 'samba_upgradedns' > You have altered smb.conf > You have configured 'named.conf' correctly > The Samba 'named.conf' file is readable by 'named' (this

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