We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in the first with the documentation and without any zone created when i start the container i get this output
bind-9 | 19-Apr-2023 14:45:02.132 DNS format error from 192.58.128.30#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 14:45:02.132 FORMERR resolving './NS/IN': 192.58.128.30#53 bind-9 | 19-Apr-2023 14:45:02.132 DNS format error from 192.112.36.4#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 14:45:02.132 FORMERR resolving './NS/IN': 192.112.36.4#53 bind-9 | 19-Apr-2023 14:45:02.132 resolver priming query complete: failure
~ nslookup youtube.com 22.10.20.46 Server: 22.10.20.46 Address: 22.10.20.46#53
** server can't find youtube.com: SERVFAIL
bind-9 | 19-Apr-2023 14:48:58.043 address not available resolving 'com/DS/IN': 2001:503:ba3e::2:30#53 bind-9 | 19-Apr-2023 14:48:58.043 broken trust chain resolving 'youtube.com/A/IN': 1.1.1.1#53
ind-9 | 19-Apr-2023 15:00:46.429 managed-keys-zone: loaded serial 0 bind-9 | 19-Apr-2023 15:00:46.441 all zones loaded bind-9 | 19-Apr-2023 15:00:46.441 running
Non-authoritative answer: Name: youtube.com Address: 142.250.66.14
bind-9 | 19-Apr-2023 15:02:30.908 DNS format error from 198.97.190.53#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 15:02:30.908 FORMERR resolving './NS/IN': 198.97.190.53#53 bind-9 | 19-Apr-2023 15:02:30.908 resolver priming query complete: failure
The text was updated successfully, but these errors were encountered:
after adding the zone files and details i am unable to to resolve to my local record i am getting Can't find demo.mavask.in: No answer
but able to resolve the youtube.com
Sorry, something went wrong.
I am having the same issue. Anyone else have this issue and resolve it?
No branches or pull requests
In the bind9-docker-compose guide
in the first with the documentation and without any zone created when i start the container i get this output
in terminal after running docker compose up
bind-9 | 19-Apr-2023 14:45:02.132 DNS format error from 192.58.128.30#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 14:45:02.132 FORMERR resolving './NS/IN': 192.58.128.30#53 bind-9 | 19-Apr-2023 14:45:02.132 DNS format error from 192.112.36.4#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 14:45:02.132 FORMERR resolving './NS/IN': 192.112.36.4#53 bind-9 | 19-Apr-2023 14:45:02.132 resolver priming query complete: failure
in my system terminal running nslookup
~ nslookup youtube.com 22.10.20.46
Server: 22.10.20.46
Address: 22.10.20.46#53
** server can't find youtube.com: SERVFAIL
in terminal after running nslookup
bind-9 | 19-Apr-2023 14:48:58.043 address not available resolving 'com/DS/IN': 2001:503:ba3e::2:30#53 bind-9 | 19-Apr-2023 14:48:58.043 broken trust chain resolving 'youtube.com/A/IN': 1.1.1.1#53
Then i added dnssec-validation no in named.conf
in terminal after running docker compose up
ind-9 | 19-Apr-2023 15:00:46.429 managed-keys-zone: loaded serial 0 bind-9 | 19-Apr-2023 15:00:46.441 all zones loaded bind-9 | 19-Apr-2023 15:00:46.441 running
in my system terminal running nslookup
~ nslookup youtube.com 22.10.20.46
Server: 22.10.20.46
Address: 22.10.20.46#53
Non-authoritative answer:
Name: youtube.com
Address: 142.250.66.14
in terminal after running nslookup
bind-9 | 19-Apr-2023 15:02:30.908 DNS format error from 198.97.190.53#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 15:02:30.908 FORMERR resolving './NS/IN': 198.97.190.53#53 bind-9 | 19-Apr-2023 15:02:30.908 resolver priming query complete: failure
the nslookup seams to be working but the output looks like something is wrong somewhere
The text was updated successfully, but these errors were encountered: