Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Mesh where same hostname has both A and AAAA records

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Mesh where same hostname has both A and AAAA records


Chronological Thread 
  • From: Brian Candler <>
  • To: "" <>
  • Subject: [perfsonar-user] Mesh where same hostname has both A and AAAA records
  • Date: Thu, 5 May 2016 17:58:26 +0100
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=to:from:subject :message-id:date:mime-version:content-type; q=dns; s=sasl; b=bSz 0rra9pyajvkMrP+2/MgSayfWYC8QI+/bs/yF3fJkmRzQd6xGvDLcVk5ZaYcmJ5ND hy2PS+93eTAkE/W/83D8m1zNfW1EKdIKVETv28lcmYnqpLlErJLSoxxniuPgvuCk 1/cBd1anNzA8D2QPVXlMBY6GTltecXruIWvKZPAY=

When I have a maddash mesh which includes hostX.example.com and hostY.example.com, and there are only A records for those names, it runs tests over V4 fine.

But when the names have both A and AAAA records, the tests only run on IPv6; the IPv4 tests stop. This is seen from looking at the collected graphs at the /toolkit/ home page. The v4->v4 and v6->v6 graphs are both listed, but the v4->v4 data stops at the time the AAAA records were added.

(I do realise that the dashboard itself is going to have difficulty rendering a single traffic light where there are multiple data sources, so perhaps that's the underlying cause of this behaviour)

So my question is: is running a maddash where the same hostname has both A and AAAA records not supported? Does this mean I need to create separate v4 and v6 hostnames, *and* create two separate meshes (i.e. one between the v4 interfaces and one between the v6 interfaces?)  Or is this likely to be allowed in future?

I can give some sample URLs off-list if required.

Regards,

Brian Candler.

P.S. Running latest perfsonar; these boxes auto-updated to 3.5.1




Archive powered by MHonArc 2.6.16.

Top of Page