>When I do NSlookup with 199.45.248.90 I get
>
>06/09/00 14:54:15 dns 199.45.248.90
>nslookup 199.45.248.90
>No reverse DNS (WSANO_DATA)
>
>Why is it no reverse DNS and what do I need to change? Thank you
This URL: http://www.samspade.org/t/dnl.cgi?a=199.45.248.90 returns:
Reverse DNS Scan
199.45.248.195 proxy.wisen.com (bogus rDNS)
199.45.248.196 charon.wisen.com (bogus rDNS)
199.45.248.197 ns2.wisen.com (bogus rDNS)
This says that the .90 PTR record is not defined, as your nslookup said.
What NS is authoritative for .90?
# dig -x 199.45.248.90
; <<>> DiG 8.2 <<>> -x
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUERY SECTION:
;; 90.248.45.199.in-addr.arpa, type = ANY, class = IN
;; AUTHORITY SECTION:
248.45.199.in-addr.arpa. 2h59m42s IN SOA xor.com. trent.xor.com. (
2 ; serial
12H ; refresh
30M ; retry
2W ; expiry
12H ) ; minimum
conclusion: yes not PTR for .90, and your DNS is not authoritative for .90.
If you want your DNS to be authoritative (it's lamely delegate now anyway),
then hit on" "trent" at xor.com to delegate reverse authority to you DNS,
and fix the lame delegation in parallel.
DNS Expert report sent privately.
Len
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
