On Monday, February 24, 1997 4:50 PM, Michael Handler[SMTP:handler@sub-rosa.com] wrote: @ In <3.0.32.19970224171008.00727978@207.87.243.20>, @ Eric Germann <ekgermann@cctec.com> wrote: @ @ > In the process of switching ISP's, I sent some updates off to InterNIC last @ > friday. The new SOA's are in place on all root servers except for @ > f.root-servers.net. Mail to hostmaster@internic.net yields no response @ > (who knows, they could be using f.....) @ @ handler@jumpgate ~$ check_soa com. | grep F @ F.ROOT-SERVERS.NET has serial number 1997021900 @ @ hostmaster@internic.net is only for updating your data on the master @ root servers. The master root has performed the updates, but @ F.ROOT-SERVERS.NET hasn't loaded new "COM." data since Wednesday @ of last week. (Sorry, Paul). @ If you are using the new TRUE Root Name Servers... J.ROOT-SERVERS.NET K.ROOT-SERVERS.NET L.ROOT-SERVERS.NET M.ROOT-SERVER.NET ....in your root.cache file, then you do not have to get involved with F.ROOT-SERVERS.NET. The Legacy Root Name Servers are being migrated to become Top Level Domain (TLD) Name Servers. If you "dig" at the TRUE Root Name Servers above for a domain in .COM, all you will get is a referral to the .COM TLD Name Servers which are shown below: =============================================== ; <<>> DiG 2.1 <<>> @j.root-servers.net unety.com ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr rd; Ques: 1, Ans: 0, Auth: 9, Addit: 9 ;; QUESTIONS: ;; unety.com, type = A, class = IN ;; AUTHORITY RECORDS: COM. 518400 NS A.ROOT-SERVERS.NET. COM. 518400 NS H.ROOT-SERVERS.NET. COM. 518400 NS B.ROOT-SERVERS.NET. COM. 518400 NS C.ROOT-SERVERS.NET. COM. 518400 NS D.ROOT-SERVERS.NET. COM. 518400 NS E.ROOT-SERVERS.NET. COM. 518400 NS I.ROOT-SERVERS.NET. COM. 518400 NS F.ROOT-SERVERS.NET. COM. 518400 NS G.ROOT-SERVERS.NET. ;; ADDITIONAL RECORDS: A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4 H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53 B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107 C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12 D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90 E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10 I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17 F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241 G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4 ;; Total query time: 62 msec ;; FROM: doorstep.unety.net to SERVER: j.root-servers.net 198.41.0.10 ;; WHEN: Mon Feb 24 17:07:56 1997 ;; MSG SIZE sent: 27 rcvd: 334 =============================================== In summary, once you move your root.cache "up" a level to the TRUE Root Name Servers, then you can forget about who is serving each Top Level Domain. You will note that the above .COM servers do not list the new TRUE Root Name Servers. That would defeat the purpose of deploying the new TRUE Root Name Servers which will only provide referrals to TLD Name Servers. -- Jim Fleming Unir Corporation e-mail: JimFleming@unety.net JimFleming@unety.s0.g0 (EDNS/IPv8)