NXDOMAIN weirdness
root zone
$ host nonexistent-example.com
Host nonexistent-example.com.members.linode.com not found: 5(REFUSED)
If I try to resolve a bogus hostname that's not in the root zone hierarchy, I get an NXDOMAIN, as it should be.
$ host steve.jobs
Host steve.jobs.members.linode.com not found: 5(REFUSED)
$ host bill.gates
Host bill.gates not found: 3(NXDOMAIN)
My /etc/resolv.conf:
domain members.linode.com
search members.linode.com
nameserver 97.107.133.4
nameserver 207.192.69.4
nameserver 207.192.69.5
I definitely used to get all NXDOMAINs for these types of queries on this box. Any ideas?
4 Replies
'host' is doing the .members.linode.com. lookup for "bill.gates", too; it just doesn't tell you about it because it received an ordinary NXDOMAIN.
@mnordhoff:
For some reason, Linode's recursive nameservers return REFUSED for things like com.members.linode.com. 'host' thinks that's weird, so it returns an error.
OK, so that's what changed. The resolvers in the other Linode datacenters I have access to don't seem to be refusing those queries. Weird. Is this just Newark? Any way to fix this behavior, other than not using the linode search domain in resolv.conf?
I wonder why the resolvers are only refusing those queries where the most significant level under members.linode.com is in the root zone. I can't think of a good reason for it.
I'm not filing a ticket about it, though.