FS#15871 - Sigurd rDNS

Attached to Project: Arch Linux
Opened by Florian Pritz (bluewind) - Sunday, 09 August 2009, 11:36 GMT
Last edited by Aaron Griffin (phrakture) - Monday, 10 August 2009, 19:55 GMT
Task Type Bug Report
Category Web Sites
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The rDNS of sigurd.archlinux.org is broken.

nslookup sigurd.archlinux.org -> 208.92.232.29 -> client-208-92-232-29.sevenl.net
-> NXDOMAIN
This task depends upon

Closed by  Aaron Griffin (phrakture)
Monday, 10 August 2009, 19:55 GMT
Reason for closing:  Fixed
Comment by Aaron Griffin (phrakture) - Monday, 10 August 2009, 18:23 GMT
I guess I'm a little confused what you'd like us to do here. This is a donated server and a large portion of what happens with it is not under our control. What solution are you expecting?
Comment by Dan McGee (toofishes) - Monday, 10 August 2009, 18:36 GMT
The point is quite valid, and one of two things should happen here (and I don't see SevenL giving us a hard time about either):

1. Get the RDNS entry for 208.92.232.29 to point to something like "sigurd.archlinux.org."
2. As the RDNS entry for 208.92.232.29 points to "client-208-92-232-29.sevenl.net.", the forward DNS entry should point back to that IP address as well.

If you shoot our contact an email, I really think this will take about 2 seconds to fix from their end. We can't control RDNS, only regular DNS, so this is out of our hands.
Comment by Aaron Griffin (phrakture) - Monday, 10 August 2009, 19:29 GMT
Ok should be fixed now. Please confirm when things propagate
Comment by Florian Pritz (bluewind) - Monday, 10 August 2009, 19:51 GMT
Works here thank you.

Loading...