Local and ISP DNS

DNS servers listed in clients are assumed to be peers or clones or as having the same contents, and are not ordered lists. More than one DNS server can be listed to clients on the off chance that one of your DNS servers are inaccessible. But it's not a "look for a DNS translation here, then look here, then look here" case. Select your own local DNS server(s) here as being the DNS server(s) supplied by your DHCP and by your clients (where the DNS server(s)s are locally set), and configure your local DNS server up to forward any requests for which it is not authoritative along to your ISP DNS, and ensure that your local DNS server can get its requests out through to the ISP DNS server. Done.

The firewall must not block these requests.
The firewall must not serve up a DNS address to clients via DHCP.
The firewall here likely should not accept inbound DNS requests into your LAN.
Beyond that, the firewall is "just an IP router" for this purpose.

Your DNS is asking a "lame" server for DNS; you're not getting an authoritative response to the query.

The target DNS server for the query isn't configured correctly; the local DNS server has found a target DNS server for the domain as being authoritative for the zone, but the target DNS server is not configured as being authoritative for the zone.

i configured my router for forwarding the port 53 to my local dns, but it didn't solved the problem!

That's not what I'd choose here.

Your clients are aimed at your DNS server. Your DNS server is aimed at your ISP servers. Your firewall is set to pass DNS out, but (generally) to block inbound DNS requests. Your DHCP is set to serve your DNS server address. If you've been tossing configuration changes and such here within your clients and your DNS servers, then you may well have some stale stuff in the DNS caches, too.

Now i tested at www.speedtest.net my latency (ping) it is 700ms(with Local DNS Forwarder),without its around 45ms.

The DNS server here might be misconfigured or an otherwise slow box, or there's something up with the network or the local connection or the ISP DNS. What this speedtest tool is doing here or what it might be testing here, I don't know. I tend to use the integrated tools; ping and such. I also don't how the DNS server is configured, what the box involved is, or otherwise.

what shall i do?

You're going to have to do some detective work. Without poking around inside the DNS and the LAN and related, I'm not in a good position to figure out why the connectivity here is slow.

Open Terminal and write: sudo changeip -checkhostname

Post results here.

[quote]i configured my router for forwarding the port 53 to my local dns, but it didn't solved the problem![/quote]

Of course it did not, because your server can handle dns requests for his dns domain, and when he does not know the answer, it "forwards" the request to the forwarder.

Regards

Kostas