#10307 Add DNS entry for 10.3.163.235
Closed: Fixed by adrian. Opened by adrian.

In https://pagure.io/fedora-infra/ansible/pull-request/845 @arrfab suggested adding a DNS entry for the primary mirror scanning of CentOS Stream. Currently the configuration file contains 10.3.163.235. Please add a DNS entry for this IP.


Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

This is a private ip space and it has dns internal to IAD2 of

[smooge@batcave01 dns (master)]$ host 10.3.163.235
235.163.3.10.in-addr.arpa domain name pointer master03.iad2.centos.org.
[smooge@batcave01 dns (master)]$ host centos-master01.iad2.fedoraproject.org
centos-master01.iad2.fedoraproject.org has address 10.3.163.235

what else is needed? the reverse and forward do not match but CPE may be able to add a iad2.centos.org to our dns servers if that helps

@arrfab What do you say? Is that close to what you were thinking?

Metadata Update from @adrian:
- Issue untagged with: low-gain, low-trouble, ops
- Issue priority set to: Needs Review (was: Waiting on Assignee)

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

slow to answer, as I'm AFK (PTO) : if internal mirrormanager backend is using the internal resolver in iad2 and can resolve, that's good.
That just means that if/when we'll eventually switch that node IP, we'll have to think about creating fedora infra ticket to reflect the ip change but BAU, so +1 for me

Thanks everyone. I will make the corresponding updates in ansible to use this hostname.

Metadata Update from @adrian:
- Issue untagged with: low-gain, low-trouble, ops
- Issue close_status updated to: Fixed
- Issue priority set to: Needs Review (was: Waiting on Assignee)
- Issue status updated to: Closed (was: Open)

Metadata