#4642 DNS could not resolve fed-cloud02
Closed: Fixed None Opened 9 years ago by msuchy.

On copr-be.cloud.fedoraproject.org:

[root@copr-be etc]# nslookup fed-cloud02.cloud.fedoraproject.org 66.35.62.163
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached

[root@copr-be etc]# nslookup fed-cloud02.cloud.fedoraproject.org 152.19.134.150
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached

[root@copr-be etc]# cat /etc/resolv.conf
nameserver 152.19.134.150
nameserver 66.35.62.163
options rotate timeout:1

I temporary resolved it by putting fed-cloud02 IP address in /etc/hosts. So Copr is now running, but it should be resolved better way.


Now with better formatting:

On copr-be.cloud.fedoraproject.org:
{{{
[root@copr-be etc]# nslookup fed-cloud02.cloud.fedoraproject.org 66.35.62.163
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached

[root@copr-be etc]# nslookup fed-cloud02.cloud.fedoraproject.org 152.19.134.150
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached

[root@copr-be etc]# cat /etc/resolv.conf
nameserver 152.19.134.150
nameserver 66.35.62.163
options rotate timeout:1
}}}
I temporary resolved it by putting fed-cloud02 IP address in /etc/hosts. So Copr is now running, but it should be resolved better way.

ok, two issues here:

  1. It does seem somehow it's getting dns servers from dhcp. I could not find anywhere in the old openstack where this is being set. ;( Due to this it gives the first server there that has a provider thats blocking dns. ;(

  2. The second dns server there was down because I was re-installing it. :(

So, if you can find the place in fed-cloud02 that sets these dns servers that would be lovely. Otherwise, I guess we just use the (now working again) second server there and move on until we have a new cloud?

Login to comment on this ticket.

Metadata