search for: dnsstublistener

Displaying 7 results from an estimated 7 matches for "dnsstublistener".

2020 Sep 06
4
Make new server the "master"
Apparently I missed a step somewhere! On DC01 /etc/systemd/resolved.conf says [Resolve] #DNS= #FallbackDNS= #Domains= #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes On DC02 it reads [Resolve] DNS=8.8.8.8 FallbackDNS=8.8.4.4 #Domains= #LLMNR=no #MulticastDNS=no DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes So the DNS line should be the IP of the DC it's on, correct? FallbackDNS? should that be 8.8.8.8 or...
2018 Dec 27
1
After upgrade to 4.9.4, internal DNS no longer working
...in the base  /etc/hostname, /etc/nsswitch.conf and /etc/resolv.conf or systemd  cointains wrong settings, you might inherit these. So it might be that a previous samba was accepting these settings, but a latest samba not. Or a previous systemd version accepted these and a newer not..   Setting : DNSStubListener=No in /etc/systemd/resolved.conf. is correct also, yes, its what you preffer, i mask the needed services.   >hostname is DC1, confirmed by hostnamectl, resolv.conf has just two entries: nameserver (own IP), and search samdom.example.com. Same as it is now, so this all works. Just that because...
2020 Sep 06
1
Make new server the "master"
...I missed a step somewhere! >> >> On DC01 /etc/systemd/resolved.conf says >> >> [Resolve] >> # DNS= >> # FallbackDNS= >> # Domains= >> # LLMNR=no >> # MulticastDNS=no >> # DNSSEC=no >> # DNSOverTLS=no >> # Cache=yes >> # DNSStubListener=yes >> # ReadEtcHosts=yes >> >> On DC02 it reads >> >> [Resolve] >> DNS=8.8.8.8 >> FallbackDNS=8.8.4.4 >> # Domains= >> # LLMNR=no >> # MulticastDNS=no >> DNSSEC=no >> # DNSOverTLS=no >> # Cache=yes >> # DNSStu...
2020 Sep 06
2
Make new server the "master"
Thank you everyone for your help. I corrected my resolv.conf files as Peter Milesson suggested and then had to take a number of extra steps so now things are looking a little better. In case it helps anyone else in the future, here's what I found (plus I am now having problems resolving internal addresses). As far as I can see, the setup on both servers is identical (except they use their own
2020 Aug 12
7
Samba DNS fails when queried with nslookup commands
Hello, ???? Having issues with a DC not responding to DNS requests. OS is Ubuntu 18.04.4 LTS. Samba version 4.12.2 compiled from source. Checking to see what is listening on port 53 reports; @soldc4:~# netstat -tulpn | grep ":53" tcp??????? 0????? 0 127.0.0.53:53 0.0.0.0:*?????????????? LISTEN????? 2935/systemd-resolv tcp6?????? 0????? 0 :::53 :::*??????????????????? LISTEN?????
2018 Dec 27
5
After upgrade to 4.9.4, internal DNS no longer working
On Thu, 27 Dec 2018 11:07:08 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Gooood morning Rowland, :-) > > Your late ;-).. > What i also did see, so its more clear for others also. > > > Dez 22 21:08:31 dc1 systemd[1]: Starting Samba AD Daemon... > > Dez 22 21:08:31 dc1 kernel: audit: type=1131 > >
2020 Aug 13
3
Samba DNS fails when queried with nslookup commands
...; # You can change settings by editing this file. > # Defaults can be restored by simply deleting this file. > # > # See resolved.conf(5) for details > > [Resolve] > #DNS= > #FallbackDNS= > #Domains= > #LLMNR=no > #MulticastDNS=no > #DNSSEC=no > #Cache=yes > #DNSStubListener=yes > > > 1 at soldc4:~$ cat /usr/local/samba/etc/smb.conf > # Global parameters > [global] > ??????? netbios name = SOLDC4 > ??????? realm = DOMAIN.LOCAL > ??????? server role = active directory domain controller > ??????? workgroup = DOMAIN > ??????? dns forwa...