BIND Server running but not responding
Warren Kumari
warren at kumari.net
Wed Apr 18 13:59:10 UTC 2018
I'm *really* not a Windows person, but all of the "could not listen on
UDP socket: permission denied" log messages strongly imply that BIND
is not able to bind() to the socket -- can you try start this with
something like Administrator privileges?
W
On Wed, Apr 18, 2018 at 9:51 AM, Admin Hardy <admin at innerface.net> wrote:
>
> I would be so grateful of your help in this issue.
>
> I am running BIND 9 on Windows 7
> Service "ISC BIND" shows as started up
>
> As a temporary measure I have disabled firewall on host and client to rule
> out any issue there.
>
> I have set the DNS IP Address on the client ipv4 to just the address of the
> BIND host 192.168.1.67
>
> I did DNS flush on the client and also cleared any possible DNS caching in
> the client requesting software.
>
> I am requesting resolution for "rota.rotatesting.com" (see below)
>
> the full http request happens to be
> "http://rota.rotatesting.com:8081/mywebapp/"
>
> The client software (browser) cannot resolve the name
> I downloaded dedicated DNS Lookup software and the request times out
> looks like the server is not responding with anything.
>
> Just two of the log files have logging.
>
> I would be really grateful if you could suggest possible causes:
>
> Here is content of file C:\named\zones\db.rotatesting.com.txt
> ===================================================================
> ===================================================================
>
> $TTL 6h
> @ IN SOA AndrewHardy.rotatesting.com. hostmaster.rotatesting.com.
> (
> 2018041801
> 10800
> 3600
> 604800
> 86400 )
>
> @ NS AndrewHardy.rotatesting.com.
>
>
> AndrewHardy IN A 192.168.1.67
> *.rotatesting.com. IN A 192.168.1.67
>
>
> Here is content of file C:\named\etc\named.conf
> ===================================================================
> ===================================================================
>
> options {
> directory "c:\named\zones";
> allow-transfer { none; };
> recursion no;
> };
>
>
> zone "rotatesting.com" IN {
> type master;
> file "db.rotatesting.com.txt";
> allow-transfer { none; };
> };
>
> key "rndc-key" {
> algorithm hmac-md5;
> secret "bBuMhqgS+8IL1SqZAKC+YQ==";
> };
>
> controls {
> inet 127.0.0.1 port 953
> allow { 127.0.0.1; } keys { "rndc-key"; };
> };
>
> logging {
> channel default_file {
> file "C:\named\default.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel general_file {
> file "C:\named\general.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel database_file {
> file "C:\named\database.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel security_file {
> file "C:\named\security.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel config_file {
> file "C:\named\config.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel resolver_file {
> file "C:\named\resolver.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel xfer-in_file {
> file "C:\named\xfer-in.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel xfer-out_file {
> file "C:\named\xfer-out.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel notify_file {
> file "C:\named\notify.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel client_file {
> file "C:\named\client.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel unmatched_file {
> file "C:\named\unmatched.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel queries_file {
> file "C:\named\queries.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel network_file {
> file "C:\named\network.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel update_file {
> file "C:\named\update.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel dispatch_file {
> file "C:\named\dispatch.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel dnssec_file {
> file "C:\named\dnssec.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
> channel lame-servers_file {
> file "C:\named\lame-servers.log" versions 3 size 5m;
> severity dynamic;
> print-time yes;
> };
>
> category default { default_file; };
> category general { general_file; };
> category database { database_file; };
> category security { security_file; };
> category config { config_file; };
> category resolver { resolver_file; };
> category xfer-in { xfer-in_file; };
> category xfer-out { xfer-out_file; };
> category notify { notify_file; };
> category client { client_file; };
> category unmatched { unmatched_file; };
> category queries { queries_file; };
> category network { network_file; };
> category update { update_file; };
> category dispatch { dispatch_file; };
> category dnssec { dnssec_file; };
> category lame-servers { lame-servers_file; };
> };
>
>
>
> Here is content of file C:\named\general.log
> ===================================================================
> ===================================================================
>
> 18-Apr-2018 14:14:21.669 managed-keys-zone: loaded serial 0
> 18-Apr-2018 14:14:21.672 zone rotatesting.com/IN: loaded serial 2018041801
> 18-Apr-2018 14:14:21.693 all zones loaded
> 18-Apr-2018 14:14:21.705 running
>
>
> Here is content of file C:\named\general.log
> ===================================================================
> ===================================================================
>
> 18-Apr-2018 14:14:21.647 additionally listening on IPv4 interface Loopback
> Interface 1, 127.0.0.1#53
> 18-Apr-2018 14:14:21.649 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.649 creating IPv4 interface Loopback Interface 1
> failed; interface ignored
> 18-Apr-2018 14:14:21.650 additionally listening on IPv4 interface TCP/IP
> Interface 2, 192.168.56.1#53
> 18-Apr-2018 14:14:21.650 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.650 creating IPv4 interface TCP/IP Interface 2 failed;
> interface ignored
> 18-Apr-2018 14:14:21.650 additionally listening on IPv4 interface TCP/IP
> Interface 3, 192.168.1.67#53
> 18-Apr-2018 14:14:21.651 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.651 creating IPv4 interface TCP/IP Interface 3 failed;
> interface ignored
> 18-Apr-2018 14:14:21.651 additionally listening on IPv4 interface TCP/IP
> Interface 4, 192.168.184.1#53
> 18-Apr-2018 14:14:21.651 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.651 creating IPv4 interface TCP/IP Interface 4 failed;
> interface ignored
> 18-Apr-2018 14:14:21.652 additionally listening on IPv4 interface TCP/IP
> Interface 5, 192.168.239.1#53
> 18-Apr-2018 14:14:21.652 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.652 creating IPv4 interface TCP/IP Interface 5 failed;
> interface ignored
> 18-Apr-2018 14:14:21.652 additionally listening on IPv4 interface TCP/IP
> Interface 6, 192.168.1.96#53
> 18-Apr-2018 14:14:21.652 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.652 creating IPv4 interface TCP/IP Interface 6 failed;
> interface ignored
> 18-Apr-2018 14:14:21.653 additionally listening on IPv6 interface TCP/IPv6
> Interface 13, 2a00:23c4:2382:e400:d5cc:ac18:6ed5:c742#53
> 18-Apr-2018 14:14:21.653 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.653 creating IPv6 interface TCP/IPv6 Interface 13
> failed; interface ignored
> 18-Apr-2018 14:14:21.653 additionally listening on IPv6 interface TCP/IPv6
> Interface 12, 2a00:23c4:2382:e400:f506:9eb:d989:f2d#53
> 18-Apr-2018 14:14:21.653 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.653 creating IPv6 interface TCP/IPv6 Interface 12
> failed; interface ignored
> 18-Apr-2018 14:14:21.654 additionally listening on IPv6 interface TCP/IPv6
> Interface 11, fdaa:bbcc:ddee:0:d5cc:ac18:6ed5:c742#53
> 18-Apr-2018 14:14:21.654 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.654 creating IPv6 interface TCP/IPv6 Interface 11
> failed; interface ignored
> 18-Apr-2018 14:14:21.654 additionally listening on IPv6 interface TCP/IPv6
> Interface 10, fdaa:bbcc:ddee:0:f506:9eb:d989:f2d#53
> 18-Apr-2018 14:14:21.655 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.655 creating IPv6 interface TCP/IPv6 Interface 10
> failed; interface ignored
> 18-Apr-2018 14:14:21.655 additionally listening on IPv6 interface TCP/IPv6
> Interface 9, 2a00:23c4:2382:e400:c4ee:765d:8ca3:b788#53
> 18-Apr-2018 14:14:21.656 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.656 creating IPv6 interface TCP/IPv6 Interface 9
> failed; interface ignored
> 18-Apr-2018 14:14:21.656 additionally listening on IPv6 interface TCP/IPv6
> Interface 8, 2a00:23c4:2382:e400:d85b:8e7f:ca73:5691#53
> 18-Apr-2018 14:14:21.656 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.656 creating IPv6 interface TCP/IPv6 Interface 8
> failed; interface ignored
> 18-Apr-2018 14:14:21.656 additionally listening on IPv6 interface TCP/IPv6
> Interface 7, fdaa:bbcc:ddee:0:c4ee:765d:8ca3:b788#53
> 18-Apr-2018 14:14:21.657 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.657 creating IPv6 interface TCP/IPv6 Interface 7
> failed; interface ignored
> 18-Apr-2018 14:14:21.657 additionally listening on IPv6 interface TCP/IPv6
> Interface 6, fdaa:bbcc:ddee:0:d85b:8e7f:ca73:5691#53
> 18-Apr-2018 14:14:21.657 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.657 creating IPv6 interface TCP/IPv6 Interface 6
> failed; interface ignored
> 18-Apr-2018 14:14:21.657 additionally listening on IPv6 interface TCP/IPv6
> Interface 5, fe80::d85b:8e7f:ca73:5691%11#53
> 18-Apr-2018 14:14:21.658 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.658 creating IPv6 interface TCP/IPv6 Interface 5
> failed; interface ignored
> 18-Apr-2018 14:14:21.658 additionally listening on IPv6 interface TCP/IPv6
> Interface 4, fe80::2562:bb37:3c69:d4ee%19#53
> 18-Apr-2018 14:14:21.658 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.658 creating IPv6 interface TCP/IPv6 Interface 4
> failed; interface ignored
> 18-Apr-2018 14:14:21.659 additionally listening on IPv6 interface TCP/IPv6
> Interface 3, fe80::2857:1d67:705b:7f76%18#53
> 18-Apr-2018 14:14:21.659 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.659 creating IPv6 interface TCP/IPv6 Interface 3
> failed; interface ignored
> 18-Apr-2018 14:14:21.659 additionally listening on IPv6 interface TCP/IPv6
> Interface 2, fe80::7829:49c8:b84d:6622%14#53
> 18-Apr-2018 14:14:21.659 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.659 creating IPv6 interface TCP/IPv6 Interface 2
> failed; interface ignored
> 18-Apr-2018 14:14:21.660 additionally listening on IPv6 interface TCP/IPv6
> Interface 1, fe80::f506:9eb:d989:f2d%10#53
> 18-Apr-2018 14:14:21.660 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.660 creating IPv6 interface TCP/IPv6 Interface 1
> failed; interface ignored
> 18-Apr-2018 14:14:21.660 additionally listening on IPv6 interface TCP/IPv6
> Loopback Interface, ::1#53
> 18-Apr-2018 14:14:21.661 could not listen on UDP socket: permission denied
> 18-Apr-2018 14:14:21.661 creating IPv6 interface TCP/IPv6 Loopback Interface
> failed; interface ignored
>
>
>
>
>
>
>
>
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
--
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
---maf
More information about the bind-users
mailing list