Thanks!
Mike Burger wrote:
Do you have a system set up as a DNS server, on your network, that your internal computers use?
If so, set up, on that DNS server, a zone for emeraldbiostructures.com, and a reverse zone for 230.168.192.in-addr.arpa.
On Thu, 2 Jan 2003, Hidong Kim wrote:
Hi,
I'm having problems with name resolution. We have several machines on an NIS network. The NIS server is Red Hat 7.2, and the rest of the machines are all Red Hat 8.0. Each machine has been assigned a local static IP address. /etc/NIS/hosts on the NIS server looks like this:
192.168.230.200 sulaco.emeraldbiostructures.com sulaco
192.168.230.201 ripley.emeraldbiostructures.com ripley
192.168.230.202 jonesy.emeraldbiostructures.com jonesy
192.168.230.203 iris.emeraldbiostructures.com iris
192.168.230.205 kcsa.emeraldbiostructures.com kcsa
The machines can be pinged by just their short names. You can also ssh to a machine by its short name. But if you try to point a browser to a machine's short name or even its FQDN, it says that the requested URL can't be found. If you point a browser to the machine's local IP address, then you get the home page. Some of these Linux machines, like ripley, are Samba servers. From a Windows machine, in Internet Explorer, I can point the browser to just "ripley", and it gets there. But on all of the Linux machines, you have to use the IP addresses. I think /etc/resolv.conf is OK since I can browse the outisde Internet just fine. It's only with the internal Linux machines where we have problems with name resolution. Thanks for any suggestions,
Hidong
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
