enom/name-services.com nameservers are severe broken

Mailman List Mirror (Read Only)
1

Just noticied a weird behaviour of dns?.name-services.com nameservers.
Here it goes (there are several problems, pls read the whole this
message):

$ host -t a -v name-services.com. dns1.name-services.com.
this gives normal answer (details skipped):
name-services.com. 7200 IN A 63.251.163.109

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:

$ host -t a -v jandg-cooper.com. dns1.name-services.com.
NXDOMAIN

$ host -t mx -v jandg-cooper.com. dns1.name-services.com.
jandg-cooper.com. 3601 IN MX 10 cooper-linux.jandg-cooper.com.

This happens with CNAME and A records so far, eg asking for
AAAA record returns proper reply with empty answer section.

And here's another brokeness:

$ host -t ptr -v jandg-cooper.com. dns1.name-services.com.
;; Warning: ID mismatch: expected ID 15165, got 0

It returns "proper" (fsvo) reply but with wrong ID.

Reportedly there's some (pretty legal) query which returns SERVFAIL
but I can't reproduce it now.

All dns?.name-services.com behaves the same way.

I think it should be fixed ASAP.. :wink:

/mjt

2

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

3

Michael Tokarev wrote:

Just noticied a weird behaviour of dns?.name-services.com nameservers.
Here it goes (there are several problems, pls read the whole this
message):

name-services.com. 3600 IN SOA dns1.name-services.com. info.name-services.com. 2002050701 10001 1801 604801 181

So for contacts, info@name-services.com should be used.
Ofcourse it does not work due the same reason (as asking
for name-services.com MX returns NXDOMAIN thus poisoning
the cache), and due to the fact that there's no SMTP
listener on 63.251.163.109 (connection just times out).

Re-sent to {info,postmaster}@enom.com, pointing out to
yet another problem... after flushing our NS cache.

Lovely.

/mjt

4

Big Wave Dave wrote:

I have seen a coupld different domains using their services be
similarly affected. Sending them an email would result in a bounce
marked "domain not found". It has been periodically occurring since

The bounce/"domain not found" is exactly due to this problem with
returning NXDOMAIN in the wrong place. I used plain SMTP in telnet
to send them email :wink:

November. By the time you track someone down that can fix it... it
has magically corrected itself.

Well.. For me, it's just "Not My Problem (tm)". And no, the problem
is still here :wink:

/mjt