Gary W. Swearingen wrote:
Now host, dig, and nslookup work OK, even without an
/etc/resolv.conf file. But sendmail seems to need the later.
(It just has nameserver 127.0.0.1.)
[...]
Mozilla apparently doesn't even use my local DNS as it still hangs.
(I must admit that I've never checked my
Alex Zbyslaw [EMAIL PROTECTED] writes:
Gary W. Swearingen wrote:
Mozilla apparently doesn't even use my local DNS as it still hangs.
(I must admit that I've never checked my caching DNS's cache.)
Mozilla will use resolve.conf, if it is there. It will also cache answers
for a long time and
Chuck Swiger [EMAIL PROTECTED] writes:
Note that the resolver will treat lookups of localhost. and localhost
differently if you have a domain or search
directive specified in /etc/resolv.conf. You could and perhaps should ensure
that the one ending in a period exists in
a zone file on the
On Mon, Aug 15, 2005 at 09:35:03AM +0500, DeadMan Xia wrote:
I m running FreeBSD 5.4 on Dell PowerEdge 6650 on Quad Processor. I
ve configured the BIND, when I start BIND its works fine but i m also
getting an error when i do tail -f /var/log/messages
Aug 15 09:26:15 www named[769
[EMAIL PROTECTED] (Gary W. Swearingen) writes:
Kevin Kinsey [EMAIL PROTECTED] writes:
Did you `sh /var/named/etc/namedb/make-localhost` ?
Yup, but that only handles the reverse translation (which works OK)
and, of course, doesn't handle other stuff I might have in /etc/hosts.
I also
Lowell Gilbert [EMAIL PROTECTED] writes:
Of course it won't work for nslookup(1); it's not supposed to.
nslookup is specifically intended for querying a name server. The
documentation for host(1) isn't as clear on the subject, but my
reading of it seems to indicate the same thing.
Well that
Gary W. Swearingen wrote:
[ ... ]
so I'd think domain resolution should look in /etc/hosts before
even checking my cache-only named. Which it seems to do for ping,
but not for host, nslookup, or mozilla.
As Lowell noted, programs like nslookup and dig are designed to query DNS
specificly
I think I followed the bind manual and poked around /var/named and it
has been working OK for a few weeks until I pointed my browser to
localhost and then I tried host localhost. It can resolve
127.0.0.1 back to localhost.localhost. fine, but if I try
my name localhost or localhost.localhost, I
Gary W. Swearingen wrote:
I think I followed the bind manual and poked around /var/named and it
has been working OK for a few weeks until I pointed my browser to
localhost and then I tried host localhost. It can resolve
127.0.0.1 back to localhost.localhost. fine, but if I try
my name localhost
I m running FreeBSD 5.4 on Dell PowerEdge 6650 on Quad Processor. I
ve configured the BIND, when I start BIND its works fine but i m also
getting an error when i do tail -f /var/log/messages
Aug 15 09:26:15 www named[769]: starting BIND 9.3.1
Aug 15 09:26:15 www named[769]: couldn't add command
Hi,
With threads disabled in bind9, is it still
usefull to give
-n 2 for example if you got a system with 2 cpu's?
The man page only mentioned worker threads...
Bye,
Mipam
___
freebsd-questions@freebsd.org mailing list
Hello,
I'm running bind, under FreeBSD. Its bind 9. I just
started noticing a udp port being used, port 63548.
udp4 0 0 *.63548*.*
I then ran tcpdump on that port, and it seems that it is
being used for dns queries.
I'm not a named expert
I've enabled the commented out named_flags=-u bind -g bind in my
rc.conf to start named in a sandbox, but whenever I do a
named.reload, I get the following message in my logs:
Jul 14 14:20:55 pompom named[34352]: couldn't create pid file
'/var/run/named.pid'
It doesn't really seem to be a big
hey, got a strange problem here.
how do i find out _why_ named hasn't started even though it
claims it did? /var/log/messages doesn't contain anything.
# /etc/rc.d/named start
Starting named.
# /etc/rc.d/named status
named is not running.
thank you man!
--
Fafa Hafiz Krantz
Research
here's some more info:
# /usr/sbin/named -g
#
18-May-2005 21:52:14.136 starting BIND 9.3.1 -g
18-May-2005 21:52:14.144 found 1 CPU, using 1 worker thread
18-May-2005 21:52:14.307 loading configuration from '/etc/namedb/named.conf'
18-May-2005 21:52:14.352 listening on IPv4 interface lnc0
everything seems to be working like a charm however whenever I reboot
the server I have two issues:
1) named doesn't seem to be able to bind to the tun0 interface properly,
I've got a few theories about this but none of them have gotten me
anywhere! At first I thought it was my firewall rules
it then switches to looking for an A record, which
is found immediately (as a CNAME).
I'm using named (8.3.7, default nameserver) on 4.11, and as far as I
can tell haven't changed anything that would have caused this behavior.
If I switch resolv.conf to use the ISP's nameserver, I get a correct
On 25 Apr 2005, at 14:09, Eric Hodel wrote:
Starting last week, queries for domains are not failing
correctly when the domain being looked up is a CNAME for an A record.
Instead of getting back a response indicating there is no record,
the resolver continues to look for a record
Amandeep wrote:
I am running FreeBSD 5.0 and named . The problem is that it named
services are crahing every few hrs..
Here are some logs.
Any ideas why named is doing that.
5.0? Please upgrade to FreeBSD-5.3 or later, and you will get a newer named
with the base system that ought to work
Re: freebsd-questions Digest, Vol 88, Issue 54
Message: 4
Date: Tue, 15 Feb 2005 19:21:32 -0500
From: Benjamin Dover [EMAIL PROTECTED]
Subject: named error in /var/log/messages
I am running fBSD 5.3 Release. I get this message repeated in
/var/log/messages
Feb 15 17:27:09 w00f
I am running fBSD 5.3 Release. I get this message repeated in
/var/log/messages
Feb 15 17:27:09 w00f named[317]: omitting IPv4 interface xl1 from
localnets ACL: address mask not contiguous
Feb 15 18:27:09 w00f named[317]: omitting IPv4 interface xl1 from
localnets ACL: address mask
anyone else seeing this?
I rebuilt my laptop yesterday after an 'incident'
(tip of the week; don't mix up ad0 and da0) and rsynced bacx
/etc /home and /root, then pkg_add -r'ed my way back to a desktop
without too much bother.
But firefox (latest one with the hole, 1.0.7mumblemumble)
refuses to
Greetings..
I am running FreeBSD 5.3 on dual Xeon 3GHz box and today i got a line
in my messages, which goes:
named[604]: *** POKED TIMER ***
I've searched the web but i could not find what this means. Could
anyone help me? Is this a bug?
Thanks in advance.
Martin
On Thu, Jan 20, 2005 at 06:39:21PM +0100, Martin Zibert wrote:
Greetings..
I am running FreeBSD 5.3 on dual Xeon 3GHz box and today i got a line
in my messages, which goes:
named[604]: *** POKED TIMER ***
I've searched the web but i could not find what this means. Could
anyone help me
*gnaahh* I seem to be unable to locate any information about limiting
nameds service to one interface only. Does anybody know where to do
this ?
Thank you
Hexren
___
freebsd-questions@freebsd.org mailing list
Le 19/01/2005 à 21:06:47+0100, Hexren a écrit
*gnaahh* I seem to be unable to locate any information about limiting
nameds service to one interface only. Does anybody know where to do
this ?
In named.conf something like
options {
listen-on port 53 { 127.0.0.1 ; your_address ; };
Hexren wrote:
*gnaahh* I seem to be unable to locate any information about limiting
nameds service to one interface only. Does anybody know where to do
this ?
Put the following line into your named.conf's options section:
listen-on { list of adresses to listen on };
In case you use IPv6, the
AS Le 19/01/2005 à 21:06:47+0100, Hexren a écrit
*gnaahh* I seem to be unable to locate any information about limiting
nameds service to one interface only. Does anybody know where to do
this ?
AS In named.conf something like
AS options {
AS listen-on port 53 { 127.0.0.1 ; your_address ; };
and 192.168.0.1 and no
other interfaces. (YMMV, as I've never actually done this). Don't
forget to stop and start named after tweaking named.conf.
--
Greg Barniskis, Computer Systems Integrator
South Central Library System (SCLS)
Library Interchange Network (LINK)
gregb at scls.lib.wi.us, (608) 266-6348
Hi folks,
when I kill -HUP named on 5.3 (BIND 9), it exits, instead of reloading,
as stated in the manpage. Is this normal? I think it's rather
impractical, since it prevents proper log rotation through
newsyslog.conf (when using file logging in named.conf). It doesn't
seem to matter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 2 Jan 2005, Matthias Buelow wrote:
Hi folks,
when I kill -HUP named on 5.3 (BIND 9), it exits, instead of reloading, as
stated in the manpage. Is this normal? I think it's rather impractical,
since it prevents proper log rotation through
Joerg Pulz wrote:
i tried 'rndc reload' and it's working and did not cause the named
process to exit. maybe '/etc/rc.d/named' should be changed to use this
as reload command.
Yes, this works here also.
In the long run, it would probably be a good idea to make newsyslog
understand arbitrary
get no answer and i keep waiting :-(
I don't know anymore what the problem is. :-(
Here are the config files:
options {
directory /etc/namedb;
pid-file/var/run/named/pid;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats
On Wed, 29 Dec 2004 14:00:04 +0100 (MET), Mipam [EMAIL PROTECTED] wrote:
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { bla; };
};
perhaps this should be:
controls {
inet 127.0.0.1 port 953
allow { localhost; } keys { bla;
On Wed, 29 Dec 2004, Nelis Lamprecht wrote:
On Wed, 29 Dec 2004 14:00:04 +0100 (MET), Mipam [EMAIL PROTECTED] wrote:
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { bla; };
};
perhaps this should be:
controls {
inet 127.0.0.1
On Wed, 29 Dec 2004 14:39:44 +0100 (MET), Mipam [EMAIL PROTECTED] wrote:
On Wed, 29 Dec 2004, Nelis Lamprecht wrote:
On Wed, 29 Dec 2004 14:00:04 +0100 (MET), Mipam [EMAIL PROTECTED] wrote:
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys {
On Wed, 29 Dec 2004, Nelis Lamprecht wrote:
On Wed, 29 Dec 2004 14:39:44 +0100 (MET), Mipam [EMAIL PROTECTED] wrote:
On Wed, 29 Dec 2004, Nelis Lamprecht wrote:
On Wed, 29 Dec 2004 14:00:04 +0100 (MET), Mipam [EMAIL PROTECTED] wrote:
controls {
inet 127.0.0.1 port
On Wed, 29 Dec 2004 14:00:04 +0100 (MET)
Mipam [EMAIL PROTECTED] wrote:
Hi,
I configured plenty of nameservers also with bind9, but this time
i cannot figure out what's wrong anymore, i'm lost.
When i do host 127.0.0.1, i get a normal answer.
When i do host localhost, i get a normal answer.
I noticed that when named starts during boot up, I dont seem to be able to
'send' notifies to my slave machines:
notify to x.y.71.63#53: retries exceeded
notify to x.y.71.63#53: retries exceeded
notify to x.y.71.63#53: retries exceeded
However, if I pkill named and start it manually from
Budi Hermansjah wrote:
Hi
I have FreeBSD 4.10-STABLE, i386. And i installed BIND 8.3.7
my /etc/rc.conf as follows:
Also, are you sure you have bind8? since bind 8 uses ``ndc''
instead of ``rndc'', also you should have appropriate keys
in your config if you do have bind9 (which uses rndc) so
that
Budi Hermansjah wrote:
Hi Budi,
connect
rndc: connect failed: timed out
indoglobalhost#
i need help how to fix the problem,
thanks
What does your logging tell you?
for example can you try to start it and readout
the logfile (/var/log/messages for example)
Perhaps that tells you something...
--
Hi
I have FreeBSD 4.10-STABLE, i386. And i installed BIND 8.3.7
my /etc/rc.conf as follows:
named_enable=YES
named_program=/usr/local/sbin/named
named_flags=-u bind -c /etc/named.conf -t /etc/namedb
my /etc/hosts as follows:
::1 localhost.indoglobalhost.com localhost
Hi,
With 5.3, running named (cashing nameserver only) and ntpd to sync
the time, I see in /var/log/messages about twice a day a line like
this:
Nov 11 05:41:44 para named[356]: *** POKED TIMER ***
Nov 11 14:51:09 para named[355]: *** POKED TIMER ***
What does this mean? Is it still a bug
Hi all,
I've got a freebsd dedicated server in germany. My web page is only
accessible by www.mydomain.com. Now, I wanna create subdomains by
country, for instance, france.mydomain.com, spain.mydomain.com,
I think I have to set-up the named and create virtual-hosts in my
apache. However
no experiencies with named or any other name-servers, but I
think you are right.
I think I have to set-up the named and create virtual-hosts in my
apache. However, my server has the named and bind already installed,
but no /etc/namedb folder exists. I've tried to create it and its
files
the named and create virtual-hosts in my
apache.
Are you running primary DNS for mydomain.com? Probably not, since you
don't have BIND running :)
Then you don't need to run bind, you need to speak to whoever looks
after that domain for you and get them to add the extra hostnames
for you
On Wed, 8 Sep 2004 07:28:11 +0900
horio shoichi [EMAIL PROTECTED] wrote:
On Tue, 7 Sep 2004 14:24:37 +0300
Toomas Aas [EMAIL PROTECTED] wrote:
Hi!
From time to time I get this:
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(d.root-servers.net)
Sep 7
Hi,
From time to time I get this:
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(d.root-servers.net)
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(a.root-servers.net)
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(c.root
On Tue, 7 Sep 2004 13:00:47 +0300
Ion-Mihai Tetcu [EMAIL PROTECTED] wrote:
Hi,
From time to time I get this:
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(d.root-servers.net)
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(a.root
Hi!
From time to time I get this:
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(d.root-servers.net)
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(a.root-servers.net)
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
On Tue, 7 Sep 2004 14:24:37 +0300
Toomas Aas [EMAIL PROTECTED] wrote:
Hi!
From time to time I get this:
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(d.root-servers.net)
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(a.root
On Tue, 7 Sep 2004 13:07:05 +0300, Ion-Mihai Tetcu wrote
On Tue, 7 Sep 2004 13:00:47 +0300
Ion-Mihai Tetcu [EMAIL PROTECTED] wrote:
Hi,
From time to time I get this:
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(d.root-servers.net)
Sep 7 12:57:44
On Tue, 7 Sep 2004 14:41:08 +0200
Robert Eckardt [EMAIL PROTECTED] wrote:
On Tue, 7 Sep 2004 13:07:05 +0300, Ion-Mihai Tetcu wrote
On Tue, 7 Sep 2004 13:00:47 +0300
Ion-Mihai Tetcu [EMAIL PROTECTED] wrote:
Hi,
From time to time I get this:
Sep 7 12:57:44 it named[353
On Tue, 7 Sep 2004 14:24:37 +0300
Toomas Aas [EMAIL PROTECTED] wrote:
Hi!
From time to time I get this:
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(d.root-servers.net)
Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS
(a.root-servers.net
Hi,
I have a problem with named in my LAN. My notebook
is sometimes attached to this network and sometimes
not.
Everything works well when the network cable is plugged-in.
Without the network cable (same network settings), the following
happens:
- sendmail is waiting for timeout while booting
Martin [EMAIL PROTECTED] wrote:
Hi,
I have a problem with named in my LAN. My notebook
is sometimes attached to this network and sometimes
not.
Everything works well when the network cable is plugged-in.
Without the network cable (same network settings), the following
happens
First, I've found a solution. The nsswitch.conf file is helpful
for my scenario. You can set hosts: files dns and the timeouts
will never happen.
Am Tue, den 06.07.2004 schrieb Bill Moran um 14:42:
It's a standard timeout. The resolver isn't aware of the status of parts
of the network stack
You need to compile named-xfer as statically linked, or move it's dependant
libraries into the chroot.
Can't remember the details of how I did that, and I don't use named any
more - but that's your problem.
hope that helps.
m/
-Original Message-
From: [EMAIL PROTECTED]
[mailto
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Muhammad Reza
I running named in sandbox as a secondary name server with
FreeBSD-5.1.p17,
Named log always complain:
named-xfer exited with signal 6 and slave zone expired for every zone
under the chroot, rather than using
mknod.
You can simply symlink the device nodes:
guardian# ls -la /var/chroot/named/dev/
total 4
drwxr-xr-x 2 bind bind 512 Mar 3 11:21 .
drwx-- 5 bind bind 512 Mar 3 11:18 ..
lrwxr-xr-x 1 root bind9 Mar 3 11:21 null - /dev/null
lrwxr-xr-x 1
. A 195.20.105.149
ns1.xname.org. A 213.133.115.5
here is the error is /var/log/messages:
May 20 18:07:14 ns1 named[718]: dns_master_load: mydomain.com:33: ignoring
out-of-zone data (ns0.xname.org)
May 20 18:07:14 ns1 named[718]: dns_master_load: mydomain.com:34: ignoring
out-of-zone data (ns1
A 10.0.0.3
MX 10 mail.mydomain.com.
ns0.xname.org. A 195.20.105.149
ns1.xname.org. A 213.133.115.5
here is the error is /var/log/messages:
May 20 18:07:14 ns1 named[718]: dns_master_load: mydomain.com:33: ignoring
out-of-zone data
dear All,
I running named in sandbox as a secondary name server with FreeBSD-5.1.p17,
Named log always complain:
named-xfer exited with signal 6 and slave zone expired for every zone
transfer.
but, when it's running on default mode (no chroot sandbox) or as a
primary server (with chroot sandbox
Hello Again,
As root, as suggested I did -
cp /usr/src/etc/namedb/named.root /etc/namedb/
and also as root -
ndc restart
after which I checked my /var/log/messages file and I still see this =
_Snip__
May 5 06:33:48 zeus named
queue is empty
I used ktrace(1) to see where does the problem come from and it appears
that when postqueue(1) tries to connect to named Unix socket
`/var/spool/postfix/public/showq' from the host and Postfix runs in a
jail, it gets a ECONNREFUSED while it works perfectly when Postfix is not
jailed
PROTECTED]
Subject: Re: dig/named - res_nsend: Protocol not supported
Luke Cowell disturbed my sleep to write:
*Why* do I need to have IPV6 enable ? Is it some configuration option
of named that I overlooked ?
Hm...it could be that named is only listening on IPv6 localhost (::1)
rather than IPv4
Ignore my previously stated question. What I meant to say was:
*Why* do I need to have IPV6 enable ? Is it some configuration option
of named that I overlooked ?
On Feb 6, 2004, at 9:23, Luke Cowell wrote:
Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with
named/dig.
%uname
How do I get only the latest version of named for FreeBSD ?
Thanks for your atention!
Alex.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with
named/dig.
%uname -a
FreeBSD polo.asap.bc.ca 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #1: Thu
Feb 5 16:23:04 PST 2004
[EMAIL PROTECTED]:/usr/src/sys/compile/POLO i386
Here's what's happening.
%dig @localhost
; DiG 8.3
On Thu, Feb 05, 2004 at 08:12:58AM -0200, Alex Jaeckel wrote:
How do I get only the latest version of named for FreeBSD ?
# /usr/ports/dns/bind9
# make install clean
The configuration files live in /usr/local/etc, you will need to
change /etc/rc.conf:
named_program=/usr/local
Luke Cowell disturbed my sleep to write:
*Why* do I need to have IPV6 enable ? Is it some configuration option
of named that I overlooked ?
Hm...it could be that named is only listening on IPv6 localhost (::1)
rather than IPv4 (127.0.0.1) by default, but that seems strange to me.
Try grep
Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with
named/dig.
%uname -a
FreeBSD polo.asap.bc.ca 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #1: Thu
Feb 5 16:23:04 PST 2004
[EMAIL PROTECTED]:/usr/src/sys/compile/POLO i386
Here's what's happening.
%dig @localhost
; DiG 8.3
Hi,
We recently installed FreeBSD 5.2 RC2 on an i386 platform and we are
noticing intermittent slowness/timeouts on DNS when querying from remote PCs
(i.e. it is an ISP DNS, users trying to resolve domain names). (You may
test, the IP is 206.117.248.2.)
Has anything like this been reported?
On Sun, Feb 01, 2004 at 04:41:02PM -0500, Xpression wrote:
Hi list, I have running named/BIND as DNS server, recently I have
some problems and I don't know the source of it, I have checked the logs and
config files but there is nothing unusual, here is my configs files, any
suggestion
Hi list, I have running named/BIND as DNS server, recently I have
some problems and I don't know the source of it, I have checked the logs and
config files but there is nothing unusual, here is my configs files, any
suggestion ???
named.root
On Sunday 01 February 2004 22:41, Xpression wrote:
Hi list, I have running named/BIND as DNS server, recently I have
some problems and I don't know the source of it, I have checked the logs
and config files but there is nothing unusual, here is my configs files,
any suggestion
Hello,
I have a bind9 named running on the 4.x stable branch, and have noticed
that it seems to be sending udp packets to 127.0.0.2:52 about once
every 10 seconds or so (ipfw is denying and logging the traffic).
Google has not shed any light on the subject.
I've grepped all through /etc
I have a bind9 named running on the 4.x stable branch, and have noticed
that it seems to be sending udp packets to 127.0.0.2:52 about once
every 10 seconds or so (ipfw is denying and logging the traffic).
Google has not shed any light on the subject.
127.0.0.2 is often returned by RBLs
/rndc.conf
d) Paste the copied key statement here.
4) In rc.conf
named_enable=YES
named_program=/usr/local/sbin/named
named_flags=-c /etc/namedb/named.conf -u bind
5) In /etc/named.conf
At the top of the file
// Use the key
include /usr/local
If I understand correctly, both freeBSD 4.9 and the 5 series use BIND 8.
I would like to replace this with BIND 9. What is the proper way to do
so? Do I need to uninstall BIND 8 in some way before using ports or
packages to install BIND 9?
Thanks
PCP
to named in your /etc/rc.conf to point to the version of
named you wish to run. So, set named_program in /etc/rc.conf to
/usr/local/sbin/named.
Trevor Cornpropst
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
# [EMAIL PROTECTED] / 2003-12-16 22:01:33 +0100:
PS: BTW, is there a search engine on freebsd.org for the archives or
do I have to stay with google, which becomes less usable each day?)
another option is marc.theaimsgroup.com
--
If you cc me or remove the list(s) completely I'll most
wasn't much help. I'm thinking that a rebuild
of NAMED might be in order.
Any ideas?
Verify that your cvsupfile is complete; e.g. you may not be updating
the contrib sources.
Kris
pgp0.pgp
Description: PGP signature
Hi!
what measures can I take against this irregular appearing Denial-Of-Service
attacks of named which is filling my logfiles (messages, daemon, all.log)
with messages like sysquery: no addrs found for root NS for minutes
at a rate of 4000 lines/sec?
Here's what I have done on my FreeBSD 4.8
wasn't much help. I'm thinking that a
rebuild
of NAMED might be in order.
Any ideas?
Verify that your cvsupfile is complete; e.g. you may
not be updating
the contrib sources.
Kris
ATTACHMENT part 2 application/pgp-signature
__
Do you Yahoo!?
New
hi freebsd experts, i am a complete newbie and seem to need lots of help on get my
name server running.
1) i keep getting these messages every few minutes on my screen.
bind(dfd=20, [xxx.xxx.1.103].53): Address already in use
Dec 15 12:41:48 host named[5142]: deleting interface [xxx.xxx.1.103].53
On Fri, Dec 19, 2003 at 09:53:04AM -0800, Gary Lum wrote:
Hmmm Looks like it is uptodate. my cvsupfile does
have 'src-contrib' listed. I checked
usr/src/contrib/bind and the dates for the build files
are Dec 16th. However, the readme is from 2002.
What if I blew away the bind folder and
On Thu, Dec 18, 2003 at 12:58:41PM +0100, Robert Eckardt wrote:
On Tue, 16 Dec 2003 20:28:10 -0800, Kris Kennaway wrote
On Tue, Dec 16, 2003 at 10:01:33PM +0100, Robert Eckardt wrote:
Hi,
what measures can I take against this irregular appearing Denial-Of-Service
attacks of named
On Thu, Dec 18, 2003 at 04:26:18PM +0100, Miguel Mendez wrote:
./Kris Kennaway wrote:
I was; if you're complaining about bugs in old versions of the
software, then the first thing to do is check whether those bugs have
been fixed in later versions. Not all bug fixes are properly
Robert Eckardt [EMAIL PROTECTED] writes:
PS: BTW, is there a search engine on freebsd.org for the archives or
do I have to stay with google, which becomes less usable each day?)
You can use http://freebsd.rambler.ru/
--
Dan Pelleg
___
Hi,
what measures can I take against this irregular appearing Denial-Of-Service
attacks of named which is filling my logfiles (messages, daemon, all.log)
with messages like sysquery: no addrs found for root NS for minutes at
a rate of 4000 lines/sec?
I'm using named 8.3.3-REL on FBSD-5.0R
On Tue, Dec 16, 2003 at 10:01:33PM +0100, Robert Eckardt wrote:
Hi,
what measures can I take against this irregular appearing Denial-Of-Service
attacks of named which is filling my logfiles (messages, daemon, all.log)
with messages like sysquery: no addrs found for root NS for minutes
am not having much success setting up
BIND in a sandbox.
The box is running FreeBSD-4.9Stable (after initially installing
4.8-Rel) after cvsup of sources.
Basically, the errors I get on start up is here:
/etc/namedb/etc # tail /var/log/messages
Nov 29 15:42:39 Demon named[226]: 'masters
On Sat, 29 Nov 2003 15:39:50 +
Matthew Seaman [EMAIL PROTECTED] wrote something
special:
On Sat, Nov 29, 2003 at 03:23:48PM +0100, Axel S. Gruner wrote:
/usr/sbin/named
i get this error message:
opensocket_f: bind([0.0.0.0].53): Address already in use
Ok, Port 53
.
The box is running FreeBSD-4.9Stable (after initially installing 4.8-Rel) after cvsup
of sources.
Basically, the errors I get on start up is here:
/etc/namedb/etc # tail /var/log/messages
Nov 29 15:42:39 Demon named[226]: 'masters' statement present for master zone
'vickiandstacey.com'
Nov 29 15:42:39
On Sat, Nov 29, 2003 at 03:29:40PM +0100, Melvyn Sopacua wrote:
Ok, Port 53 is not in use in the jail nor the hostsystem.
I think the problem is 0.0.0.0, and i have to bind named on the IP of
the jail.
I tested same named configuration on the hostsystem, i thought about
some
Hi.
I have configured named in jail (FreeBSD 5.1-RELEASE-p10).
If i want to start named in the jail
/usr/sbin/named
i get this error message:
opensocket_f: bind([0.0.0.0].53): Address already in use
Ok, Port 53 is not in use in the jail nor the hostsystem.
I think the problem is 0.0.0.0
On Sat, Nov 29, 2003 at 03:23:48PM +0100, Axel S. Gruner wrote:
Hi.
I have configured named in jail (FreeBSD 5.1-RELEASE-p10).
If i want to start named in the jail
/usr/sbin/named
i get this error message:
opensocket_f: bind([0.0.0.0].53): Address already in use
Ok, Port 53
'; Jonathan Chen; Arnason, Arni;
'[EMAIL PROTECTED]'
Subject: Re: upgrade named
On Thu, 6 Nov 2003 08:13:07 -0500
Arnason, Arni [EMAIL PROTECTED] wrote:
8.3.3 is in /usr/sbin
9 went into /usr/local/sbin
modified rc.conf to point to the
new binary
named_program=/usr/local/sbin/named
but I'm
8.3.3 is in /usr/sbin
9 went into /usr/local/sbin
modified rc.conf to point to the
new binary
named_program=/usr/local/sbin/named
but I'm still stuck with 8.3.3
ps shows my named up and running but a
which named still points to my 8.3.3 version
doesn't make sense to me, should be working
301 - 400 of 514 matches
Mail list logo
