On 01/03/2014 12:40 AM, R P Herrold wrote:
On Thu, 2 Jan 2014, Dave Neary wrote:
I am not sure who manages ovirt.org's DNS records, but if we can add a
PTR record for 2600:3c01::f03c:91ff:fe93:4b0d and that solved the issue,
that would be great.
Who can do this?
ssh into the host, from an ipv6 capable unit, and view its
ipv4 address to see which it is. Then ask the netblock
administrator -- OR use a web tool and make some guesses
It appears to be a linnode unit
http://ipv6now.com.au/traceme.php?page_id=36
1. 2406:a000::1
2
2. 2406:a000:ffff:ffff::1
2
3. ge-0-0-0-107.a06.sydnau01.au.ra.gin.ntt.net
4
4. xe-0-1-0.r05.sydnau01.au.bb.gin.ntt.net
3
5. p16-1-2-0.r02.lsanca03.us.bb.gin.ntt.net
148
6. xe-0-1-3.r21.lsanca03.us.bb.gin.ntt.net
139
7. ae-1.r20.snjsca04.us.bb.gin.ntt.net
150
8. ae-1.r07.snjsca04.us.bb.gin.ntt.net
149
9. 10gigabitethernet2-3.core1.sjc2.he.net
149
10. 10ge5-2.core1.pao1.he.net
152
11. 10ge4-4.core3.fmt2.he.net
150
12. linode-llc.10gigabitethernet7-6.core3.fmt2.he.net
152
13. 2600:3c01::f03c:91ff:fe93:4b0d
154
-- Russ herrold
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
was this resolved?
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
