Whois data for name server is incorrect
Michael Kjorling
michael at kjorling.com
Wed Jun 20 22:11:05 UTC 2001
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I would take care to ensure that all data that relates to a domain is
up-to-date at all times, including whois. If you cannot update this
using Network Solution's automated systems (try
http://www.networksolutions.com/cgi-bin/makechanges/itts/host ), then
call or write NSI and describe your problem, and ask them to update
their records.
Also, assign a coordinator to your domain. It will make life a whole
lot easier.
Michael Kjörling
On Jun 20 2001 14:03 -0700, Bret Sanders wrote:
> %whois -h whois.networksolutions.com 'host ns1.domain.com'
>
> Hostname: NS1.DOMAIN.COM
> Address: 206.244.12.3
> System: ? running ?
>
> The IP of this name server has changed. Is NSI's host record important
> to change? I've had a hell of a time changing it, because the host
> record has no coordinator attached, and also the parent domain's
> registrar is now register.com instead of NSI. But the stale record
> remains at NSI, and is incorrect.
>
> I did make the IP change with register.com, but NSI's record still
> gives the wrong IP. Normally I wouldn't care, except I have several
> other domains using NSI and this name server. However, when I dig a
> gtld server for one of these NSI domains, it responds with the correct
> IP for ns1.domain.com.
>
> So is the whois data important for anything in my case?
>
> P.S. obviously, domain.com is not my real domain :-)
- --
Michael Kjörling - michael at kjorling.com - PGP: 8A70E33E
"We must be the change we wish to see" (Mahatma Gandhi)
^..^ Support the wolves in Norway -- go to ^..^
\/ http://home.no.net/ulvelist/protest_int.htm \/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7MR9+KqN7/Ypw4z4RArlXAKD8I2YFGgbYVMBMNQ4RfkN70fCSiACfd3/6
F23UdqYD1PkWtU8zadMwlmU=
=H+tp
-----END PGP SIGNATURE-----
More information about the bind-users
mailing list