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 ;; 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.. ;) /mjt