On 10.05.2025 05:29, bi...@clearviz.biz
wrote:
>Also check /etc/resolv.conf and see what address(es) is/are
listed as nameservers.
The resolv.conf file
contains:
nameserver
127.0.0.53
search
mydom
Well, let's put it this way. I have been monitoring the logs
(/var/log/syslog in particular) as well as the separate logs I created
(named.log and query.log). I'm getting a lot of "Connection refused"
errors and a lot of "SERVFAIL" errors in named.log for various sites. I
don't know if the quer
Based on that I'm pretty confident you can remove this as being a general DNS
server issue.
I would not attempt to even change the configuration in bind at this point as
to not introduce more potential changes into your env as doing those tests will
have mostly validated the DNS server is worki
If you’re hobbled by Windows (and ones five years past EOL), I prefer to
fire up PowerShell and use Resolve-DnsName. Also include the -DnsOnly flag.
Have you been looking at the BIND logs?
Also, a BIND installation isn’t going to mess with resolv.conf. That’s
typically managed by the distro’s net
I also suspect it's not BIND, but how the OS is going about resolving
names.
Test your running BIND by using dig (please, not nslookup) @127.0.0.1
[1] for domains you think you are having a problem with.
Should it be @127.0.0.1 or should it be the machine's IP on which the
DNS server is runnin
From the instance with bind running, can you query both your defined
forwarders? Does it work consistently for a variety of domains?
dig @1.1.1.1 isc.org
dig @8.8.8.8 isc.org
Yes, it does. The above two commands work as well as several other
domains I tried, and the response has been immedia
I noted that it appears your internal network is 123.123.123.0/24. This
ip range is assigned globally to a Chinese ISP. This may not be a good
idea.
I agree that using forwarding is not necessary and may introduce some
issues.
And yes, you need to stop using nslookup and use dig instead.
On Saturday, 10 May 2025 01:35:28 CEST Greg Choules via bind-users wrote:
> Third, use tcpdump to capture port 53. Do this to a file, then look at it
> offline in Wireshark. (Michael just beat me to that tip). Check how queries
> are arriving into BIND and what it does with them. Particularly look
Hi.
I also suspect it's not BIND, but how the OS is going about resolving names.
Test your running BIND by using dig (please, not nslookup) @127.0.0.1 for
domains you think you are having a problem with.
Also check /etc/resolv.conf and see what address(es) is/are listed as
nameservers.
Third, use
I get a feeling this is going to be less of a bind issue, and more so some
other configuration issue(s).
>From the instance with bind running, can you query both your defined
>forwarders? Does it work consistently for a variety of domains?
dig @1.1.1.1 isc.org
dig @8.8.8.8 isc.org
>From the cl
On Saturday, 10 May 2025 01:18:17 CEST Michael De Roover wrote:
[...]
I do remember writing a reply that got lost while drafting my previous email,
but I don't remember what exactly it is. I do, however, remember its contents,
somewhat. I'll just rewrite it in reply to.. this, I guess.
You'll wa
On Saturday, 10 May 2025 00:58:25 CEST bi...@clearviz.biz wrote:
> Howdy all!. My name is Arnold, and I'm new to both Bind9 and to the
> Bind user's list. I'm hoping to contribute my findings on the use of
> Bind9. in the future but, for now, I need some help in getting my 1st
> install of Bind 9
Howdy all!. My name is Arnold, and I'm new to both Bind9 and to the
Bind user's list. I'm hoping to contribute my findings on the use of
Bind9. in the future but, for now, I need some help in getting my 1st
install of Bind 9.18 performing well. It does run already, but does not
perform well a
13 matches
Mail list logo
