Wow is that really icann messing with dns routing? theoatmeal.com uses DNS1.NAME-SERVICES.COM which is enom I think. Maybe enom reported something incorrectly

Wow is that really icann messing with dns routing? theoatmeal.com uses DNS1.NAME-SERVICES.COM which is enom I think. Maybe enom reported something incorrectly to icann, in fact I have to believe enom is at fault here somewhere because I cannot imagine icann pulling a whois on millions of domains. querying DNS1.NAME-SERVICES.COM for theoatmeal leads right back to enom Unfortunately he has multiple sites on one ip so they cannot be reached directly http://oatvip.gpdatacenter.com/ http://oatvip.gpdatacenter.com/ If you know what you are doing, you can send a HTTP_HOST of theoatmeal.com directly to that ip I don't think he is home right now, he is at w00tstock https://www.youtube.com/watch?v=Z6K_IQjkUbo&t=1m30s https://www.youtube.com/watch?v=Z6K_IQjkUbo&t=1m30s