the biggest problem with this is that if someone typed in 212.com into a
browser, it would take them to 208.211.134.100 (old nameserver
association) even though the true ip address for 212.com is 209.123.16.2.
root@titus/# host 212.com ns.netscape.com
Using domain server:
Name: ns.netscape.com
Address: 198.95.251.10
Aliases:
212.com has address 208.211.134.100
212.com mail is handled (pri=10) by inbox.net
root@titus/# host -d 212.com
;; res_nmkquery(QUERY, 212.com, IN, A)
;; res_send()
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44853
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; 212.com, type = A, class = IN
;; Querying server (# 1) address = 127.0.0.1
;; new DG socket
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44853
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; 212.com, type = A, class = IN
212.com. 1D IN A 209.123.16.2
212.com. 1D IN NS ns1.nill.net.
ns1.nill.net. 1D IN A 209.123.16.2
rcode = 0 (Success), ancount=1
212.com has address 209.123.16.2
;; res_nmkquery(QUERY, 212.com, IN, MX)
;; res_send()
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44854
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; 212.com, type = MX, class = IN
;; Querying server (# 1) address = 127.0.0.1
;; new DG socket
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44854
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; 212.com, type = MX, class = IN
212.com. 1D IN MX 10 inbox.net.
212.com. 1D IN NS ns1.nill.net.
inbox.net. 1D IN A 209.31.125.120
ns1.nill.net. 1D IN A 209.123.16.2
rcode = 0 (Success), ancount=1
212.com mail is handled (pri=10) by inbox.net
root@titus/# host 212.com ns1.nill.net
Using domain server:
Name: ns1.nill.net
Address: 209.123.16.2
Aliases:
212.com has address 209.123.16.2
212.com mail is handled (pri=10) by inbox.net
root@titus/#
-rm
On Sun, 4 Mar 2001, Mark Jeftovic wrote:
>
> Be careful, I was about to say, "move 212.com over to opensrs and delete
> it" but I'm not sure.
>
> Our old nameserver records have been literally marooned at NSI ever
> since we moved easydns.com over to tucows.
>
> Those NSI records show up in whois with the wrong/old IP addresses and
> there is absolutely no way to get them fixed. It's reallya piece of
> work.
>
> -mark
>
> On Sun, 4 Mar 2001, ross wrote:
>
> > when i had domains at NSI, i created a nameserver named '212.com' with
> > the ip address 208.211.134.100. after transferring to opensrs, i can no
> > longer manage this nameserver anymore since it doesn't show up on
> > manage.opensrs.net , but it still exists, and i'm looking to delete it,
> > any suggestions?
> >
> > -rm
> >
> >
>
> --
> mark jeftovic
> http://www.easydns.com
> http://mark.jeftovic.net
>
