with some icons under xfwm4 not
showing,
and some of the top menu bar text hosed (showing the square box char which
usually
indicates bad character data).
I was able to shut it down by exiting the controlling xterm.
Somewhere in there I'm pretty sure I saw a message something like
Too many named
Dear group,
I latety face an issue with BIND 9.4.-ESV-R4-P1.
According to my log file, I get the following error:
Aug 4 12:00:03 triton named[93266]: starting BIND 9.4.-ESV-R4-P1 -c
/etc/namedb/named.conf -t /var/named -u bind
Aug 4 12:00:03 triton named[93266]: command channel listening
on 04/08/2011 11:33, Jos Chrispijn wrote:
I latety face an issue with BIND 9.4.-ESV-R4-P1.
I deduce that you are running FreeBSD 7.x
According to my log file, I get the following error:
Aug 4 12:00:03 triton named[93266]: starting BIND 9.4.-ESV-R4-P1 -c
/etc/namedb/named.conf -t /var
Matthew Seaman:
One unfortunate consequence is that any relative paths within named.conf
have to be altered accordingly.
Thanks for your detailed explanation, I will follow up and let you know
if I managed to solve it.
BR
Jos Chrispijn
___
fuser(1) man page mentions the tool is supposed to list processes that
have specified named file(s) open. As there are several types of files
(according to stat(2)) it's not clear which are supported, e.g.
$ (mkfifo foo.fifo; cat foo.fifo) nc -lU foo.socket
$ fuser foo.*
foo.fifo
Yesterday noon my time I rebooted my server. Things seemed to be slow.
Several streams were hanging or stopping, and because ethic.thought.org had
been up for 61 days I figured it wouldn't hurt to reinitialize stuff.
Well, nutshell, disaster. For hours it wasn't clear whether the server would
Sorry to see you are still having issues. I thought you were set when we fixed
your resolv last night.
Okay - let's start from scratch here
Are you sure you need a named? Are you actually serving dns for your own IP
addresses or are you using it as a caching server. Getting a new named
On Wed, Jan 19, 2011 at 06:11:23PM -0500, Robert Boyer wrote:
Sorry to see you are still having issues. I thought you were set when we
fixed your resolv last night.
Okay - let's start from scratch here
Are you sure you need a named? Are you actually serving dns for your own IP
on EVERY system it tells ALL
of the software to get name services from. We fixed this last night for one of
your systems by pointing it at a name server that works (the one you had did
not work)
B) named provides name services (as well as forwarding to other dns
services) and can
thought you were set when we
fixed your resolv last night.
Okay - let's start from scratch here
Are you sure you need a named? Are you actually serving dns for your own IP
addresses or are you using it as a caching server.
i am actually serving my own DNS
On Fri, 10 Sep 2010 15:58:42 -0500
Martin McCormick mar...@dc.cis.okstate.edu wrote:
After successfully installing bind97 from a package on
to a new server, I do a cvs-sup of the system to get the latest
patches in to the kernel. After discovering that bind97 had been
replaced with
built when we
could be doing DNS.
Since I am not using that version of bind, not getting
it built is no problem. I don't even care if it gets built so
long as it does not end up in /usr/sbin to clobber the new
bind9.7.
If your ports version of named is in /usr/sbin you must have enabled
After successfully installing bind97 from a package on
to a new server, I do a cvs-sup of the system to get the latest
patches in to the kernel. After discovering that bind97 had been
replaced with bind9.6.1, I looked in /usr/src and there is a
contrib/bind9 directory. What is the safest
At 04:58 PM 9/10/2010, Martin McCormick wrote:
contrib/bind9 directory. What is the safest way to disable that
build without adversly effecting the rest of the update?
Hi,
Take a look at the man page for src.conf (and make.conf for
completeness). You can control parts of what gets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/2010 04:21:34, Peter Boosten wrote:
On 17-6-2010 4:58, Robert Huff wrote:
Martin McCormick writes:
Is there a way to keep /var/named owned by bind across
reboots?
Yes. I had this happen for a long time.
The bad news
On 17 June 2010 08:47, Matthew Seaman m.sea...@infracaninophile.co.ukwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/2010 04:21:34, Peter Boosten wrote:
On 17-6-2010 4:58, Robert Huff wrote:
Martin McCormick writes:
Is there a way to keep /var/named owned by bind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/2010 09:37:03, krad wrote:
so the logical extension to this is by changing the ownership of the
directory to bind, you are making the configuration directory writeable, and
therefore you are actually lowering security.
Correct.
Matthew Seaman writes:
Furthermore, the default setup *is* for named to run as an unprivileged
process. The setup is very carefully designed so that named doesn't
have write permission on the directory where its configuration files are
stored, or on directories that contain static zone files
I run named chrooted to bind but not in a jail. When the
system reboots, something changes ownership of /var/named back
to root:wheel.
I have thought several times I figured out how to
prevent this from happening, but to no avail. The most promising
lead was the following
Martin McCormick writes:
Is there a way to keep /var/named owned by bind across
reboots?
Yes. I had this happen for a long time.
The bad news is it had been years since I fixed it, and I no
longer remember exactly what I did. I will keep trying
On 17-6-2010 4:58, Robert Huff wrote:
Martin McCormick writes:
Is there a way to keep /var/named owned by bind across
reboots?
Yes. I had this happen for a long time.
The bad news is it had been years since I fixed it, and I no
longer remember exactly what I did. I
In my home network, I have named running to resolve machines on my LAN.
It is also configured to forward requests to my ISP for all other queries.
On another machine in my LAN, I used mpd to create a vpn connection to
my work and set appropriate routes so that any machine on my LAN can
On Tue, May 25, 2010 at 04:30:04PM -0700, Drew Tomlinson wrote:
Hi Drew,
In my home network, I have named running to resolve machines on my LAN.
It is also configured to forward requests to my ISP for all other queries.
On another machine in my LAN, I used mpd to create a vpn connection
On 5/25/2010 4:58 PM, Thomas Keusch wrote:
On Tue, May 25, 2010 at 04:30:04PM -0700, Drew Tomlinson wrote:
Hi Drew,
In my home network, I have named running to resolve machines on my LAN.
It is also configured to forward requests to my ISP for all other queries.
On another machine in my
into the
identically named mirrors on the system where the drive has been inserted.
What's worse, they may also become recognized as the mirrors with the most
recent data, even though they came from a different system and should in fact
be immediately flagged as dirty and synchronized
On Thu, 2010-04-08 at 20:46 -0400, Brodey Dover wrote:
If you already have a name server on your network then no, the WAP
will not need to use DNS. You can tell the clients of the WAP that a
nameserver exists in the DHCPD.conf file.
I believe you can also set router 10.0.0.1 for example in
Continuing the saga of building a wireless access point, what is the best way
to provide DNS service to the dowstream network? Seems like all I need is a
simple pass-through. For that named seems like overkill. Anyone have an
/etc/named/named.conf that does that?
--
Gary Dunn, Honolulu
o
On Apr 8, 2010, at 1:57 PM, Gary Dunn wrote:
Continuing the saga of building a wireless access point, what is the best way
to provide DNS service to the dowstream network?
Run a nameserver?
Seems like all I need is a simple pass-through. For that named seems like
overkill. Anyone have
On Apr 8, 2010, at 4:57 PM, Gary Dunn wrote:
Continuing the saga of building a wireless access point, what is the
best way to provide DNS service to the dowstream network? Seems like
all I need is a simple pass-through. For that named seems like
overkill. Anyone have an /etc/named
Gary Dunn wrote:
Continuing the saga of building a wireless access point, what is the best way
to provide DNS service to the dowstream network? Seems like all I need is a
simple pass-through. For that named seems like overkill. Anyone have an
/etc/named/named.conf that does that?
I normally
-through. For that named seems like
overkill. Anyone have an /etc/named/named.conf that does that?
Depends on how your internal LAN is configured. Generally if there are
no internal servers then you can forgo deploying a DNS server. Simply
setup your firewall IPFW or pf or whatever you are using
network? Seems like
all I need is a simple pass-through. For that named seems like
overkill. Anyone have an /etc/named/named.conf that does that?
Depends on how your internal LAN is configured. Generally if there
are
no internal servers then you can forgo deploying a DNS server. Simply
setup your
-0400 mikel king mikel.k...@olivent.com
wrote:
On Apr 8, 2010, at 4:57 PM, Gary Dunn wrote:
Continuing the saga of building a wireless access point, what is the
best way to provide DNS service to the dowstream network? Seems like
all I need is a simple pass-through. For that named seems like
It seems that if you add an alias to an interface once named is up
and running, it will cause named, on an hourly basis from the time
named was first started (that is, if it was started at 07:32 after
the hour, then every hour after the alias is added at about 07:32
after each hour), named
On 2/12/10, Jason Lin taosheng@gmail.com wrote:
I try this method, after set the password of toor,
I can't login with the account toor.
It is possible (I don't remember) that the toor account does not
have a shell in the default passwd file. If that's the problem, use
vipw to add the path
On 13/02/2010 17:49, Bob Johnson wrote:
It is possible (I don't remember) that the toor account does not
have a shell in the default passwd file. If that's the problem, use
vipw to add the path to a shell as the last field on the line. The
root account should provide a good example, or look
On 13 February 2010 18:10, Matthew Seaman m.sea...@black-earth.co.uk wrote:
On 13/02/2010 17:49, Bob Johnson wrote:
It is possible (I don't remember) that the toor account does not
have a shell in the default passwd file. If that's the problem, use
vipw to add the path to a shell as the last
yes, I login with toor as root successfully.
2010/2/14 Chris Rees utis...@googlemail.com:
On 13 February 2010 18:10, Matthew Seaman m.sea...@black-earth.co.uk wrote:
On 13/02/2010 17:49, Bob Johnson wrote:
It is possible (I don't remember) that the toor account does not
have a shell in the
I try this method, after set the password of toor,
I can't login with the account toor.
Bogdan Webb bog...@pgn.ro
??:c81e6afd1002102307l2b089a76p36a8d67d3085a...@mail.gmail.com...
Edit the /etc/master.passwd and /etc/passwd records to change the uid and
gid of the root account BUT FIRST
On 11/02/2010 05:23, Giorgos Keramidas wrote:
On Thu, 11 Feb 2010 00:18:30 -0500, Robert Huff roberth...@rcn.com wrote:
Lin Taosheng writes:
Is that possible to implementated?
For most purposes, what's important is not the account name,
but the User II. Root is special because it has
the root
account and have a non UID 0 account with that name. On the other
hand, if you're asking this question there may be a better way to
accomplish your objective: would you care to share?
Having an account named root that is not UID 0 (i.e. not an
administrator), is likely to have unexpected
.
As far as I know, there's no reason you can't rename the root
account and have a non UID 0 account with that name. On the other
hand, if you're asking this question there may be a better way to
accomplish your objective: would you care to share?
Having an account named root
On Thu, 11 Feb 2010 08:04:00 +, Matthew Seaman m.sea...@black-earth.co.uk
wrote:
On 11/02/2010 05:23, Giorgos Keramidas wrote:
On Thu, 11 Feb 2010 00:18:30 -0500, Robert Huff roberth...@rcn.com wrote:
Lin Taosheng writes:
Is that possible to implementated?
For most purposes, what's
On 2/11/10, Jerry McAllister jerr...@msu.edu wrote:
On Thu, Feb 11, 2010 at 01:58:07PM -0500, Bob Johnson wrote:
On 2/11/10, Robert Huff roberth...@rcn.com wrote:
Lin Taosheng writes:
Is that possible to implementated?
Yes, use vipw to edit the password file. Add another
Hi all,
Is that possible to implementated?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Lin Taosheng writes:
Is that possible to implementated?
For most purposes, what's important is not the account name,
but the User II. Root is special because it has UID 0. You can,
create other accounts with UIS 0 ... but it's usually a Very Bad
Idea.
As far as I know,
On Thu, 11 Feb 2010 00:18:30 -0500, Robert Huff roberth...@rcn.com wrote:
Lin Taosheng writes:
Is that possible to implementated?
For most purposes, what's important is not the account name,
but the User II. Root is special because it has UID 0. You can,
create other accounts with UIS
Lin Taosheng wrote:
Is that possible to implementated?
No. I think not. But I have not tried it either.
Can I ask what do you want to achieve? Because I had the same thought once,
concerning how to combat once-increasing script-driven SSH brute-force attack.
But I was instead have a better
Edit the /etc/master.passwd and /etc/passwd records to change the uid and
gid of the root account BUT FIRST MAKE SURE YOU ADD (or changed password
of) ANOTHER UID0 ACCOUNT
here's an example:
etc/master.passwd:
root:*PASSWORD HASH*:99:99::0:0:Charlie :/root:/bin/csh
and /etc/passwd
to mention is that this server is running
TWO instances of named, on two different IPs (for different domains), each
running a few hundred zones.
Bottom line: Would congestion cause this issue, or would this issue cause
congestion?
Some updates that may confuse more than inform: I caught
On Fri, Jan 29, 2010 at 10:51 AM, James Smallacombe u...@3.am wrote:
Some updates that may confuse more than inform: I caught this while it was
happening yesterday and was able to do a tcpdump. I saw a ton of UDP
traffic outbound to one IP that turned out to be a colocated server in
Chicago.
Hi--
On Jan 29, 2010, at 8:51 AM, James Smallacombe wrote:
On Thu, Jan 28, 2010 at 12:59 PM, James Smallacombe u...@3.am wrote:
To follow up on this: Noticed the issue again this morning, which also was
accompanied by latency so high that I could not connect (some pings got
through at very
On Wed, 27 Jan 2010, Chuck Swiger wrote:
Hi--
On Jan 27, 2010, at 1:15 PM, James Smallacombe wrote:
Jan 26 21:50:32 host named[667]: client IP REMOVED#57938: error sending
response: not enough free resources
Jan 26 21:50:32 host named[667]: client IP REMOVED#59830: error sending
response
forgot to mention is that this server is running
TWO instances of named, on two different IPs (for different domains), each
running a few hundred zones.
Bottom line: Would congestion cause this issue, or would this issue cause
congestion?
I would guess no, but that guess could easily
over IP. CPU was fine and
there wre no full partitions. As I had to catch a flight, I just rebooted it
and it was fine.
After getting home, I looked in the syslog and see thousands of these:
Jan 26 21:50:32 host named[667]: client IP REMOVED#57938: error sending
response: not enough free
in the syslog and see thousands of these:
Jan 26 21:50:32 host named[667]: client IP REMOVED#57938: error sending
response: not enough free resources
Jan 26 21:50:32 host named[667]: client IP REMOVED#59830: error sending
response: not enough free resources
Were these client IPs expected
of hours earlier, then looked at the
archives and noticed zero traffic on that list for the past couple of
weeks, so I then posted here.
After getting home, I looked in the syslog and see thousands of these:
Jan 26 21:50:32 host named[667]: client IP REMOVED#57938: error sending
response
Hi--
On Jan 27, 2010, at 1:15 PM, James Smallacombe wrote:
Jan 26 21:50:32 host named[667]: client IP REMOVED#57938: error sending
response: not enough free resources
Jan 26 21:50:32 host named[667]: client IP REMOVED#59830: error sending
response: not enough free resources
Were
On Wed, 27 Jan 2010, Chuck Swiger wrote:
On Jan 27, 2010, at 1:15 PM, James Smallacombe wrote:
Jan 26 21:50:32 host named[667]: client IP REMOVED#57938: error
sending response: not enough free resources
indicates a problem sending UDP traffic; netstat -s output would be
Unfortunately, I
working, but I have noticed that every time I
reboot the machine, I need to manually restart named to get it
listening on the proper interfaces as by default it is listening on
127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it
which seems like it would be configured correctly
...@example.com:/usr/obj/usr/src/sys/FRODO
amd64
I have most things working, but I have noticed that every time I
reboot the machine, I need to manually restart named to get it
listening on the proper interfaces as by default it is listening on
127.0.0.1 interfaces only. A simple /etc/rc.d
Greetings,
uname:
FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec
6 11:23:52 PST 2009 ryal...@example.com:/usr/obj/usr/src/sys/FRODO
amd64
I have most things working, but I have noticed that every time I
reboot the machine, I need to manually restart named to get
to manually restart named to get it
listening on the proper interfaces as by default it is listening on
127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it
which seems like it would be configured correctly, but I have had to
do this on a install before.
Anyone have a guess as to what
Jeffrey Goldberg wrote:
These are queries your mailservers are making to the spamhaus blocking
list.
How many queries to the ZEN Spamhaus DNSBL are you making per day? If
you exceed their non-commercial usage, they will cut you off.
I see.
Thank you all for your suggestions.
Jos Chrispijn
[named]
Lately I get messages like thin in my all.log:
named[605]: too many timeouts resolving '*.*.*.*.zen.spamhaus.org/A' (in
'zen.spamhaus.ORG'?): disabling EDNS
(*) is random ip address
Now before I add the following lines in /etc/named.conf or
/var/named/chroot/etc/
named.conf
On 9/25/09, Jos Chrispijn ker...@webrz.net wrote:
[named]
Lately I get messages like thin in my all.log:
named[605]: too many timeouts resolving '*.*.*.*.zen.spamhaus.org/A' (in
'zen.spamhaus.ORG'?): disabling EDNS
(*) is random ip address
Now before I add the following lines in /etc
On Sep 25, 2009, at 2:00 PM, Jos Chrispijn wrote:
[named]
Lately I get messages like thin in my all.log:
named[605]: too many timeouts resolving '*.*.*.*.zen.spamhaus.org/
A' (in 'zen.spamhaus.ORG'?): disabling EDNS
(*) is random ip address
These are queries your mailservers are making
Nerius Landys nlan...@gmail.com wrote:
I am still bambuzzled by the network taking 30 seconds to come up.
One thing I've run into recently is an Ethernet switch that needs to
resolve spanning tree after a port reset. The physical link comes
back up quickly, but it seems to take about 30
On Fri, Aug 21, 2009 at 09:37:09PM -0700, Nerius Landys wrote:
I am trying to figure out why DNS lookups are not possible right after
the named process has been launched (during bootup).
At start, named sends a couple of queries to e.g. root servers. All
this requires the network connection
On Fri, 21 Aug 2009 21:37:09 -0700
Nerius Landys nlan...@gmail.com wrote:
Then why
can't I do a lookup right after named starts?
Possibly it's a delay in bind being ready or maybe you don't have any
network access - the latter is common with ppp.
By the way, the underlying issue that I'm
it in rc.conf:
===
#!/bin/sh
# PROVIDE: waitfornetwork
# REQUIRE: NETWORKING
# BEFORE: named
. /etc/rc.subr
: ${waitfornetwork_enable:=NO}
name=waitfornetwork
rcvar=`set_rcvar`
stop_cmd=:
start_cmd=waitfornetwork_start
waitfornetwork_start()
{
echo Waiting for network
One last question. I'm getting interesting [kernel?] messages during
bootup. You know, the kind that are highlighted white in the console.
The relevant lines of rc.conf look like this right now:
defaultrouter=64.156.192.1
hostname=daffy.nerius.com
ifconfig_em0=inet 64.156.192.169 netmask
highlightedcalcru: runtime went backwards from 37332 usec to 16577
usec for pid 47 (sh).../highlighted
Not to seem like I'm talking to myself, but I fixed this problem:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE-RUNTIME
(Turn off Intel® Enhanced
Nerius Landys wrote:
I am still bambuzzled by the network taking 30 seconds to come up.
I don't remember the original description, but any time I hear about a
30 second gap during startup, I think of the well-known DNS reverse
look-up issue. Are you sure this is not the case here?
the original description is that when I issue a ping -c 100
x.y.z.w to a well-known IP address, only the last 70 packets get
returned, not the first 30 (hence 30 seconds). This ping command is
issued very early in the rc.d scripts, after NETWORK and before named,
and the script does not exit until
NETWORK and before named,
and the script does not exit until a ping request is successful.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions
I am trying to figure out why DNS lookups are not possible right after
the named process has been launched (during bootup). I am kind of a
newb at diagnosing these sorts of issues, but as an attempt to figure
out what's wrong, I added the following lines to the very bottom of my
/etc/rc.d/named
I am trying to figure out why DNS lookups are not possible right after
the named process has been launched (during bootup). I am kind of a
newb at diagnosing these sorts of issues, but as an attempt to figure
out what's wrong, I added the following lines to the very bottom of my
/etc/rc.d/named
apply the update reboot, named loads but
the startup script hangs.
If I press Ctrl+C, the system continues to boot. If I then run
/etc/rc.d/named start, named starts, but again the script hangs. I can do
DNS lookups while named is running, so it seems to be functioning ok.
I tried adding
wrote:
Ian wrote:
Well the fact that if I run /etc/rc.d/named manually after the system
has booted, the script also hangs suggests it's not the next process I
have just check however ntpdate is the next one in the list to be
started and that does start correctly - you can see it report
On Tue, 30 Jun 2009 08:35:26 +, no-s...@people.net.au wrote:
Sorry for starting a new thread with this - my ISP's mail server seems to
rejecting all mail recipients when I
Which which reason?
send email with a mail client, so I'm having to use webmail instead. Their
tech says they
Hi, I've been meaning to sort this out since the release of 7.1p5, but only
just got around to it - I have an installation of 7.1 that runs bind and has
been working fine up until I tried to update the system to 7.1p5 (using
freebsd-update). As soon as I apply the update reboot, named loads
, named loads but the
startup script hangs.
If I press Ctrl+C, the system continues to boot. If I then run /etc/rc.d/named
start, named starts, but again the script hangs. I can do DNS lookups while
named is running, so it seems to be functioning ok.
I tried adding various echo statements to /etc
freebsd-update). As soon as I apply the update reboot, named
loads but the startup script hangs.
If I press Ctrl+C, the system continues to boot. If I then run
/etc/rc.d/named start, named starts, but again the script hangs. I can do
DNS lookups while named is running, so it seems
Ian wrote:
Well the fact that if I run /etc/rc.d/named manually after the system has
booted, the script also hangs suggests it's not the next process
I have just check however ntpdate is the next one in the list to be started
and that does start correctly - you can see it report the clock
On Sunday 28 June 2009 03:24:26 Ian wrote:
I tried adding various echo statements to /etc/rc.d/named and found that
the script seems to run right through.
rc_debug=YES in /etc/rc.conf is REALLY handy for this.
--
Mel
___
freebsd-questions
+noall +answer -t ptr -x 10.0.5.16 @10.0.5.16
16.5.0.10.in-addr.arpa. 86400 IN PTR kanga.honeypot.net.
But I can't get the same from named:
$ dig -t ptr -x 10.0.5.16
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 56485
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1
On Thursday 04 June 2009 11:53:38 am Kirk Strauser wrote:
For some reason, BIND 9 (FreeBSD 7.2-RELEASE) isn't properly forwarding
queries.
Commenting out
// zone 10.in-addr.arpa { type master; file master/empty.db; };
from named.conf fixed the problem. That's kind of... embarrassing.
--
Steve Bertrand wrote:
Chris St Denis wrote:
Steve Bertrand wrote:
What type of device is em1 attached to? Is it a switch or a hub? Is it
possible to upgrade this? You should upgrade it to 100 (or 1000)
anyways. Does this device show any collisions?
This is a dedicated
This is a dedicated server in a datacenter. I don't know the exact
switch specs but it's likely a
layer 2/3 managed switch. Probably a 1U catalyst.
you mean cisco?
there are actually most problematic switches. They don't properly
autonegotiate speed and full/half duplex with many network
kanga.honeypot.net.
But I can't get the same from named:
$ dig -t ptr -x 10.0.5.16
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 56485
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;16.5.0.10.in-addr.arpa.IN PTR
- the network/LAN named tries to sent UDP packet is somehow flooded.
Dns is probably fairly busy. It's the primary authorative dns for some
busy domains.
Is there a setting I can do to increase the limits of UDP packets to keep
it from
causing problems?
it would need
On Wednesday 03 June 2009 00:46:20 Wojciech Puchar wrote:
named[69750]: client *ip removed*: error sending response: not
enough free resources
quite misleading message, but the problem is that named want to send UDP
packet and get's error from kernel.
possible reasons
- your
possible reasons
- your firewall rules are the cause - check it.
- your network card produce problems (REALLY i have that case)
- the network/LAN named tries to sent UDP packet is somehow flooded.
- the network card changes from UP to DOWN state at the time of the error
See that a lot running
On Wednesday 03 June 2009 11:48:48 Wojciech Puchar wrote:
possible reasons
- your firewall rules are the cause - check it.
- your network card produce problems (REALLY i have that case)
- the network/LAN named tries to sent UDP packet is somehow flooded.
- the network card changes
Not really. The point is that at the time the network card goes from up to
down, named spits out this error. If you log named to a different log file
then /var/log/messages, you will not see the relation. The reason for changing
this is one reason i always change syslog.conf to configure
I occasionally get named errors like these in my messages log. I've done
a lot of searching and have found others with similar problems, but no
solutions.
named[69750]: client *ip removed*: error sending response: not
enough free resources
named[69750]: client *ip removed*: error
lot of searching and have found others with similar problems, but no
solutions.
named[69750]: client *ip removed*: error sending response: not
enough free resources
named[69750]: client *ip removed*: error sending response: not
enough free resources
named[69750]: client *ip removed
Wojciech Puchar wrote:
lot of searching and have found others with similar problems, but no
solutions.
named[69750]: client *ip removed*: error sending response: not
enough free resources
named[69750]: client *ip removed*: error sending response: not
enough free resources
named[69750
don't think it's a hardware problem.
- the network/LAN named tries to sent UDP packet is somehow flooded.
Dns is probably fairly busy. It's the primary authorative dns for
some busy domains. Is there a setting I can do to increase the
limits of UDP packets to keep it from causing
1 - 100 of 514 matches
Mail list logo
