Sponsored Content
Operating Systems Linux Red Hat Network becomes slow and return fast only after restart network Post 302895620 by rbatte1 on Tuesday 1st of April 2014 01:17:08 PM
Old 04-01-2014
There may be repeated rogue queries that are trying to return vast amounts of data. If the user is disconnected/timed out/gets bored, they may well re-issue. I would consider reading the application logs to check that the queries are indeed going to return suitable data volumes.

This was learned from prolonged painful experience eventually leading to better validation and sanity checking on the application server before the query was executed.


Robin
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

network speed is slow

Hello, everyone: i encounter a problem these days , pls help me ,thanks in advance. my env: machine: ES40 A ES40 B os: true64 Unix 4.0f note: src.tar 8M network card speed 100M my problem: ... (3 Replies)
Discussion started by: q30
3 Replies

2. AIX

How to send big files over slow network?

Hi, I am trying to send oracle archives over WAN and it is taking hell a lot of time. To reduce the time, I tried to gzip the files and send over to the other side. That seems to reduce the time. Does anybody have experienced this kind of problem and any possible ways to reduce the time. ... (1 Reply)
Discussion started by: giribt
1 Replies

3. Solaris

Unavailable/Slow Network Paths in $PATH

At work, I'm in a Solaris environment working with csh, and $PATH is populated with anywhere between 10 and 20 entries. Last week, every command I issued (even "ls") took several seconds, if not an entire minute, to run. Once I moved "/home/sybase/bin" to the end of $PATH, certain commands... (2 Replies)
Discussion started by: acheong87
2 Replies

4. Red Hat

slow network on RHEL5

hey guys, We have two Sun x2100 servers running RHEL5 in a test environment. Both servers are fresh OS installs and hooked up to the same network switch. When ssh'ing to one server, there is a significant delay, while ssh'ing to the other server, the connection is almost instant. We are... (2 Replies)
Discussion started by: amheck
2 Replies

5. BSD

restart the network on freeBSD 7.2

hi howto restart the network with a wireless interface including wpa_supplicant on freeBSD 7.2 without reboot? (3 Replies)
Discussion started by: ccc
3 Replies

6. AIX

How restart the network interface in AIX?

Hi All, Please let me know the command to restart the network interface and enable it on boot in AIX, similar to /etc/init.d/network restart in Redhat. Thanks, Sunil.K please watch out to post in the right subforum! (9 Replies)
Discussion started by: sunilrk07
9 Replies

7. UNIX for Advanced & Expert Users

Slow printing to network printers using CUPS

Hi Guys, I've inherited a mess of an infrastructure in my new job, there hasn't been a sys admin in post for about a year, so things are falling apart. The first thing to break after I started was the printer server. I have it working again, and people can print, however it's very slow, slower... (0 Replies)
Discussion started by: rudigarude
0 Replies

8. Solaris

Solaris 11.1 Slow Network Performance

I have identical M5000 machines that are needing to transfer very large amounts of data between them. These are fully loaded machines, and I've already checked IO, memory usage, etc... I get poor network performance even when the machines are idle or copying via loopback. The 10 GB NICs are... (7 Replies)
Discussion started by: christr
7 Replies

9. AIX

Network Perforamnce - It's just slow!

Hello everyone, I've been a life long Unix/Linux user but I'll be the first to admit I have little specific AIX knowledge at this point and I've inherited these systems for better or worse so please forgive if I ask something in the wrong context. And yes, I've searched google for 3 days now :)... (3 Replies)
Discussion started by: BDMcGrew
3 Replies

10. Debian

How do i correct restart network-services in Debian?

Hello, I would like to do follow steps. Set a static IP-Adress on eth0 (For Testing) Set DHCP on eth0 All steps should be done without a single reboot. /etc/network/interfaces iface eth0 inet static address 192.0.2.7/24 gateway 192.0.2.254How do i perform... (3 Replies)
Discussion started by: int3g3r
3 Replies
DNSPROXY(1)						    BSD General Commands Manual 					       DNSPROXY(1)

NAME
dnsproxy -- DNS proxy SYNOPSIS
dnsproxy [-dhV] [-c file] DESCRIPTION
The dnsproxy daemon waits for nameserver queries on a user specified address, dispatches these queries to authoritative and recursive name- servers and forwards the received answers back to the original client. The options are as follows: -c file Read configuration from file. -d Detach from current terminal and run as background process. -h Show usage. -V Show version. If a client from an internal IP address does a recursive lookup the query is forwarded to a recursive DNS server. Authoritative queries and queries coming from clients in foreign networks are forwarded to an authoritative DNS server. CONFIGURATION FILE
At startup dnsproxy reads a configuration file specified via the -c option or at the default location of /etc/dnsproxy.conf. The following keywords are recognized: authoritative IP Address of the authoritative nameserver [required]. recursive IP Address of the recursive nameserver [required]. listen IP Local address (defaults to 0.0.0.0). port number Local port number (defaults to 53). chroot path A path to chroot to before starting to answer queries. user name A user to change to before starting to answer queries. authoritative-timeout seconds Time in seconds when authoritative queries time out (defaults to 10). recursive-timeout seconds Time in seconds when recursive queries time out (defaults to 90). authoritative-port number Port number on authoritative nameserver (defaults to 53). recursive-port number Port number on recursive nameserver (defaults to 53). statistics seconds Period between output of statistics (defaults to 3600). Use 0 to disable output of statistics completely. internal network Declare networks recognized as internal and thus eligible to do recursive queries. One network in CIDR notation per keyword. EXAMPLE authoritative 10.1.1.1 recursive 127.0.0.1 recursive-port 10053 listen 192.168.1.1 port 53 chroot /var/empty user nobody internal 192.168.1.0/24 internal 127.0.0.1 STATISTICS
Every hour (by default) dnsproxy logs the collected statistics about its usage to standard error (or syslog when running detached). Statis- tics look like ActiveQr AuthorQr RecursQr AllQuery Answered 0 0 0 0 0 TimeoutQ DroppedQ DroppedA LateAnsw HashColl 0 0 0 0 0 and have the following meaning: ActiveQr Number of currently active queries proxied to the servers. AuthorQr Accumulated number of authoritative queries. RecursQr Accumulated number of recursive queries. AllQuery Accumulated number of all queries ever received. Answered Accumulated number of answered queries. TimeoutQ Accumulated number of queries that did not receive an answer in time. DroppedQ Accumulated number of dropped queries (e.g. transmission errors). DroppedA Accumulated number of dropped answers. LateAnsw Accumulated number of answers received after the timeout period. HashColl Accumulated number of hash collisions in the query list. SEE ALSO
named(1) VERSION
This manual page describes dnsproxy version 1.16. AUTHORS
Armin Wolfermann <armin@wolfermann.org> The dnsproxy homepage is at http://www.wolfermann.org/dnsproxy.html. LOCAL
November 29, 2003 LOCAL
All times are GMT -4. The time now is 02:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy