The last (and presumably final) point release (6.5) of NetWare was in
2003, only 4 years after RFC 2671. Just saying...
- Kevin
On 4/30/2013 7:08 PM, Pascal wrote:
Thank you. That does appear to be the problem.
-Pascal
On 4/30/2013 5:
Thank you. That does appear to be the problem.
-Pascal
On 4/30/2013 5:17 PM, Mark Andrews wrote:
BIND 9.9 dig turns on EDNS by default. You really should be asking
why 172.31.123.6 doesn't suppport EDNS nearly 14 years after it was
specified (RFC 2671 August 1999).
Add +noedns to the comman
Sorry, I guess I wasn't clear enough. I was just using
www.alarmspecs.com as a sample domain. As you see, that domain is
working fine.
My problem is 172.31.123.6 is a NetWare DNS server. I maintain several
in different locations and trees. Any time I try to use Dig 9.9 against
one of them
In message <51803fd2.3070...@users.sourceforge.net>, Pascal writes:
> Dig 9.9 consistently gives me "FORMERR" against NetWare DNS servers.
> Previous versions worked fine. Suggestions on how to figure out if the
> bug is in Dig or NetWare?
>
> -Pascal
BIND 9.9 dig turns on EDNS by default. Y
On Tue, 2013-04-30 at 17:04 -0500, Pascal wrote:
> Dig 9.9 consistently gives me "FORMERR" against NetWare DNS servers.
> Previous versions worked fine. Suggestions on how to figure out if the
> bug is in Dig or NetWare?
>
> -Pascal
>
> O:\Documents and Settings\admin\dig\9.9.2-P2>dig www.
Dig 9.9 consistently gives me "FORMERR" against NetWare DNS servers.
Previous versions worked fine. Suggestions on how to figure out if the
bug is in Dig or NetWare?
-Pascal
O:\Documents and Settings\admin\dig>dig www.alarmspecs.com @172.31.123.6
; <<>> DiG 9.8.4-P2 <<>> www.alarmspecs.com
6 matches
Mail list logo
