Hi,

I read about this place on Slashdot yesterday and signed up the same day; it looked like a great place. I've been impressed so far. However, there seems to be a problem with the reverse DNS; namely, for reverse DNS to work, you need to reverse the order of the octets in the IP address before appending the ".in-addr.arpa" suffix. For example, from a completely separate machine this is how it sees my Linode (which should be matrix.theblob.org, 66.220.1.230):

$ host 66.220.1.230
230.1.220.66.in-addr.arpa domain name pointer li4-230.members.linode.com.
$ host 230.1.220.66
66.220.1.230.in-addr.arpa domain name pointer matrix.theblob.org.

Obviously, this isn't right. From another computer it displays:

$ host 230.1.220.66
66.220.1.230.in-addr.arpa domain name pointer reserved-multicast-range-NOT-delegated.example.com.

I'm not sure what needs to be done to fix it, but presumably it's just a matter of reversing the octets in the IP address before setting the reverse DNS.

Thanks!

Oops. I think I just worked out what was up - it must be the router here that's faulty. I had initially done a "host matrix.theblob.org" before then and the router's DNS server must have looked it up and wrongly set a corresponding PTR entry corresponding to the IP in its cache. As you can see (many thanks to Slashdot for providing wildcarded DNS for this example ):

$ host ciaran-is-cool.slashdot.org
ciaran-is-cool.slashdot.org has address 66.35.250.151
$ host 66.35.250.151
151.250.35.66.in-addr.arpa is an alias for 151.0/24.250.35.66.in-addr.arpa.
151.0/24.250.35.66.in-addr.arpa domain name pointer star.slashdot.org.
$ host 151.250.35.66
66.35.250.151.in-addr.arpa domain name pointer ciaran-is-cool.slashdot.org.

Hey, I have my own subdomain with reverse DNS on slashdot!

Stupid router. *kicks it* Sorry, false alarm.