Displaying 5 results from an estimated 5 matches for "dnsovertl".
Did you mean:
dnsovertls
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?
Fallba...
2020 Sep 06
1
Make new server the "master"
...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
>> # MulticastDNS=no
>> DNSSEC=no
>> #...
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
2019 Feb 20
3
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
...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.172.in-addr.arpa...
2019 Feb 09
4
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
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,