Reverse problems

Tony Huang thuang at mail.communityconnect.com
Thu Jul 6 05:28:18 UTC 2000


Keith,
I finally get to know the full story.
Let's start from the root server :
-------------------------------------------
dig ns @A.ROOT-SERVERS.NET 16.238.205.in-addr.arpa.

; <<>> DiG 8.2 <<>> ns @A.ROOT-SERVERS.NET 16.238.205.in-addr.arpa.
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 3
;; QUERY SECTION:
;;      16.238.205.in-addr.arpa, type = NS, class = IN

;; ANSWER SECTION:
16.238.205.in-addr.arpa.  6D IN NS  NS0.VERIO.NET.
16.238.205.in-addr.arpa.  6D IN NS  NS1.VERIO.NET.
16.238.205.in-addr.arpa.  6D IN NS  NS2.VERIO.NET.

;; ADDITIONAL SECTION:
NS0.VERIO.NET.          2D IN A         129.250.15.61
NS1.VERIO.NET.          2D IN A         204.91.99.140
NS2.VERIO.NET.          2D IN A         129.250.31.190
---------------------------------------------------------------------------------


More information about the bind-users mailing list