How to enter multiple DNS in Load balanicng technic

RouterOS General
1

hello guys,

am doing load balancing using http://wiki.mikrotik.com/wiki/Per-Traffic_Load_Balancing …

i have DSL line and anothe dedicated line

Dsl - http (80) ,DNS, imap,pop3,msn,googltalk,https traffic

Dedicated - Rest all ( yahoo messnger, skpye, p2p)..

Each of WAN internet has 2 DNS, primary n secondary. and my dedicated Line has proxy server also 8080 port for speed browsing… now how can i enter DNS and proxy settings in mikrtik… which one primary n which one secondary..
and where can i set proxy of dedicated line
..

pls suggest..

Thanx in advance..

2

pls advice…,

3

Hah Classic.

What is done in this situations is - each DNS IP is policy routed over the Internet uplink of its provider. Same can be done for the proxy. Primary DNS entered in RouterOS should be the faster one - in this case - use the DNS of your dedicated link. It can be entered in WinBox → IP → DNS etc …

Cheers :wink:

4

thanx network pro,
i will try this solution..

btw is there any advantage with DNS cache in mikrotik..
allow-remote-requests: yes
cache-size: 8048KiB
cache-max-ttl: 1w
cache-used: 31KiB

i made allow-remote-requests: yes..

5

DNS will resolve quicker if it’s cached locally. If it’s cached locally, you potentially will not pick up changes from the authoritative server for the duration of the record TTL.

But I’d consider a local cache an advantage.

Edit: it’s extremely unlikely you’d be asking the authoritative server for the record in any case. You’d most likely simply be asking a caching resolver further upstream and would run into the same caveat, but without the ability to clean the cache.

6

Use DNS in transparent mode as well. : http://wiki.mikrotik.com/wiki/NetworkPro_on_firewalling#Proxying_everything Note:Do Not enable web proxy, it fails miserably with some websites.

All entries have TTL and it is very rare a website will change IP address and a user will hit that website on the old IP before DNS TTL expires and new DNS request is made upstream… lol And what about local DNS cache on the machine of the client? This problem is bigger there :stuck_out_tongue: