AXFR from Windows 2008R2 failing after upgrading to 9.18
Lefteris Tsintjelis
lefty at spes.gr
Tue May 24 01:50:42 UTC 2022
Error seems to be related to character set checking. I do have the zone
configured to ignore checking names but it doesn't seem to work.
zone "domain.com" { type secondary; primaries { 1.1.2.2; }; check-names
ignore; max-journal-size 32k; masterfile-format text; file
"/usr/local/etc/namedb/secondary/db.domain.com"; };
On 24/5/2022 4:12, Lefteris Tsintjelis via bind-users wrote:
> I turned on all logs channels and this is the error I get:
>
> zone domain.com/IN: refresh: unexpected rcode (FORMERR) from primary
> 1.1.2.2#53 (source 0.0.0.0#0
>
> tcpdump seems to also agree with the FORMERR
>
> 1.1.2.2.domain > secondary.58648: 113 FormErr- 0/0/1 (45)
>
> Regards,
>
> Lefteris
>
> On 24/5/2022 3:00, Grant Taylor via bind-users wrote:
>> On 5/23/22 5:55 PM, Lefteris Tsintjelis via bind-users wrote:
>>> Nothing actually. Windows logs are clean. Unix logs also.
>>
>> #trustTheBitsOnTheWire
>> #useTheSniffer
>>
>> I'd start by capturing w/ tcpdump using the `-s 0` and `-w
>> /path/to/capture.pcapng` options. Then use Wireshark to analyze the
>> packet capture.
>>
>> You may see the problem with tcpdump, especially if you turn verbosity
>> up. But Wireshark has some much nicer decoding and display than
>> tcpdump does.
More information about the bind-users
mailing list