Known issue with resolving hosts with multiple PTR records?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I was wondering if RHEL4 has a known problem with returning multiple PTR records. Carrying out a "host", "dig -x" or "nslookup" against an IP like 202.92.65.220 results in no records at all being returned:
# host 202.92.65.220
;; Truncated, retrying in TCP mode.
;; connection timed out; no servers could be reached

Checking the IP from another Linux (not RedHat) server results in 12 PTR records being returned for the host. A Windows server returns the first entry in the list.

There is no problem carrying out name resolution for a host with a single PTR record from the RHEL4 box:
# host 74.125.19.103
103.19.125.74.in-addr.arpa domain name pointer cf-in-f103.google.com.

I'm wondering if it's a fault with the gethostname() function, but I can't find anything in the Red Hat Bugzilla.

Thanks,

Tracy


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux