Sponsored Content
Full Discussion: HP-UX DNS issue
Operating Systems HP-UX HP-UX DNS issue Post 302887442 by MadeInGermany on Friday 7th of February 2014 02:09:23 PM
Old 02-07-2014
No, it's safer to have files first!
Especially "localhost" should not be searched in an external name service.
E.g. "swinstall" and several applications talk to localhost. And should work even if the network cable is unplugged...
This User Gave Thanks to MadeInGermany For This Post:
 

10 More Discussions You Might Find Interesting

1. IP Networking

DNS issue.

Hi, We use linux as a DNS server for our local network. ( linuxnol.nollekens.be ) We can ping this machine on all our XP clients like this: C:\>ping linuxnol Until yesterday it was on our XP clients enough to type "ping ibm250" ( our 2de unix server, an AIX ). But after a shutdown of this... (1 Reply)
Discussion started by: progressdll
1 Replies

2. UNIX for Advanced & Expert Users

DNS issue still not looking in files

anyone ever seen this problem with /etc/nsswitch.conf forcing the system to look in files then dns but the system ignores the files and goes off check the dn servers is there any further config I've missed ??? /etc/resolve.conf name servers >>>> boring IPS /etc/nsswitch.conf is set to... (5 Replies)
Discussion started by: kie
5 Replies

3. Solaris

t2000 DNS issue

I have an issue with DNS on a solaris t2000 When I set up the zones there was an issue with the /etc/resolv.conf, I had made a typo in my DNS server. I only noticed this after creating my new zones. I have corrected this in the global zone and I am now able to ping and nslookup inthe... (2 Replies)
Discussion started by: james dewitt
2 Replies

4. Red Hat

Linux DNS issue

Hi , I have configured OEL 5.3 server on VMware server,installation went fine, however when i am checking host using configured /etc/hosts i am getting following error let me know where it went wrong . I had disabled firewall options and SELLinux. root@oen11g ~]# host oen11g.grid.com ;;... (2 Replies)
Discussion started by: autoconfig
2 Replies

5. Red Hat

DNS issue in Redhat 9

Hi all m newbie in linux and trying to setup my internal DNS server for local network.After messing with DNS for hours i am posting this. i have configured /etc/resolve.conf, hostname with domain name in /etc/sysconfig/network file,/etc/hosts file with local host entry and zone file... (1 Reply)
Discussion started by: Vaibhav.T
1 Replies

6. Red Hat

Issue in DNS set up

:wall:I am a beginer in Linux admin. I have build new DNS setting in my system. Please find the below procedure what I followed to build DNS. but at last when I fired nslookup command, its getting error. I am using RHEL5 OS. Please help me to resolve this below issue.. Advance thanks for... (1 Reply)
Discussion started by: pradipta_pks
1 Replies

7. Red Hat

dns update issue

i have redhat service as public dns i have added new entry but when i reload the named service i got this error in log the working directory is not writable (1 Reply)
Discussion started by: leganti
1 Replies

8. Red Hat

DNS Resolution Issue

Hello, Having issue resolving DNS using the IP address. Using the server Name it resolves fine. Was wondering if there is any configuration issue. # nslookup xxxxxxxx01 Server: Primary DNS IP Address: Primary DNS IP#53 Name: xxxxxxxx01.local domain Address: x.y.z.123 # nslookup... (1 Reply)
Discussion started by: ikn3
1 Replies

9. IP Networking

OS X & VPN DNS Issue

I'll try and be brief and detailed. I have a Macbook Pro Retina running Mavericks. When on my network at the office (work) everything local works just fine. Local servers are resolved through our internal DNS settings. For example, we have a fileserver at "fs01". I can connect to it with... (1 Reply)
Discussion started by: jbhardman
1 Replies

10. Linux

DNS Response Issue

Hi, I have a Windows based Domain (abc.com)servers like: 172.30.1.246 172.30.1.247 172.30.3.246 172.30.3.247 On all my Linux servers (/etc/resolv.conf) have a following DNS servers entries: nameserver 172.30.3.246 nameserver 172.30.3.247 But when i ping my Domain (abc.com), it... (5 Replies)
Discussion started by: refra
5 Replies
TALK(1) 						    BSD General Commands Manual 						   TALK(1)

NAME
talk -- talk to another user SYNOPSIS
talk person [ttyname] DESCRIPTION
The talk utility is a visual communication program which copies lines from your terminal to that of another user. Options available: person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another host, then person is of the form 'user@host' or 'host!user' or 'host:user'. ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name, where ttyname is of the form 'ttyXX'. When first called, talk sends the message Message from TalkDaemon@his_machine... talk: connection requested by your_name@your_machine. talk: respond with: talk your_name@your_machine to the user you wish to talk to. At this point, the recipient of the message should reply by typing talk your_name@your_machine It does not matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the two parties may type simultaneously, with their output appearing in separate windows. Typing control-L '^L' will cause the screen to be reprinted. Typing control-D '^D' will clear both parts of your screen to be cleared, while the control-D character will be sent to the remote side (and just displayed by this talk client). Your erase, kill, and word kill characters will behave normally. To exit, just type your interrupt character; talk then moves the cursor to the bottom of the screen and restores the terminal to its previous state. Permission to talk may be denied or granted by use of the mesg(1) command. At the outset talking is allowed. FILES
/etc/hosts to find the recipient's machine /var/run/utx.active to find the recipient's tty SEE ALSO
mail(1), mesg(1), wall(1), who(1), write(1), talkd(8) HISTORY
The talk command appeared in 4.2BSD. In FreeBSD 5.3, the default behaviour of talk was changed to treat local-to-local talk requests as originating and terminating at localhost. Before this change, it was required that the hostname (as per gethostname(3)) resolved to a valid IPv4 address (via gethostbyname(3)), making talk unsuitable for use in configurations where talkd(8) was bound to the loopback interface (normally for security reasons). BUGS
The version of talk released with 4.3BSD uses a protocol that is incompatible with the protocol used in the version released with 4.2BSD. Multibyte characters are not recognized. BSD
January 21, 2010 BSD
All times are GMT -4. The time now is 03:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy