I don't see what is wrong. They have been running the root servers for too long and they are now trying to make some money out of it.
Huh? They have not been running the root name servers for free! AFAIK, every registrar has to pay them for every domain registered under .com/.net. I think it's $6/pop...
And they only do it for invalid domains. It is much better than pop up ads in flash that cover the screen.
I can turn those off, for e.g. in an application like Mozilla or using add-ins for IE. I can't turn this off, without significant effort.
I would think this is a legitimate way of making money.
Slashdot has a an article:
http://slashdot.org/articles/03/09/19/039214.shtml?tid=123&tid=126&tid=95&tid=99
Basically, a cybersquatting company - Popular Enterprises LLC, is suing VeriSign for this move. How *legitimate* is your business if you are being sued by a cybersquatter?
The issue of technical problems cropping up due to this also looks exaggerated to me. Clearly, any danger to SMTP servers can not be a concern as they would probably add wildcards for "A" type record and not "MX" records.
Here's a sample email I had sent:
----- The following addresses had permanent fatal errors ----- <[EMAIL PROTECTED]>
----- Transcript of session follows ----- ... while talking to tarunpadhyay.com.:
>>>>>> RCPT To:<[EMAIL PROTECTED]>
<<< 550 User domain does not exist. 550 <[EMAIL PROTECTED]>... User unknown
Now, how do you expect a non-technical user to interpret this?
-> Call you and ask what happened to your domain? -> Ask his support department? -> Assume he has the wrong address and try again?
Can somebody more knowledgeable enlighten me on what kind of things I can expect to break because of this from a system administration point of view and how can they be repaired. (just the facts please, not the rhetoric).
Let's consider some other problems:
-> SMTP: As above
-> HTTP:
---> Much more traffic across the Internet. Whereas earlier there would have been just a NXDomain DNS query result, now the entire site would be downloaded.
---> Scripts which used domain lookup faliures to do interesting things would break. E.g. A company uses a script to check the expiration of it's own domains.
-> Other protocols:
---> Take telnet for example:
----> A domain lookup would have failed faster, but now a typo means that I end up waiting for a couple of minutes before being told "Connection timed out".
----> More Traffic. Syn packets would be sent, which would not have been earlier. Not a problem for an individual site, but consider the overall traffic increase on the Internet.
Also, the problem is that domains not resolving is a key method for troubleshooting problems. Say some user has misconfigured their mail client...now they would call up the support chaps saying that they are getting a "Connection refused" message instead of "Domain not found". How easy would it be for the support people to diagnose this?
Regards, Varun Varma, --------------------------------------------- Mindframe Software & Services Pvt. Ltd., A-50, Sector-39, NOIDA, U.P. - 201301, India
http://www.mindsw.com ---------------------------------------------
_______________________________________________ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
