enom/name-services.com nameservers are severe broken

Wed Mar 9 11:48:09 UTC 2005

Michael Tokarev wrote:

> And this is Very Wrong (tm):
>
> $ host -t cname -v name-services.com. dns1.name-services.com.
> Host name-services.com not found: 3(NXDOMAIN)
>
> In short: for *some* types of records for a valid name, the server
> returns NXDOMAIN, which it should not be.
>
> Obviously, when doing this query using a caching nameserver, the
> cache gets poisoned (remembering that the domain in question
> does not exists, as opposed to "No data of requested type"
> response).
>
> Another example for a domain hosted by them:

And as an example of the issue:

$ host -t ns name-services.com.
name-services.com name server dns4.name-services.com.
name-services.com name server dns5.name-services.com.
name-services.com name server dns1.name-services.com.
name-services.com name server dns2.name-services.com.
name-services.com name server dns3.name-services.com.
$ host -t cname name-services.com.
Host name-services.com not found: 3(NXDOMAIN)
$ host -t ns name-services.com.
Host name-services.com not found: 3(NXDOMAIN)

Regards,

Mat