Displaying 3 results from an estimated 3 matches for "f6xx".
Did you mean:
6xx
2019 Nov 10
4
Invalid PTR record in reverse lookup zone
...ad.home.arpa, .ad.home.arpa and 183.168.192.in-addr.arpa are forwarded
to the DC (.183.5 address)
Here is the output for the server:
Collected config --- 2019-11-10-18:30 -----------
Hostname: kronos
DNS Domain: ad.home.arpa
FQDN: kronos.ad.home.arpa
ipaddress: 192.168.183.5 2003:e3:570b:9400:f6xx:xxff:fexx:xxxx 2003:e3:5705:5200:f6xx:xxff:fexx:xxxxxx fd1f:6d10:24a0:1:f6xx:xxff:fexx:xxxx
-----------
Kerberos SRV _kerberos._tcp.ad.home.arpa record verified ok, sample output:
Server: 192.168.183.1
Address: 192.168.183.1#53
_kerberos._tcp.ad.home.arpa service = 0 100 88 kronos.ad.home.arp...
2019 Nov 10
2
Invalid PTR record in reverse lookup zone
Hello,
I have configured an samba AD DC for use with
some windows and linux machines. The linux machines use
samba for user auth and also as kerberos kdc for
nfs mounts. This works fine so far but after a while
the user can not access the nfs shares anymore.
I tried to analyze the problem and finally found, that
the obtaining a ticket for nfs service failes in this
case because of a wrong
2019 Nov 11
0
Invalid PTR record in reverse lookup zone
...ere is the output for the server:
>>>
>>>
>>> Collected config --- 2019-11-10-18:30 -----------
>>>
>>> Hostname: kronos
>>> DNS Domain: ad.home.arpa
>>> FQDN: kronos.ad.home.arpa
>>> ipaddress: 192.168.183.5 2003:e3:570b:9400:f6xx:xxff:fexx:xxxx 2003:e3:5705:5200:f6xx:xxff:fexx:xxxxxx fd1f:6d10:24a0:1:f6xx:xxff:fexx:xxxx
>>>
>>> -----------
>>>
>>> Kerberos SRV _kerberos._tcp.ad.home.arpa record verified ok, sample output:
>>> Server: 192.168.183.1
>>> Address: 192.168.1...