Displaying 5 results from an estimated 5 matches for "intdom".
Did you mean:
ntdom
2019 May 04
2
Issues with bind9 dlz
.... The
DNS backend is DLZ
We are seeing DNS issues as per below
When using dnsupdate we get the following error. The server can resolve the
hostname(itself)
added interface eth0 ip=192.168.117.10 bcast=192.168.117.255
netmask=255.255.255.0
IPs: ['192.168.117.10']
need cache add: A server5.intdom.group 192.168.117.10
Looking for DNS entry A server5.intdom.group 192.168.117.10 as
server5.intdom.group.
Traceback (most recent call last):
File "/usr/sbin/samba_dnsupdate", line 827, in <module>
elif not check_dns_name(d):
File "/usr/sbin/samba_dnsupdate", line 3...
2019 May 04
0
Issues with bind9 dlz
...DNS issues as per below
>
> When using dnsupdate we get the following error. The server can
> resolve the hostname(itself)
>
> added interface eth0 ip=192.168.117.10 bcast=192.168.117.255
> netmask=255.255.255.0
> IPs: ['192.168.117.10']
> need cache add: A server5.intdom.group 192.168.117.10
> Looking for DNS entry A server5.intdom.group 192.168.117.10 as
> server5.intdom.group.
> Traceback (most recent call last):
> File "/usr/sbin/samba_dnsupdate", line 827, in <module>
> elif not check_dns_name(d):
> File "/usr/sbin...
2019 May 04
2
Issues with bind9 dlz
...mba/bind9
-rw-r--r-- 1 root root 38904 Apr 4 18:05 dlz_bind9.so
-rw-r--r-- 1 root root 38904 Apr 4 18:05 dlz_bind9_10.so
-rw-r--r-- 1 root root 38904 Apr 4 18:05 dlz_bind9_11.so
-rw-r--r-- 1 root root 38904 Apr 4 18:05 dlz_bind9_9.so
/etc/hosts
192.168.117.10 server5
192.168.117.10 server5.intdom.group
/etc/hostname
server5
On Sun, May 5, 2019 at 12:58 AM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Sun, 5 May 2019 00:11:40 +1000
> Rob Thoman via samba <samba at lists.samba.org> wrote:
>
> > Hi,
> >
> > We mi...
2019 May 05
1
Issues with bind9 dlz
...interface eth0 ip=192.168.117.10 bcast=192.168.14.255
netmask=255.255.255.0
added interface eth0 ip=192.168.117.10 bcast=192.168.14.255
netmask=255.255.255.0
Cannot do GSSAPI to an IP address
Failed to start GENSEC client mech gssapi_krb5: NT_STATUS_INVALID_PARAMETER
pszZoneName : intdom.group
pszZoneName : _msdcs.intdom.group
I went through the
https://wiki.samba.org/index.php/BIND9_DLZ_AppArmor_and_SELinux_Integration bit
and setup the selinux and apparmor exceptions, restarting the apparmor. I
hadn't noticed but am seeing an rndc issue
May 05 13:19:20 doze...
2019 May 05
0
Issues with bind9 dlz
...5 dlz_bind9.so
> -rw-r--r-- 1 root root 38904 Apr 4 18:05 dlz_bind9_10.so
> -rw-r--r-- 1 root root 38904 Apr 4 18:05 dlz_bind9_11.so
> -rw-r--r-- 1 root root 38904 Apr 4 18:05 dlz_bind9_9.so
Nothing wrong there
> /etc/hosts
> 192.168.117.10 server5
> 192.168.117.10 server5.intdom.group
That really should be on one line and what happened to '127.0.0.1' ?
try it like this:
127.0.0.1 localhost
192.168.117.10 server5.intdom.group server5
> /etc/hostname
> server5
Good, just the short hostname
Rowland