Jared Mauch writes:
>The ability of routers to use DNS for service names is getting to be more of a
>soft-requirement => hard requirement these days. I may want to configure a
>DNS name for my BMP/KFAFKA magic and have it fail over if we renumber the
>machine (for example).
Yup, this one's on my list of features I haven't added yet. The
plan was to have the value contain both the DNS and the address so
we (a) always have an address, and (b) can re-resolve at some
specific future time. It's less of an issue for NTP, but imagine
having DNS fail for your syslog server and not getting logs. The
re-resolve would be an explicit action, done at the user's direction
(or via event policy, etc).
Anyway, it would look something like:
[edit system ntp]
drew@charlie# show
server 0.pool.ntp.org%216.230.228.242;
server 1.pool.ntp.org%45.79.109.111;
server 2.pool.ntp.org%172.98.193.44;
server 3.pool.ntp.org%69.195.159.158;
where the junos system components would see only the address, but
the UI would hold both and "request system configuration resolve"
would perform the magic. There'd be an "opt in" knob to turn on
this new behavior, so API clients (and humans) wouldn't freak at
these hybrid values.
Thanks,
Phil
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
