I am sure a little scripting on mikrotik behalf could write to bind to
update as needed.
On 11/19/2015 09:16 AM, That One Guy /sarcasm wrote:
is there a way in bind with mikrotik to dynamically update the records
like in active directory dns, though thats a function of the dhcp
integration i believe?
On Thu, Nov 19, 2015 at 9:11 AM, David <[email protected]
<mailto:[email protected]>> wrote:
Yep,
just throw in an old pc running debian/bind and go for it.
create a view for the domain and (here come the BOOM!)
LOL
On 11/19/2015 09:06 AM, Dennis Burgess wrote:
MT can’t do PTRs just static entries, but a full blown DNS server
can handle private IP space and if you and/or your customers are
using it, it should be able to give you a DNS name for
troubleshooting etc.
Dennis Burgess, CTO, Link Technologies, Inc.
[email protected] <mailto:[email protected]> – 314-735-0270
x103 <tel:314-735-0270%20x103> – www.linktechs.net
<http://www.linktechs.net/>
*From:*Af [mailto:[email protected]] *On Behalf Of *That One
Guy /sarcasm
*Sent:* Wednesday, November 18, 2015 4:59 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* [AFMUG] mikrotik ptr record for internal space
we currently have out routing taking place on 172.31.x.x space.
Is there a way to make the mikrotiks just respond with a name, if
not is there an easy way to have the mikrotik update its ptr to a
local bind server if we move to using our own DNS servers? I
assume if there is no way to get the ttl expired to respond with
the name there would be no way to have this viewable to the
outside world, but for internal troubleshooting it would be
beneficial
--
If you only see yourself as part of the team but you don't see
your team as part of yourself you have already failed as part of
the team.
--
If you only see yourself as part of the team but you don't see your
team as part of yourself you have already failed as part of the team.
