06-04-2003
I've been looking into the DNS issue here what I got, I added a logical interface with the ip 1.1.1.1
cofdr01 > ifconfig hme0 addif 1.1.1.1 up
Created new logical interface hme0:1
added 1.1.1.1 testftp /etc/hosts
/etc/nsstich.conf was hosts:files dns
cofdr01 > ping 1.1.1.1
1.1.1.1 is alive
cofdr01 > nslookup testftp
Server: blah.blah
Address: 170.30.9.12
then changed nsswitch.conf
hosts: dns
ping didn't work either did nslookup
cofdr01 > arp -d 1.1.1.1
1.1.1.1 (1.1.1.1) deleted
cofdr01 > arp -d testftp
arp: testftp: unknown host
from testing this with truss I've found nslookup doesn't look in nsswitch, ping does as I added the files option to nsswitch.conf and
cofdr01 > ping testftp
testftp is alive
Dataprotector I think, looks for the existance existance of resolv.conf and goes ahead otherwise looks in /etc/hosts, I'll try a truss later on a UPDATE
heres the opened files whilst running
truss -o /tmp/kie omnicc -update_host mgunix11 ; grep open /tmp/kie
open("/var/ld/ld.config", O_RDONLY) Err#2 ENOENT
open("/usr/lib/libnsl.so.1", O_RDONLY) = 3
open("/usr/lib/libsocket.so.1", O_RDONLY) = 3
open("/usr/lib/libw.so.1", O_RDONLY) = 3
open("/usr/lib/libBrandChg.so", O_RDONLY) Err#2 ENOENT
open("/opt/omni/lib/libBrandChg.so", O_RDONLY) = 3
open("/usr/lib/libc.so.1", O_RDONLY) = 3
open("/usr/lib/libdl.so.1", O_RDONLY) = 3
open("/usr/lib/libmp.so.2", O_RDONLY) = 3
open("/usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1", O_RDONLY) = 3
open("/etc/netconfig", O_RDONLY) = 3
open("/dev/udp", O_RDONLY) = 3
open64("/etc/.name_service_door", O_RDONLY) = 3
open64("/opt/omni/lib/nls/C/omni.cat", O_RDONLY) = 4
open("/usr/share/lib/zoneinfo/GB", O_RDONLY) = 5
open64("/etc/opt/omni/cell/cell_server", O_RDONLY) = 5
open("/etc/nsswitch.conf", O_RDONLY) = 5
open("/usr/lib/nss_files.so.1", O_RDONLY) = 5
open("/etc/services", O_RDONLY) = 5
it looks in nsswitch.conf bollx, wonder if it has a reading problem, I've copied a good nsswitch file from another. Could this be a new problem for the DP lab boys ?
10 More Discussions You Might Find Interesting
1. IP Networking
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. Solaris
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
3. Red Hat
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
4. Red Hat
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
5. Red Hat
: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
6. Red Hat
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
7. Red Hat
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
8. IP Networking
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
9. HP-UX
Hi All,
I'm having some problems with our HP-UX environment. I'm running Oracle EBS on a HP-UX system, and whenever my primary dns server goes down some of my clients can no longer connect. Everything on my windows side continues to work, and clients can reach the internet and other services... (6 Replies)
Discussion started by: agonza07
6 Replies
10. Linux
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
LEARN ABOUT MOJAVE
nss-systemd
NSS-SYSTEMD(8) nss-systemd NSS-SYSTEMD(8)
NAME
nss-systemd, libnss_systemd.so.2 - Provide UNIX user and group name resolution for dynamic users and groups.
SYNOPSIS
libnss_systemd.so.2
DESCRIPTION
nss-systemd is a plug-in module for the GNU Name Service Switch (NSS) functionality of the GNU C Library (glibc), providing UNIX user and
group name resolution for dynamic users and groups allocated through the DynamicUser= option in systemd unit files. See systemd.exec(5) for
details on this option.
This module also ensures that the root and nobody users and groups (i.e. the users/groups with the UIDs/GIDs 0 and 65534) remain resolvable
at all times, even if they aren't listed in /etc/passwd or /etc/group, or if these files are missing.
To activate the NSS module, add "systemd" to the lines starting with "passwd:" and "group:" in /etc/nsswitch.conf.
It is recommended to place "systemd" after the "files" or "compat" entry of the /etc/nsswitch.conf lines so that /etc/passwd and /etc/group
based mappings take precedence.
EXAMPLE
Here is an example /etc/nsswitch.conf file that enables nss-systemd correctly:
passwd: compat mymachines systemd
group: compat mymachines systemd
shadow: compat
hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
SEE ALSO
systemd(1), systemd.exec(5), nss-resolve(8), nss-myhostname(8), nss-mymachines(8), nsswitch.conf(5), getent(1)
systemd 237 NSS-SYSTEMD(8)