DNS should support in-addr.arpa and other stuff
Bug #332408 reported by
Geoffrey Thomas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Invirt Project |
Fix Released
|
Undecided
|
Unassigned | ||
| XVM |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Even if we don't have reverse-resolution delegated yet, we should still support manually looking up things against xvm.mit.edu.
Also, we should support HINFO, TXT, and RP records of some sort, so I can figure out who owns a machine, what their comment is, and possibly what type of machine it is. (HINFO can be populated best-effort by the choice of install CD or autoinstall). See RFC 1183 for more information about the RP record, and RFC 1033 for comments on the others.
| Changed in xvm: | |
| status: | New → Invalid |
Revision history for this message
| Evan Broder (broder) wrote | #1 |
| Changed in xvm: | |
| status: | Invalid → Won't Fix |
| Changed in invirt: | |
| status: | New → Won't Fix |
| status: | Won't Fix → Fix Released |
Revision history for this message
| Evan Broder (broder) wrote | #2 |
| Changed in xvm: | |
| status: | Won't Fix → Fix Released |
To post a comment you must log in.
I'd be fine with exposing contact information over DNS, since we plan to expose it over Moira anyway. I'm less OK with exposing information about a machine's configuration, since it seems like a privacy violation - more so than what's in Moira, since we usually just guess "IBM/PC/SOMETHING" anyway.
As far as contact goes, is RP actually used in deployment anywhere? The Moira dump certainly doesn't use it, and neither does the mit.edu root. I think I'd rather block on getting Moira integration figured out, which should be fairly easy to integrate into SQLAlchemy if we ever get to a point that you can use PyMoira on a 64-bit system.