I've got a bind recursion DNS server setup that is returning the wrong
value for an outside domain that I also maintain and host on another server
running a bind DNS server. Yet Google's DNS and other major DNS providers
respond with the correct IP address A record when querying. I can't figure
o
On 16.07.23 02:08, OwN-3m-All wrote:
I've got a bind recursion DNS server setup that is returning the wrong
value for an outside domain that I also maintain and host on another server
running a bind DNS server. Yet Google's DNS and other major DNS providers
respond with the correct IP address A
Real data please:
- example queries (genuine, not invented for illustration)
- real domains
- real IP addresses
- packet captures
- both BIND server configs
- zone file contents
- startup logs
There are so many things it *could* be, the more information the better.
Cheers, Greg
On Sun, 16 Jul 20
Also:- make the record self-contained, don’t make us go elsewhere, especially not to a place where data could disappear at the whim of the owner (as seen recently)- and finally, describe what you see, don’t speculate what it might be; by describing you are less likely to miss an important detailOnd
Spam assassin is blocking my message, so here are all the details (my
latest response message):
https://pastebin.com/raw/jSm6aGfC
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
This time from the correct email alias!
On Mon, 17 Jul 2023 at 22:58, Greg Choules
wrote:
> Hi.
> Some observations:
> - Please don't use nslookup. Please use dig, it is much more versatile and
> gives much more information with which to try and interpret what might be
> going on.
> - If you're
The output from "named-checkconf -px" is over a million lines long, but
here you go:
http://23.29.117.19/bindconf.zip
My resolver servers are setup for ad-blocking, hence why there are so many
defined zones.
Here is a quick tcpdump sample where I do not see anything too helpful:
http://23.29.11
I turned logging on, but I'm still not seeing anything that can help me
pinpoint why the query is failing?
Audit log:
18-Jul-2023 19:45:14.938 client @0x7f26e6def368 23.29.117.19#44526 (*.
wildcard-test.dynx.me): query: *.wildcard-test.dynx.me IN A -E(0)DCV
(23.29.117.19)
18-Jul-2023 19:45:22.142
Ok, I fixed the problem.
I changed the zonefile templates for dynamic DNS used at dynamix.run to the
following:
$TTL60
@ IN SOA ns.{domainname}. ad...@dynamix.run (
{serial} ;
30 ; Refresh
20; Retr
9 matches
Mail list logo
