All things related to multicast

[(Kevin C. Almeroth)]

>>To: 
>>
>>Subject: Beacons, in-addr.arpa and forward-DNS
>>From: Havard Eidnes 
>><>
>>Hi,
>>
>>I started looking a bit closer at the accessgrid beacon multicast
>>reachability status, with a view towards finding out what is causing
>>some of the reachability problems my beacon is experiencing.
>>
>>I noticed that the accessgrid beacon status page now hsa 5 beacons
>>which apparently do not have an in-addr.arpa DNS registration, which
>>looks a little lame.
>>
>>Furthermore, I found at least two beacons that I have connectivity
>>problems with (nephilim.sprintlink.net and vogt.sprintlink.net)
>>where there does not exist a name-to-IP-address mapping for these
>>names.  Needless to say, this creates somewhat of a problem when it
>>comes to debugging the connectivity problems from my end of things.
>>
>>Furthermore, it appears that the user/host combinations are similar
>>to e-mail addresses -- I assumed that is the intent.  I'll however
>>bet that attempts at sending e-mail to the beacon identifiers would
>>generate quite a number of bounces, something which again makes
>>debugging more difficult than it otherwise can be.
>>
>>
>>I'll therefore appeal to those of you who run beacons on the
>>accessgrid group to at least make sure that reverse *and* forward
>>mappings for the beacon IP addresses are consistent with reality,
>>and that such mappings exist.
>>
>>I'm not sure about whether it should be possible to send e-mail to
>>the beacon identifiers (for what it's worth, it is possible to send
>>e-mail to my beacon identifier).
>>
>>Secondly, I would like to get in touch with the administrator of the
>>sprintlink.net participant beacons, to get the IP addresses of the
>>participating beacons, and so that we can (off-line) look into what
>>is causing our connectivity problems; pointers or replies
>>appreciated.
>>
>>Best regards,
>>
>>- Håvard
>>
>>
>>