immediate positive benefit is that it's no longer possible for
someone to hold a given IP address hostage by registering a name server at
that address. (Anyone can register a com/net/org name server at any IP
address.)
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Global Registry Services
; 24 hours per day, so if it's a real emergency
you can always contact them or activate the bat signal with a posting
on NANOG, which is also read here throughout the day.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
24x7 customer service
department contacted Dotster and Melbourne IT. Melbourne IT changed
the panix.com name servers back to their original settings and
transferred the domain back to Dotster.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
problem, but could be. but it is a problem.
a.gtld-servers.net and b.gtld-servers.net have records. Some
applications and stacks try the v6 address first if it's available and
will appear to hang if you don't have v6 connectivity. That may very
well be what's happening here.
sponder who isn't known to support them be allowed a retry with
no extensions if it responds with such an RCODE. [...]
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
use
it is referenced at least one NS record also in the com and net zones,
i.e., it appears on the right side of an NS record.
This is the case with www.stemtostern.com. While it is not a name
server for stemtostern.com, it is a name server for
harbormarinetowing.com; please see the dig output belo
t: those are the only registrars
that I have definitive information on. The only way to know for sure
about your registrar is to ask them.
Please let me know if I can be answer any other questions or otherwise
help you out.
Kind regards,
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Global Registry Services
umably Network Solutions
took this action based on customer instructions, but you'd have to ask
them.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Global Registry Services
bout rapid updates for .com/.net are
available at http://www.verisign.com/nds/naming/rapid_update/faq.html.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
[1] http://www.merit.edu/mail.archives/nanog/2004-01/msg00115.html
[2] http://www.verisign.com/nds/naming/tld/
On Fri, 09 Jul 2004, Robert Boyle wrote:
> Does this also apply to domains with other registrars?
I'm not sure what you mean by "other registrars". VeriSign sold the
Network Solutions registrar in November 2003 (although it retains a
15% ownership).
The rapid updates apply to all changes from a
persons
> concerned with dns technical support worldwide should be done.
With over 7000 subscribers (if I'm remembering the numbers from
Susan's latest statistics slide correctly), NANOG covers more than
just routing in North America: a posting here reaches Internet
operators worldwide. Indeed, my original posting has already appeared
in other places. But your point is well taken.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
this is an education
issue. Does anyone want to co-author an Internet-Draft on the topic
of choosing appropriate TTLs?
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
rver placement, especially in
the BGP case.
For what it's worth,
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
because these zones are widely used and closely watched, we want to
let the Internet community know about the changes in advance.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
On Mon, 20 Sep 2004, Matt Larson wrote:
> VeriSign will add support for accessing the com/net zones using IPv6
> transport on October 19, 2004. On that day, records for
> a.gtld-servers.net and b.gtld-servers.net will be added to the root
> and gtld-servers.net zones.
&g
h "jns6" are
> just the individual servers of a setup called "hgtld".
Correct. At the moment, most J root instances are colocated with
com/net name servers. The instance you're reaching is colocated with
h.gtld-servers.net, which is in Amsterdam.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
esses not in that form it would be great.
While I'm not with Network Solutions, I'll pass your email on to a
clueful person there and report back whatever I hear.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
est to the NANOG
community, is available here:
http://www.verisign.com/resources/gd/sitefinder/bestpractices.pdf
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
. Another option is
remaining with the more standard SMTP sequence (returning 250 in
response to HELO/EHLO), but then returning 550 in response to MAIL
FROM as well as RCPT TO.
I would welcome feedback on these options sent to me privately or the
list; I will summarize the former.
Matt
--
Matt Lars
Saturday, October 4. The former behavior for these
zones (returning Name Error/RCODE=3 in response to queries for
nonexistent domain names) will be in place by 0100 UTC on Sunday,
October.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
e 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 th
On Fri, 09 Jan 2004, Robert E. Seastrom wrote:
> I'm just hoping that the choice of a time_t as serial is not a
> harbinger of djbdns in the gtld servers...
No. All 13 .com/.net name servers now run ATLAS (and have for just
over a year), our own from-scratch DNS server implementation. Nothing
e
connection with provisioning
of authoritative name service for orkut.com.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Naming and Directory Services
notice to anyone who may have to update
processes that parse this output.
A sample of the revised output is included at the end of this message.
Matt
--
Matt Larson <[EMAIL PROTECTED]>
VeriSign Information Services
[Sample output follows.]
Whois Server Version 2.0
Domain names in the .c
On Sat, 19 Jan 2008, Randy Bush wrote:
> >I don't know what the process is for getting IPv6 addresses associated
> >with host records in the VGRS COM/NET registry, but it seems like good
> >information to share here if you find a definitive answer.
>
> i will. i am trying to document ops proce
On Wed, 23 Jan 2008, Christopher Morrow wrote:
> >o netsol understands glue
>
> REGISTRY part of NetSol here, I think David means the REGISTRAR part no?
To my knowledge, there is no registry part of Network Solutions.
Network Solutions and VeriSign are two distinct companies with
distin
26 matches
Mail list logo
