Serve the site directly at bdata.uw.edu

[advaitmb]

https://bdata.uw.edu/ currently resolves to the UW host 128.208.3.117, which returns a permanent redirect to https://behavioral-data.github.io/. GitHub Pages currently has no custom domain configured.

To keep bdata.uw.edu in the address bar, coordinate this cutover with the UW DNS/web administrator:

• Replace the current A record / Apache forwarding setup with a CNAME record from bdata.uw.edu to behavioral-data.github.io.
• Configure bdata.uw.edu as this repository's GitHub Pages custom domain immediately after the DNS change.
• Change content/site.json and production documentation to use https://bdata.uw.edu as the canonical URL.
• Deploy master, wait for GitHub's TLS certificate, and enforce HTTPS.
• Verify that https://bdata.uw.edu/ serves the site without redirecting away, and that the GitHub Pages URL redirects to the custom domain.

Do not configure GitHub Pages before coordinating the UW change: with the current UW redirect, that can create a redirect loop.

References: GitHub Pages custom-domain documentation, UW URL forwarding documentation.

[advaitmb]

Ownership check on September 11, 2026:

• bdata.uw.edu has an A record for 128.208.3.117.
• Reverse DNS identifies that address as new-rumble.cs.washington.edu.
• bdata.cs.uw.edu is a CNAME to the same Allen School server.
• Its TLS certificate covers both names, and both currently return the same 301 redirect to https://behavioral-data.github.io/.

This points to Allen School CSE IT as the appropriate first contact. Their published support address is support@cs.washington.edu; their main support page also provides a support-request link and phone number. Ask them to replace the bdata.uw.edu A record / Apache forwarding rule with a CNAME to behavioral-data.github.io, and to coordinate the change time so the GitHub Pages custom-domain setting can be enabled immediately. bdata.cs.uw.edu can then redirect to the canonical https://bdata.uw.edu/ if that alias should remain.

UW's Networks Portal also permits authorized administrative contacts to manage A and CNAME records directly. If the relevant CSE contact group is visible there, its administrator can make the DNS change; otherwise CSE IT should handle or route the request.

Sources: https://www.cs.washington.edu/who-we-are/lab/ and https://uwconnect.uw.edu/it?id=kb_article_view&sysparm_article=KB0034270