添加链接
link管理
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接
Hi,

My adventures continue: My logs are filling up with messages like the
following:

May 25 19:01:16 atlanta unbound: [31267:0] notice: sendto failed:
Invalid argument
May 25 19:01:16 atlanta unbound: [31267:0] notice: remote address is
208.67.220.220 port 53

I'm assuming this stems from my attempt to implement dnscrypt (which
seemed fairly disastrous even after I got the other problem solved).
I've tried backing out those changes, but I'm now unable to find the
web page where I found the directions which I followed.

Here again (but modified a bit since the last time) is the configuration:

atlanta# egrep -v "^[[:space:]]*#|^$" /etc/unbound/unbound.conf
server:
verbosity: 1
extended-statistics: yes
interface: 10.8.0.1
outgoing-interface: 127.0.0.1
do-ip4: yes
do-ip6: yes
do-udp: yes
do-tcp: yes
access-control: 0.0.0.0/0 refuse
access-control: 127.0.0.0/8 allow
access-control: 10.8.0.0/16 allow
access-control: ::0/0 refuse
access-control: ::1 allow
chroot: ""
harden-referral-path: yes
use-caps-for-id: yes
private-address: 10.0.0.0/8
private-address: 172.16.0.0/12
private-address: 192.168.0.0/16
private-address: 192.254.0.0/16
private-address: fd00::/8
private-address: fe80::/10
do-not-query-localhost: yes
prefetch: yes
prefetch-key: yes

auto-trust-anchor-file: "/etc/unbound/dnssec_root.key"
val-log-level: 2

local-zone: "parts-unknown.org." static
local-data: "parts-unknown.org. IN A 74.207.225.79"
local-data: "parts-unknown.org. IN MX 10 parts-unknown.org."
local-data: "atlanta.parts-unknown.org. IN A 10.8.0.1"
local-data: "graton.parts-unknown.org. IN A 10.8.0.10"
local-data: "graton.parts-unknown.org. IN MX 20 parts-unknown.org."
local-data: "graton.parts-unknown.org. IN MX 10
graton.parts-unknown.org."
local-data: "n4rky.parts-unknown.org. IN A 10.8.0.22"
local-data: "notary.parts-unknown.org. IN A 10.8.0.1"
local-data: "www.parts-unknown.org. IN A 74.207.225.79"
local-data: "s.parts-unknown.org. IN A 74.207.225.79"
local-zone: "cybernude.org." static
local-data: "cybernude.org. IN A 173.230.137.73"
local-data: "cybernude.org. IN MX 10 parts-unknown.org."
local-data: "atlanta.cybernude.org. IN A 10.8.0.1"
local-data: "graton.cybernude.org. IN A 10.8.0.10"
local-data: "graton.cybernude.org. IN MX 20 parts-unknown.org."
local-data: "graton.cybernude.org. IN MX 10 graton.parts-unknown.org."
local-data: "n4rky.cybernude.org. IN A 10.8.0.22"
local-data: "www.cybernude.org. IN A 10.8.0.10"
local-data: "s.cybernude.org. IN A 173.230.137.73"
local-zone: "disunitedstates.com." static
local-data: "disunitedstates.com. IN A 173.230.137.73"
local-data: "disunitedstates.com. IN MX 10 parts-unknown.org."
local-data: "atlanta.disunitedstates.com. IN A 10.8.0.1"
local-data: "graton.disunitedstates.com. IN A 10.8.0.10"
local-data: "graton.disunitedstates.com. IN MX 10
graton.parts-unknown.org."
local-data: "graton.disunitedstates.com. IN MX 20
parts-unknown.org."
local-data: "n4rky.disunitedstates.com. IN A 10.8.0.22"
local-data: "www.disunitedstates.com. IN A 173.230.137.73"
local-data: "www.joomla.disunitedstates.com. IN A 173.230.137.73"
local-data: "s.disunitedstates.com. IN A 173.230.137.73"
local-zone: "disunitedstates.org." static
local-data: "disunitedstates.org. IN A 173.230.137.76"
local-data: "disunitedstates.org. IN MX 10 parts-unknown.org."
local-data: "atlanta.disunitedstates.org. IN A 10.8.0.1"
local-data: "graton.disunitedstates.org. IN A 10.8.0.10"
local-data: "graton.disunitedstates.org. IN MX 20
parts-unknown.org."
local-data: "graton.disunitedstates.org. IN MX 10
graton.parts-unknown.org."
local-data: "n4rky.disunitedstates.org. IN A 10.8.0.22"
local-data: "www.disunitedstates.org. IN A 173.230.137.76"
local-data: "s.disunitedstates.org. IN A 173.230.137.76"
local-zone: "n4rky.me." static
local-data: "n4rky.me. IN A 173.230.137.73"
local-data: "n4rky.me. IN MX 10 parts-unknown.org."
local-data: "atlanta.n4rky.me. IN A 10.8.0.1"
local-data: "graton.n4rky.me. IN A 10.8.0.10"
local-data: "n4rky.n4rky.me. IN A 10.8.0.22"
local-data: "www.n4rky.me. IN A 173.230.137.73"
local-data: "s.n4rky.me. IN A 173.230.137.73"
local-data-ptr: "10.8.0.1 atlanta.parts-unknown.org"
local-data-ptr: "10.8.0.10 graton.parts-unknown.org"
local-data-ptr: "10.8.0.22 n4rky.parts-unknown.org"
python:
remote-control:
control-enable: yes
control-interface: 127.0.0.1
forward-zone:
name: "."
forward-addr: 208.67.222.222
forward-addr: 208.67.220.220
atlanta#

What am I doing wrong?

Thanks!
- --
David Benfell
***@parts-unknown.org
Post by David Benfell
Hi,
My adventures continue: My logs are filling up with messages like
remote address is 208.67.220.220 port 53
I'm assuming this stems from my attempt to implement dnscrypt
(which seemed fairly disastrous even after I got the other problem
solved). I've tried backing out those changes, but I'm now unable
to find the web page where I found the directions which I
followed.
Well, I'm actually balding and greying (from black), but I guess this
Post by David Benfell
outgoing-interface: 127.0.0.1
Thanks to the person who wrote me off-list to point this out.


- --
David Benfell
***@parts-unknown.org
Post by David Benfell
Post by David Benfell
remote address is 208.67.220.220 port 53
I'm assuming this stems from my attempt to implement dnscrypt
(which seemed fairly disastrous even after I got the other problem
solved). I've tried backing out those changes, but I'm now unable
to find the web page where I found the directions which I
followed.
Well, I'm actually balding and greying (from black), but I guess this
Post by David Benfell
outgoing-interface: 127.0.0.1
I have a real IP in there, but still get these

May 26 11:46:54 debian unbound: [18205:0] notice: sendto failed: Invalid argument
May 26 11:46:54 debian unbound: [18205:0] notice: remote address is 80.236.108.223 port 0

Jun 10 16:40:57 debian unbound: [18205:0] notice: sendto failed: Invalid argument
Jun 10 16:40:57 debian unbound: [18205:0] notice: remote address is 67.215.13.106 port 0

and these

Jun 14 02:35:14 debian unbound: [18205:0] notice: sendto failed: Resource temporarily unavailable
Jun 14 02:35:14 debian unbound: [18205:0] notice: remote address is 64.40.8.45 port 25345

I'm on 1.4.16 atm.


If someone could share tips about what to do, that would be nice!


Kind regards,
--Toni++
Post by Toni Mueller
Post by David Benfell
Well, I'm actually balding and greying (from black), but I guess this
Post by David Benfell
outgoing-interface: 127.0.0.1
I have a real IP in there, but still get these
May 26 11:46:54 debian unbound: [18205:0] notice: sendto failed: Invalid argument
May 26 11:46:54 debian unbound: [18205:0] notice: remote address is 80.236.108.223 port 0
Jun 10 16:40:57 debian unbound: [18205:0] notice: sendto failed: Invalid argument
Jun 10 16:40:57 debian unbound: [18205:0] notice: remote address is 67.215.13.106 port 0
and these
Jun 14 02:35:14 debian unbound: [18205:0] notice: sendto failed: Resource temporarily unavailable
Jun 14 02:35:14 debian unbound: [18205:0] notice: remote address is 64.40.8.45 port 25345
I'm on 1.4.16 atm.
Looks like your firewall might be blocking udp port 53?

Try:

iptables -I INPUT -p all --dport 53 -j ACCEPT
iptables -I OUTPUT -p all --sport 53 -j ACCEPT

Paul
Hi,
Post by Paul Wouters
Post by Toni Mueller
I have a real IP in there, but still get these
May 26 11:46:54 debian unbound: [18205:0] notice: sendto failed: Invalid argument
May 26 11:46:54 debian unbound: [18205:0] notice: remote address is 80.236.108.223 port 0
Jun 10 16:40:57 debian unbound: [18205:0] notice: sendto failed: Invalid argument
Jun 10 16:40:57 debian unbound: [18205:0] notice: remote address is 67.215.13.106 port 0
and these
Jun 14 02:35:14 debian unbound: [18205:0] notice: sendto failed: Resource temporarily unavailable
Jun 14 02:35:14 debian unbound: [18205:0] notice: remote address is 64.40.8.45 port 25345
I'm on 1.4.16 atm.
Looks like your firewall might be blocking udp port 53?
thanks for the idea, but I can safely rule these out. I also run an
authoritative nameserver on the same network.


Kind regards,
--Toni++
Post by Toni Mueller
Post by Paul Wouters
Looks like your firewall might be blocking udp port 53?
thanks for the idea, but I can safely rule these out. I also run an
authoritative nameserver on the same network.
I meant a firewall on your server itself, since you're getting a packet
denied error.

Paul