So its searching for a DNS server in that range because it's a defined default place to find a DNS server. Theres no indication that its looking at the netware boxes.... So is ping not reading /etc/resolv.conf?
Is there something that I'm not aware of that is telling ping to look elsewhere for DNS services? Does that spark any ideas for anyone? -----Original Message----- From: Carl Cerecke [mailto:[EMAIL PROTECTED] Sent: Tuesday, 2 November 2004 11:47 a.m. To: CLUG Cc: David Kirk Subject: Re: Reverse DNS Lookups from SuSE 9.1 David Kirk wrote: > So, we can see the the DNS lookups are working in both directions > (forward and reverse), but when I use ping it does something with > 224.0.0.251. Isn't that a multicast address? I don't know anything > about multicast (if that's what it is). What does this mean? From: http://www.iana.org/assignments/multicast-addresses we see that 224.0.0.251 is used for DNS discovery on a local network: "The range of addresses between 224.0.0.0 and 224.0.0.255, inclusive, is reserved for the use of routing protocols and other low-level topology discovery or maintenance protocols, such as gateway discovery and group membership reporting. Multicast routers should not forward any multicast datagram with destination addresses in this range, regardless of its TTL." Cheers, Carl.
