That rule would never be used.  That matching traffic wouldn't be seen by
the Core.

Customers would go to eth4 of the BMU to eth2 of the BMU.


Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373

On Fri, Jun 19, 2015 at 10:13 AM, Micah Miller <[email protected]> wrote:

> Why use the ip's from the old DNS servers at all?  Couldn't you simply
> redirect all DNS traffic from your customers to your new DNS?
>
> Somthing like this possibly:
> /ip firewall nat chain=dst-nat to-addresses=<new-dns-server>
> to-ports=53 protocol=udp src-address=<customer-subnet> dst-port=53
>
> On Fri, Jun 19, 2015 at 8:55 AM, Josh Luthman
> <[email protected]> wrote:
> > Here's my network from a high level:
> >
> > Customers -> Powercode BMU (router) -> Mikrotik Core -> Upstreams
> >                      Powercode BMU (router) <- DNS servers
> >
> > Is it possible to redirect the traffic in this case?  I'm kind of
> thinking
> > on paper here, but what if I took the IPs of the old DNS servers, put
> them
> > on the MT core and then did a dstnat to the new IPs?
> >
> > The reasoning behind this is the public IPs of the old servers are TWC
> > addresses and I am moving to my own ARIN (portable) IPs.
> >
> > Josh Luthman
> > Office: 937-552-2340
> > Direct: 937-552-2343
> > 1100 Wayne St
> > Suite 1337
> > Troy, OH 45373
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> http://mail.butchevans.com/pipermail/mikrotik/attachments/20150619/34446796/attachment.html
> >
> > _______________________________________________
> > Mikrotik mailing list
> > [email protected]
> > http://mail.butchevans.com/mailman/listinfo/mikrotik
> >
> > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> RouterOS
>
>
>
> --
> Micah Miller
> Network/Server Administrator
> Network Business Systems, Inc.
> Phone: 309-944-8823
> _______________________________________________
> Mikrotik mailing list
> [email protected]
> http://mail.butchevans.com/mailman/listinfo/mikrotik
>
> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> RouterOS
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.butchevans.com/pipermail/mikrotik/attachments/20150619/7643bec5/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

Reply via email to