We have created a container image and are running our playbooks through that execution environment.
There are 4 domains:
example1
domain hasex1
IPexample2
andexample3
are currently working under the sameex2
IPexample4
domain hasex3
IP
My krb5.conf:
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
default_realm = example1.net
dns_lookup_realm = false
dns_lookup_kdc = false
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true
[realms]
EXAMPLE1.NET = {
kdc = HOSTNAME.example1.net
admin_server = HOSTNAME.example1.net
}
EXAMPLE2.NET = {
kdc = HOSTNAME.example2.net
admin_server = HOSTNAME.example2.net
}
EXAMPLE3.NET = {
kdc = HOSTNAME.example3.net
admin_server = HOSTNAME.example3.net
}
EXAMPLE4.NET = {
kdc = HOSTNAME.example4.net
admin_server = HOSTNAME.example4.net
}
[domain_realm]
.example1.net = EXAMPLE1.NET
example1.net = EXAMPLE1.NET
.example2.net = EXAMPLE2.NET
example2.net = EXAMPLE2.NET
.example3.net = EXAMPLE3.NET
example3.net = EXAMPLE3.NET
.example4.net = EXAMPLE4.NET
example4.net = EXAMPLE4.NET
This is my resolv.conf
:
nameserver ex1
nameserver ex2
nameserver ex3
The Problem:
If I alter resolv.conf
, for example, by keeping ex1
in the 2nd line, it is not able to connect, and I get the error: “Cannot contact any KDC for realm ‘example1’ while getting initial credentials.”
If I move ex1
back to the 1st line, it works. However, if I move ex3
(which corresponds to example4
) to the 3rd line, it does not work. If I keep it in the 1st line, it pings successfully.
Please help! It’s been more than a month, and I have not been able to resolve this.
your text
I’m able to nslookup
, and kinit
is working for all the domains. I have tried using the /etc/hosts
file, but it’s not working, so I am just trying with resolv.conf
.
I’ve tried altering the resolv.conf
, but if the 1st nameserver works, then the 3rd one does not.
Sukanya N is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.