Sponsored Content
Full Discussion: dns client not working
Operating Systems Solaris dns client not working Post 302482272 by mtomar on Tuesday 21st of December 2010 06:41:37 AM
Old 12-21-2010
you have to configure and run bind if you wish to do nslookup. hostname in file can be cross checked by doing a ping / telnet etc etc. nslookup will try to get it via dns db file not file(/etc/hosts)

ping dummy.set.com
telnet dummy.set.com
ftp dummy.set.com
Smilie
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

DNS client nslookup

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

Solaris DNS Client For Microsoft DNS Server

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

HOWTO: Linux multihomed dns client

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

PB : DNS Client don't ping internet

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

How to Determine client's DNS server Ip

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

How to add a client to DNS server

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

Nslookup working but ping not working at windows client

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

DNS client - what exactly it is

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

DNS client added to DNS server but not working

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
BOOTPARAMS(5)                                                 BSD File Formats Manual                                                BOOTPARAMS(5)

NAME
bootparams -- boot parameter database SYNOPSIS
/etc/bootparams DESCRIPTION
The bootparams file specifies the boot parameters that diskless clients may request when booting over the network. Each client supported by this server must have an entry in the bootparams file containing the pathnames for its root and (optionally) swap areas. Each line in the file (other than comment lines that begin with a #) specifies the client name followed by the pathnames that the client may request by their logical names. The components of the line are delimited with blank or tab, and may be continued onto multiple lines with a backslash. For example: dummy root=host:/export/dummy/root swap=host:/export/dummy/swap dump=host:/export/dummy/swap When the client named "dummy" requests the pathname for its logical "root" it will be given the pathname ``host:/export/dummy/root'' as the response to its RPC request. The "host:" component must be supplied. FILES
/etc/bootparams default configuration file SEE ALSO
bootparamd(8) Linux NetKit (0.17) October 2, 1994 Linux NetKit (0.17)
All times are GMT -4. The time now is 11:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy