Re: Change to .com/.net behavior
While I too am outraged by the actions of Verisign, I've decided to NOT modify my servers in any way. I might decide to block the sitefinder IP, but I will not change my nameservers into modifying DNS responses. Doing so would be to break things,
*You* cannot modify DNS responses, but it's okay for Verisign to do so? Steinar Haug, Nethelp consulting, sthaug@nethelp.no
While I too am outraged by the actions of Verisign, I've decided to NOT modify my servers in any way. I might decide to block the sitefinder IP, but I will not change my nameservers into modifying DNS responses. Doing so would be to break
From: <sthaug@nethelp.no> things,
*You* cannot modify DNS responses, but it's okay for Verisign to do so?
No. However they are NOT modifying DNS responses. The responses are perfectly valid results of having a wildcard in the zone. The thing is, they have decided to make ALL second level domains in the com and net zones exist, regardless of wether they are registred or not. This is a policy breakage that I'm not pleased with at all. It is, however, very important to realise the difference between breaking policy and breaking technology. - Kandra
Kandra didn't say that they CANNOT modify DNS responses, just that they were not going to. william ----- Original Message ----- From: <sthaug@nethelp.no> To: <kandra@foxette.net> Cc: <nanog@merit.edu> Sent: Wednesday, September 17, 2003 1:13 PM Subject: Re: Change to .com/.net behavior
While I too am outraged by the actions of Verisign, I've decided to NOT modify my servers in any way. I might decide to block the sitefinder IP, but I will not change my nameservers into modifying DNS responses. Doing so would be to break
things,
*You* cannot modify DNS responses, but it's okay for Verisign to do so?
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
participants (3)
-
Kandra Nygårds -
sthaug＠nethelp.no -
William Devine, II