Am 30.10.2023 um 12:25:32 Uhr schrieb Mosharaf Hossain:
> mofa.gov.bd.86400 IN NS ns1.bcc.gov.bd.
> mofa.gov.bd.86400 IN NS ns2.bcc.gov.bd.
> couldn't get address for 'ns1.bcc.gov.bd': not found
> couldn't get address for 'ns2.bcc.gov.bd': not found
Everything looks good from here in a Debian with 9.18
# nslookup mofa.gov.bd
Server: 193.93.164.194
Address:193.93.164.194#53
Non-authoritative answer:
Name: mofa.gov.bd
Address: 103.163.210.121
Name: mofa.gov.bd
Address: 103.163.210.117
# dig ns mofa.gov.bd
; <<>> DiG 9.18
On 30-Oct-23 03:46, Marco M. wrote:
Am 30.10.2023 um 12:25:32 Uhr schrieb Mosharaf Hossain:
mofa.gov.bd.86400 IN NS ns1.bcc.gov.bd.
mofa.gov.bd.86400 IN NS ns2.bcc.gov.bd.
couldn't get address for 'ns1.bcc.gov.bd': not found
couldn't get address f
Thanks to all who responded. Putting qname-minimization disabled; in named.conf
resolves the issue in my testing.
I did try specifying relaxed (which appears to be the default), but that didn’t
work either.
I agree it would be great if the far ends would make sure what they publish is
correct,
> Am 30.10.2023 um 16:59 schrieb Michael Martinell via bind-users
> :
>
> Thanks to all who responded. Putting qname-minimization disabled; in
> named.conf resolves the issue in my testing.
>
> I did try specifying relaxed (which appears to be the default), but that
> didn’t work either.
>
> On 30 Oct 2023, at 17:25, Mosharaf Hossain
> wrote:
>
> mofa.gov.bd.86400 IN NS ns1.bcc.gov.bd.
> mofa.gov.bd.86400 IN NS ns2.bcc.gov.bd.
> couldn't get address for 'ns1.bcc.gov.bd': not found
> couldn't get address for 'ns2.bcc.gov.bd': not fo
Hello All
The problem of the .gov.bd domain resolution has been successfully
resolved.
In the zone file configuration, there was a forward entry for .gov.bd, and
after commenting out those lines, all .gov.bd domains are now functioning
correctly.
Thank you all for providing the right guidance that
7 matches
Mail list logo