[
https://ovirt-jira.atlassian.net/browse/OVIRT-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgheni Dereveanchin reassigned OVIRT-2857:
-------------------------------------------
Assignee: Marc Dequènes (Duck) (was: infra)
> zone transfer to OSAS dns broken from PHX
> -----------------------------------------
>
> Key: OVIRT-2857
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2857
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Evgheni Dereveanchin
> Assignee: Marc Dequènes (Duck)
>
> I've been experiencing issues with hostnames showing outdated IPs recently in
> PHX.
> Looks like zone transfer is broken between foreman.phx.ovirt.org and OSAS DNS
> servers, specifically ns1.osci.io and ns2.osci.io that are mentioned as
> authoritative for this zone.
> Example:
> dig staging-shift-int.phx.ovirt.org @foreman.phx.ovirt.org
> ;; ANSWER SECTION:
> staging-shift-int.phx.ovirt.org. 86400 IN A 38.145.50.70
> dig staging-shift-int.phx.ovirt.org @ns1.osci.io
> ;; ANSWER SECTION:
> staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36
> dig staging-shift-int.phx.ovirt.org @ns2.osci.io
> ;; ANSWER SECTION:
> staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36
> The correct IP is 38.145.50.70 in this case and the name server in PHX has
> already been restarted and re-transfer initiated several times yet
> unfortunately the changes are not visible on OSAS DNS which is blocking us
> from rebuilding the staging OpenShift environment.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100118)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/H6TH2WPNA2OR4N3NKHOT2ECEDTEPNUCR/
