#8778 src.fedoraproject.org resolve the wrong IP address for softwarefactory-project.io
Closed: Fixed a year ago by smooge. Opened a year ago by fbo.

Describe what you would like us to do:

We did a migration of softwarefactory-project.io yesterday to a new cloud provider. IP addresses of services changed, domain name is still the same. The DNS changed was done yesterday (> 12 hours ago).

Problem is that we no longer receive web hook calls from src.fedoraproject.org. A first investigation from @pingou shown that src.fedoraproject.org resolves the previous ip address of softwarefactory-project.io. From pagure.io it resolves the right IP address.

from src.fedoraproject.org: softwarefactory-project.io has address
from pagure.io softwarefactory-project.io has address

from my laptop: dig +short @ softwarefactory-project.io
^ This is the new service address.

Could you check what is happening ?

When do you need this to be done by?

ASAP as the Pull Request Distgit CI provided by Zuul is unable to process incoming PRs.

Thanks in advance

Could this be related to the unspecified DNS fix done for https://pagure.io/fedora-infrastructure/issue/8320 ?

The problem is with the Red Hat internal DNS servers which are 'authoritative' for softwarefactory.io. They still point to the old ip address and that is what is going to be used by anything inside of a Red Hat network. A dig +trace internal shows that if you are external to PHX2 (aka where src.fedoraproject.org is) then the authoritative answer is but internal it is something else.

Please open a ticket with Red Hat IT to get this fixed. I can't do anything myself as I don't own the zone affected.

OK there does seem to be another problem which I will be following up with internal Red Hat. We are not able to get to the ns1/ns2/ns3 nameservers at this time when we could yesterday or so. I am working on figuring out what is broken here.

I have opened an internal red hat ticket to determine what changed and how to fix

Metadata Update from @smooge:
- Issue priority set to: None (was: Needs Review)
- Issue tagged with: dns, high-gain, high-trouble, outage

a year ago

Thanks for the followup and investigation.

Changes were made to allow for us to use different internal nameservers. The problem seems to be fixed.

Metadata Update from @smooge:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Yes thank @smooge ! the Zuul CI is fixed now !

Login to comment on this ticket.