The correct response for a DNS server when a domain does not exist

domain-name-system

I've recently been noticing some "odd" behavior from my ISP's DNS server when resolving non-existent domain. It's been causing me some problems and I was wondering if these DNS servers are actually conforming to the standard.

It started with them adding the feature that if you request an incorrect domain, it directs you to a search page that they run. I guess this is useful for some people when web browsing, but it borks things up for other applications particularly if the search server has some other open ports such as SMTP.

To get round this, I changed preferences with my ISP to turn this feature off. Now my ISP's DNS does something lot stranger. When a domain can not be found, it returns MY own IP address as the A name for that non-existent domain. So now if I click a link which no-longer exists, it bounces me to my own home page (run through the same Internet connection).

I'm trying to understand why being bounced to my own IP address would ever be useful. More to the point, is this the standard or are they breaking the standard for some purpose best known to themselves?

Best Answer

Yes, your ISP is breaking the standard, but it is a common occurrence these days. Your ISP's DNS servers should be returning a NXDOMAIN response, or "Non-existent Domain".

If they are unable to do this, I would look at using external DNS servers like Google or OpenDNS, or running your own internal caching/resolving servers for your clients.

A note on OpenDNS, I believe you have to sign up for a business account to turn off NXDOMAIN redirection.