With that being said, I think the biggest issue (DNS resolution) was related to the anycast code we committed. I already got some changes in testing and I'll be merging them today.

* Reverse DNS

I have a learn-address script to generate the DNS entries on connection, but no idea on how I would make it work with such a setup. If both links are up, then the link with the least packetloss and l

(Quote)

We've narrowed it down to not being DNS related already.

(Quote)

The only thing I can think of is that this particular computer maybe has a custom DNS server set that is causing this problem..

Have you cleared your caches/flushed dns etc?

(Quote)

Use ping6

(Quote)

IPV6 is enabled. I am on DHCP but using manual DNS.

ClamHost has been in business for over a year!We own most of our hardware.Automatic rDNS updatesDNS Management availableSecondary Private Network IncludedFriendly and Knowledgeable Support

(Quote)

You can't typically run dns or mail services off shared ipv4 nat servers unless your host is nice enough to assign you the standard ports.

This is a measure they take to "prevent abuse". It make more sense logically if they blocked SMTP on the smallest plan entirely and allow rDNS vs what they do now.

* They do not provide reverse DNS for their smallest two bundles. Their third bundle is $16/month (but on sale right now for $8/month) so this is not necessarily a show-stopper.

It was brought to my attention last week that an RDNS XSS could exploit LookingGlass.

We have several useful tools at solvedns.com. My favorite is the dns speed test. Let me know what you think! (Image)

https://github.com/trick77/tunlr-style-dns-unblocking