Am 12.09.2010 19:03, schrieb Florian Mayer (Mayer Electronics):
Hello,
we have a quite strange DNS behavior in conjunction with a Mikrotik
Router (Rouser OS 4.6): In some cases, DNS works, and in some cases not:
r...@localhost test20]# nslookup www.t-online.de
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: www.t-online.de
Address: 62.153.159.92
Name: www.t-online.de
Address: 217.6.164.162
[r...@localhost test20]# nslookup www.google.de
;; Truncated, retrying in TCP mode.
;; Connection to 127.0.0.1#53(127.0.0.1) for www.google.de failed:
connection refused.
[r...@localhost test20]#
[r...@localhost test20]# nslookup www.heise.de
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: www.heise.de
Address: 193.99.144.85
[r...@localhost test20]# nslookup www.ebay.de
;; Truncated, retrying in TCP mode.
;; Connection to 127.0.0.1#53(127.0.0.1) for www.ebay.de failed:
connection refused.
DNS resolution works fine on other systems in the network.
It is connman Version 0.57.
Does anybody have a tip for me?
Regards
Florian Mayer
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
Hello folks,
I found it out:
it is because the default max packet size for DNS over UDP on RouterOS
is set to 512 Bytes. If you set it to 4096 Bytes (in /ip dns
max-udp-packet-size) it is working. Mikrotik did not implement EDNS but
DNS over TCP, by the way. And those routers are quite common in Eastern
Europe.
Regards
Florian Mayer
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
