Are you saying that you have a new VPS and DNS isn't working on it? If so, the first thing to do is to check that you can connect to the DNS servers you wish to use:
(If you don't have dig, install the bind-utils package and try again)
If that works, but ping Google fails to resolve the hostname, check the following two files: /etc/resolv.conf
Make sure it contains: /etc/nsswitch.conf
Make sure it contains:
what are the files needed for the installation of a dns server on linux (redhat 7x)? what service does it run and where are the files & services located? (1 Reply)
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)
hello
i am running my sipx server in 192.168.2.14
i would like to configure domain name and host name for this .....
can anyone tell me how to configure dns server and dhcp server so that any body both outside and inside the lan could access the sipx server by their host.domain.com name (1 Reply)
I now know that I have to configure dns mx to actually be able to send email correctly to my mail.
I have the link(user guide) on how to do this :
http://bobcares.com/blog/?p=29
but where do I configure it? Is there a specific file for the configuration? I really don't understand this part. (2 Replies)
Hi everybody,
for revolving local host name of my network, I set up an dns server to solve my problem, but til now, nothing happen when I ping a hostname, but work on IP. Can you help me to correct the configuration. Here is all my settings:
Voici mes fichiers de configuration:
-... (2 Replies)
I'd like to get some opnions on choosing DNS server:
Windows DNS vs Linux BIND comparrsion:
1) managment, easy of use
2) Security
3) features
4) peformance
5) ??
I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Hi,
I have a question on how to point the DNS server-1's A-record to second DNS server, which is DNS server-2. So, the computer can access other domain which only listed in the DNS server-2. The scenario is as follow:
http://img689.imageshack.us/img689/6333/12234.png
How to configure this... (4 Replies)
I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based.
I've installed CentOS 6.2 with... (4 Replies)
Can someone help with a detail step-by-step oh how to configure DNS server on Linux Server.
-
I need to have 3 IP addresses map to a single hostname.
for clients
I'm a Linux rookie.
Thanks
Oscar (1 Reply)
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 DEBIAN
smokeping_probes_dns
Smokeping_probes_DNS(3) SmokePing Smokeping_probes_DNS(3)NAME
Smokeping::probes::DNS - Name Service Probe for SmokePing
SYNOPSIS
*** Probes ***
+DNS
binary = /usr/bin/dig # mandatory
forks = 5
offset = 50%
step = 300
timeout = 15
# The following variables can be overridden in each target section
lookup = www.example.org
pings = 5
server = ns1.someisp.net
# [...]
*** Targets ***
probe = DNS # if this should be the default probe
# [...]
+ mytarget
# probe = DNS # if the default probe is something else
host = my.host
lookup = www.example.org
pings = 5
server = ns1.someisp.net
DESCRIPTION
Integrates dig as a probe into smokeping. The variable binary must point to your copy of the dig program. If it is not installed on your
system yet, you should install bind-utils >= 9.0.0.
The Probe asks the given host n-times for it's name. Where n is the amount specified in the config File.
VARIABLES
Supported probe-specific variables:
binary
The location of your dig binary.
Example value: /usr/bin/dig
This setting is mandatory.
forks
Run this many concurrent processes at maximum
Example value: 5
Default value: 5
offset
If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe-
specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or
alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT
influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable
'concurrentprobes' is set in the 'General' section.)
Example value: 50%
step
Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the
step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to
delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the
'General' section.)
Example value: 300
timeout
How long a single 'ping' takes at maximum
Example value: 15
Default value: 5
Supported target-specific variables:
lookup
Name of the host to look up in the dns.
Example value: www.example.org
pings
How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the
number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have
to delete the old RRD files or somehow convert them.
Example value: 5
server
Name of the dns server to use.
Example value: ns1.someisp.net
AUTHORS
Igor Petrovski <pigor@myrealbox.com>,
Carl Elkins <carl@celkins.org.uk>,
Andre Stolze <stolze@uni-muenster.de>,
Niko Tyni <ntyni@iki.fi>,
Chris Poetzel<cpoetzel@anl.gov>
2.6.8 2013-03-17 Smokeping_probes_DNS(3)