Nameservers are hitting an address of yours. Therefore something is
probably handing out your address. Somebody (that would be me) has
looked up the address in question and even looked up the nameserver
which is handing out that address in a glue record.
A simple problem EASILY solved.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jon Radel
Sent: Tuesday, June 10, 2008 4:02 PM
To: Wojciech Puchar
Cc: freebsd-questions@freebsd.org
Subject: Re: OT: lots of IPv6 DNS requests
Nameservers are hitting an address of yours
pearl# dig dns3.tensor.gdynia.pl
dns3.tensor.gdynia.pl. 21682 IN 2001:4070:101:2::1
that's funny because i have in my domain:
dns3A 213.192.74.1
dns32001:4070:101::1
not :2::1
tried my secondary dns - the same.
can find to any DNS query.
After a few days the owners of the misconfigured nameservers
or clients will go hunting for whatever is poisoning their cache.
Problem solved.
Ted
when i will be sure it is not my fault i would do this ;) but now i
actually don't know where is a problem
Do a netstat -na | grep 53. This will help. Something is wrong with your
setup if you are seeing undesirable results.
all OK, on port 53 my named is listening. it is used as cache-only DNS for
my computer and few others.
yes i can just block out accesses from outside 2001:4070:101:2::/64
Ted Mittelstaedt wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jon Radel
Sent: Tuesday, June 10, 2008 4:02 PM
To: Wojciech Puchar
Cc: freebsd-questions@freebsd.org
Subject: Re: OT: lots of IPv6 DNS requests
Nameservers are hitting an address
Wojciech Puchar wrote:
pearl# dig dns3.tensor.gdynia.pl
dns3.tensor.gdynia.pl. 21682 IN 2001:4070:101:2::1
that's funny because i have in my domain:
dns3A 213.192.74.1
dns32001:4070:101::1
not :2::1
tried my
Camilo Reyes wrote:
The easiest way to deal with this is to disable IPv6 on your kernel.
There is a good guide here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html.
Simply comment out the 'options INET6' line from your config file. Also,
you could give more
$ dig @bilbo.nask.org.pl tensor.gdynia.pl ns
so something is broken with my registrar. as other dns'es reports only 2
nameservers.
host -t ns tensor.gdynia.pl dns.task.gda.pl
reports 2 of them, and dns.task.gda.pl is main dns for gdynia.pl
thank you for finally explaining things
-Original Message-
From: Jon Radel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 6:15 AM
To: Ted Mittelstaedt
Cc: Wojciech Puchar; freebsd-questions@freebsd.org
Subject: Re: OT: lots of IPv6 DNS requests
Ted Mittelstaedt wrote:
-Original Message
: lots of IPv6 DNS requests Was: Re:
freebsd-questions
Digest, Vol 219, Issue 6
To: [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
Camilo Reyes wrote:
The easiest way to deal with this is to disable IPv6
Ted Mittelstaedt wrote:
-Original Message-
From: Jon Radel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 6:15 AM
To: Ted Mittelstaedt
Cc: Wojciech Puchar; freebsd-questions@freebsd.org
Subject: Re: OT: lots of IPv6 DNS requests
Ted Mittelstaedt wrote:
-Original
Wojciech Puchar wrote:
i'm getting lots of things like this in logs:
Jun 10 17:13:50 wojtek named[909]: client
2610:130:101:100:214:22ff:fe12:241#60282: query (cache)
'wojtek.tensor.gdynia.pl/MX/IN' denied
Post:
# ifconfig -a
# netstat -na | grep 53
Looks like named may be listening
Wojciech Puchar wrote:
Jun 10 17:14:32 wojtek named[909]: client
2001:4830:167d:5237::3:1#59882: query (cache)
'wojtek.tensor.gdynia.pl//IN' denied
Jun 10 17:14:32 wojtek named[909]: client
2001:4830:167d:5237::3:1#59882: query (cache)
'wojtek.tensor.gdynia.pl/ANY/IN' denied
my
2610:130:101:100:214:22ff:fe12:241#60282: query (cache)
'wojtek.tensor.gdynia.pl/MX/IN' denied
Post:
# ifconfig -a
# netstat -na | grep 53
Looks like named may be listening publicly on IPv6, but then refusing the
requests.
yes it does. but allows requests only for limited set of
why they are asking?
Because your computer is reachable on either
dns.tensor.gdynia.pl. 10800 IN 2001:4070:101::1
or
dns2.tensor.gdynia.pl. 10732 IN 2001:4070:101:1::2
no it is not! that's why i'm asking.
___
Wojciech Puchar wrote:
why they are asking?
Because your computer is reachable on either
dns.tensor.gdynia.pl. 10800 IN 2001:4070:101::1
or
dns2.tensor.gdynia.pl. 10732 IN 2001:4070:101:1::2
no it is not! that's why i'm asking.
Oh, for heaven's sake.
dns.tensor.gdynia.pl. 10800 IN 2001:4070:101::1
or
dns2.tensor.gdynia.pl. 10732 IN 2001:4070:101:1::2
no it is not! that's why i'm asking.
Oh, for heaven's sake. We all know you like to shoot off your mouth. Now go
back to my mail and read it ALL THE WAY
Wojciech Puchar wrote:
dns.tensor.gdynia.pl. 10800 IN 2001:4070:101::1
or
dns2.tensor.gdynia.pl. 10732 IN 2001:4070:101:1::2
no it is not! that's why i'm asking.
Oh, for heaven's sake. We all know you like to shoot off your mouth.
Now go back to my mail
Jon Radel wrote:
dns3.tensor.gdynia.pl. 28800 IN 2001:4070:101:2::1
Sorry Jon, I completely missed that the first time through ;)
Steve
___
freebsd-questions@freebsd.org
Wojciech Puchar wrote:
dns.tensor.gdynia.pl. 10800 IN 2001:4070:101::1
or
dns2.tensor.gdynia.pl. 10732 IN 2001:4070:101:1::2
no it is not! that's why i'm asking.
Oh, for heaven's sake. We all know you like to shoot off your mouth.
Now go back to my
Wojciech Puchar wrote:
no it is not! that's why i'm asking.
Oh, for heaven's sake. We all know you like to shoot off your mouth.
Now go back to my mail and read it ALL THE WAY THROUGH BEFORE YOU
ANSWER AGAIN. Jeez.
so maybe you should explain clearer because i do read what you write.
22 matches
Mail list logo
