#4713 beaker-project.org DNS zone cannot be resolved inside Fedora infrastructure
Closed: Fixed None Opened 9 years ago by dcallagh.

= bug description =
Within Fedora infrastructure, DNS lookups for beaker-project.org are returning NXDOMAIN.

For example, on virt16.qa.fedoraproject.org when runnning Beaker job:

{{{
fatal: Unable to look up git.beaker-project.org (port 9418) (Name or service not known)
}}}

{{{
http://beaker-project.org/yum/harness-testing/Fedora21/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: beaker-project.org"
}}}

Also reproduced on bastion-comm01.fedoraproject.org:

{{{
$ nslookup beaker-project.org
;; connection timed out; trying next origin
Server: 10.5.126.21
Address: 10.5.126.21#53

** server can't find beaker-project.org: NXDOMAIN
}}}

= bug analysis =
The beaker-project.org DNS zone is served by Red Hat's DNS servers (although the actual IP addresses are in Linode, it is not a Red Hat internal thing).

I'm guessing this is caused by some kind of split DNS used in Fedora infra for Red Hat domains.

= fix recommendation =
Maybe the beaker-project.org zone just needs to be copied onto the Fedora infra DNS servers?


Please note that beaker-project.org is not served by the Fedora Project, but by Red Hat IT.

We will need to contact them to get this solved.

Sorry for the confusion, this should now be solved.

Login to comment on this ticket.

Metadata