On Saturday 03 September 2011 12:26 AM, Michael D. Setzer II wrote: > Our MIS department just decided to not allow the use of the public > IP addresses of system from local machines, so I made the > additions to the hosts file with the private ip and the name. > restart named and restarted squid, and squid picked up the > change, and would bring up pages using the name. Unfortunately, > dig and other options would still be using the public IP instead. > > Tried restarting the machine to see if something might not have > been changed, but it remains the same. > > In the past, I had done this same thing for local services I have. > redhatgcc.dyndns.org has a public ip of 202.128.73.24, but on the > inside it has the private ip of 192.168.50.41. So, the hosts file has > the link between the 192.168.50.41 and the > redhatgcc.dyndns.org, and it reports that. You need to setup a DNS server or add a new zone to existing DNS server for local network. BTW /etc/hosts is not part of DNS , thats why you cannot see the effects during dig <name> command Warm Regards -- °v° /(_)\ ^ ^ Jatin Khatri RHCSA,RHCE,CCNA Registerd Linux user No #501175 www.counter.li.org No M$ -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
