Greetings everyone, Due to a breathtaking number of new compromised PCs hitting our primary and secondary mail hubs, we are now rejecting e-mail from hosts that have no reverse lookup, or a bogus reverse lookup. This means that if the IP address of your mail server does not have a legitimate reverse “PTR” record, we […]
Blog
Updated: Members site maintenance: February the 7th 2009
UPDATE: We are pushing this update to February the 7th 2009, at 10:00pm EST Original notice below; Greetings, On Saturday January the 31st, 2009, at 10:00pm EST, the EasyDNS admin team will be doing maintenance on our retail members interface. This maintenance will impact members site access and dynamic DNS requests. DNS queries, mail flow, […]
Wango Tango!!! TedNugent.com – are you kidding me?
One of the things I love about this business is finding out some of the ultra-cool websites who use us for DNS. The first couple years of this business I think I had every domain name on the system memorized, not so much now. But I found out today that TedNugent.com uses easyDNS nameservers ROCK […]
Relay of email to AT&T mailservers…
We are aware of an issue with our primary mailservers relaying email forwarded emails to destination email addresses within the AT&T network due to a block on their end. Affected destination email address domains are: @bellsouth.net @sbcglobal.net @pacbell.net @att.net @ameritech.net @swbell.net @prodigy.net @snet.net Our sysAdmins have routed email to non-affected mailservers which will allow email […]
Why we do not offer Whois masking at easyDNS
Update: we have since flip-flopped on this. Please See: The Official easyDNS Flip-Flop on Whois Privacy. We get asked this a alot: Why do you guys not offer whois masking or whois contact privacy? The brief background on this is: whenever you register a domain name, your contact details are published in a publicly visible […]
Update: re ns2 timeouts
The issues we experienced with timeouts when querying ns2.easydns.com were cleared up as of approx 3:45pm(EST) on Tuesday Nov 11. We are still working with our provider to determine the root cause of the issue.
