05-21-2008
If you can reproduce the behavior at the command prompt, you can use various dig options etc to get DNS debugging info, such as which server responded and how long it took.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all,
If I give ls , it lists files in 1 second.
It I give ls -l , it takes 8 seconds
There are only 55 files in the directory.
Any explanation?
Thanks
Wilson (4 Replies)
Discussion started by: geraldwilson
4 Replies
2. SCO
Hi All
We have one SCO Server here and it never gives us any trouble. Until Now!! Well its not earth shattering but we have one user who is complaining of a very slow response time when changing to his Home Directory. Other users who have similar profiles are OK. I have su'd to this user and I can... (0 Replies)
Discussion started by: JohnOB
0 Replies
3. UNIX for Advanced & Expert Users
Double question here ... Running on Debian Etch and Apache 2.0
1) Using mod_proxy and/or mod_proxy_http in apache 2.0.
The basics of using mod_proxy are pretty simple so long as you're using a static config. I'm trying to figure out how to do it dynamically - that is, allow the entry of a... (4 Replies)
Discussion started by: Halfwalker
4 Replies
4. UNIX and Linux Applications
I am using Apache 2.2.3 on RHEL5 and having problems to get mod_deflate work with mod_proxy. mod_deflate will compress files by mime-type just fine as long as those files are served statically from the local server. However, files served via dynamic php application (ie, MediaWiki) or via... (2 Replies)
Discussion started by: otheus
2 Replies
5. Emergency UNIX and Linux Support
Hi,
My application runs on AIX, and clients complain of 3am slowdowns. This seems to have increased in the recent past.
Can someone guide me what are the various things that I need to be looking at on he AIX box, that could be causing slowdowns.
Thanks in Advance. (4 Replies)
Discussion started by: ggayathri
4 Replies
6. AIX
Hi All.
We are using AIX 5.3 ML9. There is 1 Gig NIC installed on two servers (Primary and Secondary) with Full Duplex Mode. We have scheduled a cronjob to copy the backup from primary to secondary thru FTP on WAN. The total data size is 15 GB and it took 9 Hours and 18 Mins with transfer rate... (6 Replies)
Discussion started by: lodhi1978
6 Replies
7. Post Here to Contact Site Administrators and Moderators
Hi,
I am experiencing slow response of unix.com from past 3-4 days.
like-
- most of the time the page does not reload instantly (when I do a manual reload from browser)
- not able to view graphics. ( displays only text).
- when posting into forum, the page gets stuck for considerably long... (6 Replies)
Discussion started by: clx
6 Replies
8. IP Networking
Hi,
I am running scientific linux (which is clone of red hat linux) on virtual machine that is virtual box.
I tried to start the apache but I got the following message.
starting httpd: httpd: arp_sockaddr_info_get() failed for scientific-linux
httpd: could not reliably determine the... (2 Replies)
Discussion started by: programAngel
2 Replies
9. Solaris
Solaris terminal responding very slow .. we have recently put a T3 hardware in to production , the applications running are it are perfectly and no complaints from user ..but when i ssh to the server ... the terminal response is very very slow .. it takes 3 seconds to show the character i type ..... (3 Replies)
Discussion started by: skamal4u
3 Replies
10. Web Development
I have the following setup in my apache vhost:
ProxyPass /abc http://www.newest.com/
ProxyPassReverse /abc http://www.newest.com/
I want to setup a failover approach in which if after a particular timeout say 10secs the load shifts to some other website like Refer.com | The world. The timeout... (0 Replies)
Discussion started by: ankur328
0 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)