I ran into a weird name lookup issue:

I have a host 134.79.23.45.
Its DNS name is sdfdtn005.slac.stanford.edu everywhere, except on the node itself.
On the node, its hostname is also the above, but an name lookup of the ip address will give sdfdtn005.sdf.slac.stanford.edu (note the .sdf.)
domain name .sdf.slac.stanford.edu is not known anywhere except on this host (and other nodes in SLAC's newest computing facility)
Don't ask why 3) and 4). it is politics.

When xrootd starts, it somehow associate the IP address to sdfdtn005.sdf.slac.stanford.edu.

a) using xrootd client in 5.5.0, after TLS, the client (xrdfs) will try to reach to sdfdtn005.slac. So all works
b) using xrootd client in 5.4.x, after TLS, the client (xrdfs) will try to reach to sdfdtn005.sdf.slac... this will fail because domain .sdf.slac.stanford.edu is not known to the outside.

I worked around this issue by manipulating /etc/hosts so that the IP address is associated to sdfdtn005.slac.stanford.edu

why these different behavior between xrootd 5.5.0 and xroot 5.4.x ?
how to prevent xrootd from associating 134.79.23.45 to sdfdtn005.sdf.slac (especially since its host name is sdfdtn005.slac)

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1787", "url": "https://github.com/xrootd/xrootd/issues/1787", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1