12-21-2010
have you configured BIND on your linux box? based on what you have posted, it seems you only have edited the hosts file and the nsswitch.conf. the changes that you have done on nsswitch.conf file only tells the local machine to search dns if the host can't be found on the hosts file.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I just got done setting up a DNS server and a client. However, when I do an nslookup with just the hostname, I got this output:
Microsoft Windows 2000
(C) Copyright 1985-2000 Microsoft Corp.
C:\Documents and Settings\dev9>nslookup dev9
Server: webdev.testsurgemail.com
Address:... (3 Replies)
Discussion started by: xnightcrawl
3 Replies
2. Solaris
hey guys, how to add soalris box as a microsoft DNS Client ?
and how to register in the microsoft DNS ??
i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf
but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies
3. IP Networking
The Linux resolver queries all nameservers in the order they are listed in /etc/resolver.conf.
If a nameserver times out, it advances on to the following nameserver.
But, if a nameserver returns "not found" (NXDOMAIN) it stops.
This behaviour is problematic when you need to resolve names from... (0 Replies)
Discussion started by: colemar
0 Replies
4. Debian
Hi,
I have my router (192.168.1.1) connected to the internet.
I have installed Debian on a server with Bind9 (192.168.1.254).
The configurations files are :
$ cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface... (1 Reply)
Discussion started by: Thibault
1 Replies
5. IP Networking
Is there a way for a server to determine client's DNS ip? I have an application that logs client's IP but in certain cases its desirable to know their DNS too (1 Reply)
Discussion started by: vickylife
1 Replies
6. Linux
Hi all,
What is the procedure to add a client to a DNS server.
what are the settings and files need to be added/changed ?
thanks in advance! (6 Replies)
Discussion started by: lramsb4u
6 Replies
7. Red Hat
Hi Team
we have created a DNS server at RHEL6.2 environment in 10.20.203.x/24 network.
Everything is going well on linux client as nslookup, ping by host etc in entire subnet. We are getting problem in windows client as nslookup working as well but not ping. all the firewall is disabled and... (5 Replies)
Discussion started by: boby.kumar
5 Replies
8. Solaris
Hi all,
I always thought DNS server = provide DNS response (host to ip / ip to host) to DNS client (which send DNS resolve request).
So in my solaris 10 box, i setup /etc/resolv/conf, /etc/nsswitch.conf (added in dns) etc.
Yes, i am able to dig and nslookup. But.. am i a DNS client ?
... (5 Replies)
Discussion started by: javanoob
5 Replies
9. Solaris
Hi,
We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using
and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies
LEARN ABOUT SUSE
cifs.upcall
CIFS.UPCALL(8) System Administration tools CIFS.UPCALL(8)
NAME
cifs.upcall - Userspace upcall helper for Common Internet File System (CIFS)
SYNOPSIS
cifs.upcall [--trust-dns|-t] [--version|-v] {keyid}
DESCRIPTION
This tool is part of the cifs-utils suite.
cifs.upcall is a userspace helper program for the linux CIFS client filesystem. There are a number of activities that the kernel cannot
easily do itself. This program is a callout program that does these things for the kernel and then returns the result.
cifs.upcall is generally intended to be run when the kernel calls request-key(8) for a particular key type. While it can be run directly
from the command-line, it's not generally intended to be run that way.
OPTIONS
-c
This option is deprecated and is currently ignored.
--trust-dns|-t
With krb5 upcalls, the name used as the host portion of the service principal defaults to the hostname portion of the UNC. This option
allows the upcall program to reverse resolve the network address of the server in order to get the hostname.
This is less secure than not trusting DNS. When using this option, it's possible that an attacker could get control of DNS and trick
the client into mounting a different server altogether. It's preferable to instead add server principals to the KDC for every possible
hostname, but this option exists for cases where that isn't possible. The default is to not trust reverse hostname lookups in this
fashion.
--version|-v
Print version number and exit.
CONFIGURATION FOR KEYCTL
cifs.upcall is designed to be called from the kernel via the request-key callout program. This requires that request-key be told where and
how to call this program. The current cifs.upcall program handles two different key types:
cifs.spnego
This keytype is for retrieving kerberos session keys
dns_resolver
This key type is for resolving hostnames into IP addresses
To make this program useful for CIFS, you'll need to set up entries for them in request-key.conf(5). Here's an example of an entry for each
key type:
#OPERATION TYPE D C PROGRAM ARG1 ARG2...
#========= ============= = = ================================
create cifs.spnego * * /usr/local/sbin/cifs.upcall %k
create dns_resolver * * /usr/local/sbin/cifs.upcall %k
See request-key.conf5() for more info on each field.
SEE ALSO
request-key.conf(5), mount.cifs(8)
AUTHOR
Igor Mammedov wrote the cifs.upcall program.
Jeff Layton authored this manpage.
The maintainer of the Linux CIFS VFS is Steve French.
The Linux CIFS Mailing list is the preferred place to ask questions regarding these programs.
cifs-utils 4.0 02/07/2010 CIFS.UPCALL(8)