search for: multicastdn

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

Hello CentOS, I'm curious... there seems to be a couple of default firewall rules that I'm not familiar with in the CentOS 4.0 # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD

...d penny via samba wrote: > On 06/09/2020 20:56, Peter Pollock wrote: >> 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 >> # M...

...57523-2022743653-4403: > NT_STATUS_NO_SUCH_USER > > > The output of systemd-resolve --status is > > Global >           DNSSEC NTA: 10.in-addr.arpa >            <many others> > > Link 2 (ens18) >       Current Scopes: DNS >        LLMNR setting: yes > MulticastDNS setting: no >       DNSSEC setting: no >     DNSSEC supported: no >          DNS Servers: 10.0.0.2 > > and my interface's configuration is > > ens18: >       addresses: [ 10.0.0.3/24 ] >       gateway4: 10.0.0.1 >       nameservers: >           addresses: &gt...

...tusersids_recv)   Could not convert sid S-1-5-21-2816186202-4468957523-2022743653-4403: NT_STATUS_NO_SUCH_USER The output of systemd-resolve --status is Global           DNSSEC NTA: 10.in-addr.arpa            <many others> Link 2 (ens18)       Current Scopes: DNS        LLMNR setting: yes MulticastDNS setting: no       DNSSEC setting: no     DNSSEC supported: no          DNS Servers: 10.0.0.2 and my interface's configuration is ens18:       addresses: [ 10.0.0.3/24 ]       gateway4: 10.0.0.1       nameservers:           addresses:               - "10.0.0.2" I don't use the...

...H_USER >> >> >> The output of systemd-resolve --status is >> >> Global >>           DNSSEC NTA: 10.in-addr.arpa >>            <many others> >> >> Link 2 (ens18) >>       Current Scopes: DNS >>        LLMNR setting: yes >> MulticastDNS setting: no >>       DNSSEC setting: no >>     DNSSEC supported: no >>          DNS Servers: 10.0.0.2 >> >> and my interface's configuration is >> >> ens18: >>       addresses: [ 10.0.0.3/24 ] >>       gateway4: 10.0.0.1 >>       name...

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

Hi, Louis, Rowland, thanks for you answer. @Louis All packages were installed. I change my config file following your advices, the problem is still here. I already followed guides from thctlo's github. @Rowland Yes, my dns domain was different, but answered also to test.lan. It's now set to 'kdc=dc.foo.lab' I have my user vincent with uidNumber 10010 and gidNumber 13010

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

...it or not. Then if systemd is use correctly and you use the systemd-resolvd, you get this. A random new server im setting up, not a samba server, but that not the point, the point is resolving, And what you see in this output. sudo resolvectl ( the defaults ) Global LLMNR setting: yes MulticastDNS setting: yes DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Fallback DNS Servers: 8.8.8.8 8.8.4.4 2001:4860:4860::8888 2001:4860:4860::8844 DNSSEC NTA: 10.in-addr.arpa 16.1...

...tries in this file show the compile time defaults. > # 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 controlle...

Thank You Rowland. I did it like You say, killed avahi, added the record without domain suffix, but nothing changed, and the record seems no different compared to other records added with the suffix some time before. My Samba DNS record looks like this (and I see nothing special in there):   Name=, Records=3, Children=0     SOA: serial=39, refresh=900, retry=600, expire=86400, minttl=3600,

Hi, I have a few questions about the inner workings of netfilter (a graphical layout of my network setup @ https://aequorin.homeunix.net:62389/local/media/network-graph.png) 1) These are the syslog entries for some simple connection tests. Shorewall/netfilter has been set to record all stateful connections SSH is recognized as phys(eth0) -> $FW traffic. This is because PHYSIN is