|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Wed, 7 Nov 2001 14:07:15 -0800 From: Adam McKenna <adam-nanog@flounder.net> To: nanog@merit.edu Message-ID: <20011107140715.M2055@flounder.net> Mail-Followup-To: nanog@merit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <NDBBKECCEHKIHGIMJECAEEEMCLAA.vivienm@dyndns.org> Mail-Copies-To: never Errors-To: owner-nanog-outgoing@merit.edu On Wed, Nov 07, 2001 at 04:14:18PM -0500, Vivien M. wrote: > You can get quirky situations, though, because the NSI registrar division > does not update its database of registered name servers from the NSI > registry. Yes, this is correct. However, it doesn't matter what info NSOL has. If the "host record" they're using matches up with something that's registered in Internic WHOIS, then the GTLD servers will use the correct info when updating the glue records in the SOA. The only effective symptom of having the wrong info in the NSOL WHOIS is annoyance and confused customers. For a real-life example of this, try: $ whois nanovention.com then try $ dig @a.gtld-servers.net nanovention.com soa --Adam
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |