cmdns.dev.dns-oarc.net oddness with windows 10 and bind
legacyone at virginmedia.com
Thu Jun 10 16:17:10 UTC 2021
So I redone my windows bind setup on a new system and this bug may never
get fixed but I wanted to post the oddness of this bug.
Bind on New PC as servers 127.0.0.1 for dns on that system
cmdns.dev.dns-oarc.net reports fine except for IPv6 test OK
I then have two PC's as clients to this DNS bind server 192.168.255.62
and 192.168.53.2 the internet works fine DNS seems to work fine but
testing at cmdns.dev.dns-oarc.net shows some failed tests for IPv4.
And it gets odder if on that PC I remove 192.168.255.62 and 192.168.53.2
and put in 127.0.0.1 setup bind with forwarder only 192.168.255.62 and
192.168.53.2 then run cmdns.dev.dns-oarc.net it shows as fine!
I just don't get it?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users