Ok, I fixed the problem.
I changed the zonefile templates for dynamic DNS used at dynamix.run to the
following:
$TTL 60
@ IN SOA ns.{domainname}. ad...@dynamix.run (
{serial} ;
30 ; Refresh
20 ; Retry
1209600 ; Expire
30 ) ; Minimum
{domainname}. IN NS ns.{domainname}.
ns.{domainname}. IN A {serverip}
ns.{domainname}. IN A {serveripBackup}
Rather than:
$TTL 60
@ IN SOA ns.{domainname}. ad...@dynamix.run (
{serial} ;
30 ; Refresh
20 ; Retry
1209600 ; Expire
30 ) ; Minimum
{domainname}. IN NS ns.{domainname}.
ns.{domainname}. IN A {dnsip}
{dnsip} would get updated with the user's dynamic IP address. Thus, if you
were to query specific.wildcard-test.dynx.me, it would send the traffic to
their IP address to resolve, which is not correct, since the record is
defined on the main server, not theirs.
This makes it so queries for that subdomain resolve to that same specific
server, rather than the IP address provided by the end user since it is
acting as the main DNS server, in this case.
But, it still makes no sense to me how google's DNS (and others) was able
to resolve everything just fine... google's dns must not be asking
ns.{domainname}. for the records?
How crazy. I still don't fully understand why this happens, but I could
clearly see tcpdump asking 23.29.117.19 for the A record for
specific.wildcard-test.dynx.me which it has no information about since
there is no zonefile on 23.29.117.19 for wildcard-test.dynx.me...
--
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.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
