Slashdot Mirror


Verisign Plans DNS Changes

NetWizard writes "According to a recent NANOG post and an InfoWorld story, 'Verisign will change the serial number format and "minimum" value in the .com and .net zones' SOA records on or shortly after 9 February 2004'. They seemed to have learned their lesson, from the post: 'There should be no end-user impact resulting from these changes (though it's conceivable that some people have processes that rely on the semantics of the .com/.net serial number.) But because these zones are widely used and closely watched, we want to let the Internet community know about the changes in advance.)'"

6 of 161 comments (clear)

  1. Stop Changing DNS by Blackknight · · Score: 3, Insightful

    God damn it ICANN, you need to take away Verisign's authority over DNS. Every time they change something it's a major pain in the ass for anybody that works in an ISP, web hosting, etc.

    STOP FUCKING CHANGING THINGS!

    1. Re:Stop Changing DNS by Anonymous Coward · · Score: 5, Insightful

      How the hell will this be a pain in the ass? Any software that relies on .com's serial number remaining static is broken and needs to be fixed. Complain to the software developers, as Verisign is not at fault this time.

    2. Re:Stop Changing DNS by CarrionBird · · Score: 3, Insightful

      Maybe, but everything is working now, and there's no reason to change it other than breaking these "broken" programs.

      --
      Free Mac Mini Yeah, it's
    3. Re:Stop Changing DNS by jrumney · · Score: 4, Insightful

      Reading between the lines, it looks to me like Verisign want to start providing real time DNS updates, in which case there is a reason for change it. Currently they update the database twice a day, which is well within the limits of the current serial number scheme. But with real time updates, they could easily get to 100 updates in a day.

  2. Hey... by Neophytus · · Score: 5, Insightful
  3. Re:Serial number format by Trillan · · Score: 3, Insightful

    This looks like a good change to me. I can't imagine there would be an outcry over this if Verisign hadn't previously implemented the SiteFinder dung.