Hmm. Did you get that via reverse DNS with a ping?server1.jesseangell.net
Cool!
Hmm. Did you get that via reverse DNS with a ping?
DANG!Very nicely done. And I'll admit, it wasn't all too inconvenient, even for me.
DANG!
Well, thats ok - we have ways of making your life miserable...
BTW it looks like pilotsofamerica.com (.org and .net) uses jesseeangell.net as the name server but the rDNS is served by serverbeach.com (66.139.72.5 and 64.34.160.71).Hmm. Did you get that via reverse DNS with a ping?
There are two servers dedicated towards PoA. They are physically located on opposite sides of the country with different providers. I may place PoA on a local server eventually--but local bandwidth is *way way* more costly. I need to get some measurements on PoA's usage before that is possible. But in the end..there really is little benefit to it being local.;; QUESTION SECTION:
;69.169.34.64.in-addr.arpa. IN PTR
;; ANSWER SECTION:
69.169.34.64.in-addr.arpa. 86400 IN PTR server1.jesseangell.net.
;; QUESTION SECTION:
;98.40.5.64.in-addr.arpa. IN PTR
;; ANSWER SECTION:
98.40.5.64.in-addr.arpa. 86400 IN PTR server2.jesseangell.net.
Jesse -
I had a hang up at 0814 CST when posting to a thread. The system "locked up" until I hit stop and then submit reply again. The reply posted but I got an error about a double post.
It happened again when posting this message at 0817.
BTW it looks like pilotsofamerica.com (.org and .net) uses jesseeangell.net as the name server but the rDNS is served by serverbeach.com (66.139.72.5 and 64.34.160.71).
I am assuming this is not a dedicated machine so I can't think of an obvious solution.
Joe
Well Mike the point I was trying to make is that if he has multiple servers on the same machine with one ip address he may want the rDNS to point to his domain not PoA's.It is a dedicated machine and what difference does it make who serves the DNS? It could be running in Bosnia. DNS servers are supposed to be geographically diverse by design.
It also doesn't matter if reverse DNS and DNS are on seperate servers, in separate countries, or planets and far from the web servers as long as the service works.
BTW it looks like pilotsofamerica.com (.org and .net) uses jesseeangell.net as the name server but the rDNS is served by serverbeach.com (66.139.72.5 and 64.34.160.71).
I am assuming this is not a dedicated machine so I can't think of an obvious solution.
Joe
Well Mike the point I was trying to make is that if he has multiple servers on the same machine with one ip address he may want the rDNS to point to his domain not PoA's.
As far as who administers the rDNS, if it's Jesse he edits a file and does a kill -HUP, but if it's his ISP he has to contact them. I'm not sure how I implied they should be at a single location.
Other than that thanks for the insight.
Joe
I see other activity that was successful during that time period. It was most likely that the problem was either with your ISP or with a hop between the two. I can't fix the whole internet. Or maybe I can...
Not quite Mike. There is no reason to have the rDNS match the forward of the web domain. We live in an era of multiple ip addresses per web domain and that is enforced strongly by ARIN. With the exception being for SSL. PoA is not running anything via SSL. You'll find that there are few websites out there with rDNS matching the forward.You've got a point - that the RDNS and forward should have the same name - because some spam killers will assign the spam score on whether the reverse DNS matches the domain in the email, as well as AFIAK, things like whether an SSL certificate is for the right site.
I concur with Jesse. DNS (forward and reverse) are set up exactly as they need to be. There will be no ill effects from a lack of rDNS that references PoA.
Things are running very smoothly so far. Let's trust him...
dittoYep. It was a minor point.
Over a year later--website still remains fast.