InCommon DNS Issues?

[Donald Lohr]

This would not have any thing to do with still using the old legacy 
metadata mechanism to get the whole metadata aggregate file would it:

http://md.incommon.org/InCommon/InCommon-metadata.xml

...in lieu of using their new MDQ metadata method 
(https://spaces.at.internet2.edu/display/MDQ/migrate-to-mdq)? With the 
new MDQ approach, to pull the full metadata aggregate, the url is this:

metadataURL="https://mdq.incommon.org/entities"

To manually command-line test both try from a Linux computer:

curl http://md.incommon.org/InCommon/InCommon-metadata.xml
curl https://mdq.incommon.org/entities

Don

On 4/20/22 5:17 PM, Ullfig, Roberto Alfredo via users wrote:
> *CAUTION: *This email originated from outside of JMU. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
> ------------------------------------------------------------------------
> Seeing these errors in our IDP logs:
>
> Metadata Resolver FileBackedHTTPMetadataResolver InCommon: Error 
> retrieving metadata from 
> http://md.incommon.org/InCommon/InCommon-metadata.xml: 
> md.incommon.org: No address associated with hostname
>
> 22 such events this month on one server. Anyone else see this?
>
> ---
> Roberto Ullfig - rullfig at uic.edu
> Systems Administrator
> Enterprise Applications & Services | Technology Solutions
> University of Illinois - Chicago
>

-- 
D o n a l d   L o h r
I n f o r m a t i o n   S y s t e m s
J a m e s   M a d i s o n   U n i v e r s i t y
5 4 0 . 5 6 8 . 3 7 3 0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20220421/0c1e8587/attachment.htm>