[Samba] Newly joined DC - Failed to bind to uuid for ncacn_ip_tcp .. NT_STATUS_INVALID_PARAMETER
Jonathan Hunter
jmhunter1 at gmail.com
Tue Jan 28 20:49:50 UTC 2020
Thank you Rowland!
On Tue, 28 Jan 2020 at 18:37, Rowland penny via samba
<samba at lists.samba.org> wrote:
> Your DC doesn't seem to be listing on its IP or 127.0.0.1 on port 53, yours:
>
> tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
>
> Mine:
>
> tcp 0 0 192.168.0.6:53 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
> [...]
> Okay, I use Bind9, but I would expect, in your case, that 'named' would
> be replaced with samba.
The listening on 0.0.0.0:53 matches my other DCs, I am pretty sure the
specific interface binding you have is just due to the 'listen-on { }'
section in your named.conf. My BIND nameservers have the same line in
named.conf, i.e. listen on 127.0.0.1 plus the local IP address; I
guess that's a standard pattern for BIND.
dc2$ sudo netstat -aplnt | grep :53
tcp 0 0 0.0.0.0:53 0.0.0.0:*
LISTEN 2721/samba
tcp6 0 0 :::53 :::*
LISTEN 2721/samba
newdc$ sudo netstat -aplnt | grep :53
tcp 0 0 0.0.0.0:53 0.0.0.0:*
LISTEN 1144/samba: task[dn
tcp6 0 0 :::53 :::*
LISTEN 1144/samba: task[dn
So I think listening on 0.0.0.0 (all interfaces) is perfectly normal
for samba's internal DNS.
> What is in:
>
> /etc/hostname
newdc$ cat /etc/hostname
newdc.mydomain.org.uk
> /etc/hosts
newdc$ cat /etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
192.168.1.6 newdc.mydomain.org.uk
> /etc/resolv.conf
newdc$ cat /etc/resolv.conf
# Generated by resolvconf
nameserver 192.168.1.3 <--- dc2
nameserver 192.168.1.6 <--- newdc
nameserver 192.168.200.10 <--- regular nameserver
nameserver 192.168.250.10 <--- regular nameserver
(This matches the format of resolv.conf from my other DCs)
Thank you :)
--
"If we knew what it was we were doing, it would not be called
research, would it?"
- Albert Einstein
More information about the samba
mailing list