nanog mailing list archives
Re: Change to .com/.net behavior
From: Roy <garlic () garlic com>
Date: Mon, 15 Sep 2003 17:29:43 -0700
It looks like it broke. Your web server (64.94.110.11) is inoperative. How about backing out the change!!!!
Matt Larson wrote:
Today VeriSign is adding a wildcard A record to the .com and .net zones. The wildcard record in the .net zone was activated from 10:45AM EDT to 13:30PM EDT. The wildcard record in the .com zone is being added now. We have prepared a white paper describing VeriSign's wildcard implementation, which is available here:http://www.verisign.com/resources/gd/sitefinder/implementation.pdf
.....
Current thread:
- Re: Change to .com/.net behavior, (continued)
- Re: Change to .com/.net behavior Jared Mauch (Sep 15)
- Re: Change to .com/.net behavior Adam 'Starblazer' Romberg (Sep 15)
- Re: Change to .com/.net behavior Jared Mauch (Sep 15)
- Re: Change to .com/.net behavior Steve Gibbard (Sep 15)
- Re: Change to .com/.net behavior Mark Radabaugh (Sep 15)
- Re: change to the COM and NET TLD Neil J. McRae (Sep 16)
- Re: change to the COM and NET TLD Rafi Sadowsky (Sep 16)
- Re: change to the COM and NET TLD Karsten W. Rohrbach (Sep 16)
- Re: Change to .com/.net behavior Jay Hennigan (Sep 15)
- Re: Change to .com/.net behavior Michael Tokarev (Sep 15)
- Re: Change to .com/.net behavior David B Harris (Sep 15)
- Re: Change to .com/.net behavior David B Harris (Sep 15)
- Re: Change to .com/.net behavior David B Harris (Sep 15)
- Re: Change to .com/.net behavior David B Harris (Sep 16)