Let me say this again for the both of you. "Improves DNS server performance". If a DNS client is written to expect a 404 error than it is the developer who is cracked.I fail to see how such an application can adversly impact a client. One of the other posts did bring up an exception. For spam checking software they do a DNS lookup on the sender domain to verify that the domain exists. Fourtunatly this is a MX record lookup and I doubt this application is touching MX records as these would have no reason for a redirect. In no way would such an application "break" the RFC ( I have read alot of RFCs my favorites are RFC986 and RFC 3514). Applications like this and all the others take advantage that the clients and servers are RFC compliant in order to function. There are no "DNS" standards to break. The RFCs a very vauge to begin with and are more of guidlines to begin with.
The funny part of this argument is this service and others like it actually improves your DNS performance. Normally when a DNS lookup fails, the client will retry before giving up and displaying page not found. With this type of service in place the DNS service only sees one failure because the failed message is intercepted or replaced with a redirect to a search page. These types of services actually reduce overall traffic on DNS servers. I am all for faster DNS. Right now I am not annoyed by it anymore than the default MSN search, yahoo toolbar, google, AOL and others that do the same thing.
Let me say this again for the both of you. "Improves DNS server performance". If a DNS client is written to expect a 404 error than it is the developer who is cracked.I fail to see how such an application can adversly impact a client. One of the other posts did bring up an exception. For spam checking software they do a DNS lookup on the sender domain to verify that the domain exists. Fourtunatly this is a MX record lookup and I doubt this application is touching MX records as these would have no reason for a redirect. In no way would such an application "break" the RFC ( I have read alot of RFCs my favorites are RFC986 and RFC 3514). Applications like this and all the others take advantage that the clients and servers are RFC compliant in order to function. There are no "DNS" standards to break. The RFCs a very vauge to begin with and are more of guidlines to begin with.
The funny part of this argument is this service and others like it actually improves your DNS performance. Normally when a DNS lookup fails, the client will retry before giving up and displaying page not found. With this type of service in place the DNS service only sees one failure because the failed message is intercepted or replaced with a redirect to a search page. These types of services actually reduce overall traffic on DNS servers. I am all for faster DNS. Right now I am not annoyed by it anymore than the default MSN search, yahoo toolbar, google, AOL and others that do the same thing.