Bug Reporting Thread

We had that problem yesterday.Percy fixed it this morning. Then Brad broke it again.

Could the be spam filtering (at your site) that has run awry?

There appears to be no rDNS (reverse DNS) for 72.4.161.195. That is, a lookup of the IP address does not return a hostname. Instead, it returns status: NXDOMAIN, indicating that there is no entry in DNS for that name.It is becoming increasingly common for mail servers to refuse email from sites with no rDNS.The failed DNS lookup references ns1.primarydns.com as the responsible DNS server, and the hostmaster at primarydns.com as the responsible person, for handling an rDNS entry.

May I suggest that you edit out Brian's email address from your post. Maybe replace with ****@****Brian might not be getting our email. But the spammer address harvesting web crawlers will get his email address, and increase the amount of spam he gets.On my count, his address appears 4 times.

Forward DNS seems fine. The MX record (used for email) looks fine.I just tried connecting to the mail server. That worked fine. I manually ran through the SMTP protocol for sending mail, but QUIT before entering a message. That all looked fine to me.If you like, I can try sending you a test message.

I'm willing to help where I can (subject to time availability). I don't have any experience with primarydns.com. The actual record that would need to be in DNS is The zone 161.4.72.in-addr.arpa. does already exist, served by primarydns.com, so they presumably do have a way of handling this.

In unix, you can use

% dig -x 72.4.161.195

That is still saying NXDOMAINIf you don't have a dig command, then

% nslookup
    > set type=ptr
    > 195.161.4.72.in-addr.arpa
    > exit

That (nslookup) probably works on windows, too. Note that you have to use the IP address backwards when using nslookup.You can try with a different IP address, say that of yahoo.com, to see what you should get.Sorry for slow reply. I was at meetings.

I think they have now un-deprecated it, so future versions will stop giving that warning.In any case, "dig" is easier to use. Forward map:

207.36.231.74
    207.36.231.74

Reverse map:

207.36.231.74     207-36-231-74.ptr.primarydns.com.

That's better than no reverse map. It would be better still if the reverse map gave the name (or one of its variants, such as dedicated.).Hmm, the software is turning a hostname that begins "www" into a url link, even inside a code block.

I checked with

% dig @ns1.primarydns.com -x 207.36.231.74

That makes the request directly at the official DNS server for that lookup. When looking up that way, there should not be any latency issues.

I have noticed this before, but never got around to reporting it as a bug.I see the edit time reported as 9:20 pm.You have a great time machine there, Chiropta. You are editing the message 5 hours in the future It seems to me that the edit time should always be recorded in the default time, OR the timezone use in the edit time should be included. Otherwise these edit times can be confusing.

On the bottom of a forum page, I find the notation "SiteMap".
I follow that link. Then I see a bunch of links, including one for "Technical FAQ". If I click on that, I get The same thing happens for a bunch of other links on that SiteMap page.

I'm not sure whether there is a problem or not, but forum pages are currently taking an unusually long time to load.

No, it is clearly not imagination.I am seeing brief periods with a ping time (to ) of 64 ms, and 100 packet response. I am seeing long periods of 111 ms ping time, and 50% or higher packet loss. Steiner62 appeared to be having similar problems in Help me understand Intelligent Design (part 2)It looks to me like a DoS attack, or perhaps a failing router. Since others are not all seeing the problem, the attack might not be on EvCforum itself, but on an ISP through whose routers my path goes. A "tracert" shows a path through some cogentco.com routers, so the problem might be there.

This problem continues.EvCforum really sucks at present. I realize it is not your fault, and there might not be much you can do about it.It appears to be a problem with cogentco routers. People whose path to EvC goes via cogentco are having problems. On chat last night, Chiroptera mentioned that he was having problems.I believe I have loaded Message 253 at least 4 times. It is still showing the blue light that indicates I have not read it. The browser page loads are not completing properly, so cookies are not updating.As I type this response the indicator still shows my browser as loading this reply page -- it just finished (maybe due to a timeout). Now I can start counting how many tries it will take before my reply is properly submitted.

Things improved dramatically in the last 30 minutes or so.Page loading speeds are now back to normal.A "traceroute" shows that my route to evcforum no long goes via cogentco.This is from my work machine. I will recheck from home, when I get there.