Displaying 3 results from an estimated 3 matches for "fqdnservernam".
Did you mean:
fqdnservername
2019 Nov 10
2
Invalid PTR record in reverse lookup zone
...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 spn: nfs/servername at ... instead of
nfs/fqdnservername at ... is used by the clients to get the
ticket.
I tracked the problem down to an invalid PTR record for
the DC in the reverse lookup zone. The ptr record
had only the hostname but not the fqdn set.
I manually fixed this using samba-tool dns add/delete and nfs
mount worked again. Unfortunately...
2019 Nov 10
0
Invalid PTR record in reverse lookup zone
...unts. 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 spn: nfs/servername at ... instead of
> nfs/fqdnservername at ... is used by the clients to get the
> ticket.
>
> I tracked the problem down to an invalid PTR record for
> the DC in the reverse lookup zone. The ptr record
> had only the hostname but not the fqdn set.
>
> I manually fixed this using samba-tool dns add/delete and nfs
&g...
2019 Nov 10
4
Invalid PTR record in reverse lookup zone
...t 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 spn: nfs/servername at ... instead of
> > nfs/fqdnservername at ... is used by the clients to get the
> > ticket.
> >
> > I tracked the problem down to an invalid PTR record for
> > the DC in the reverse lookup zone. The ptr record
> > had only the hostname but not the fqdn set.
> >
> > I manually fixed this using...