Renaming Infoblox devices in Name Server Groups ?

[#1]

Renaming Infoblox devices in Name Server Groups ?

We have a Grid setup with several Trinzic devices.
The devices were setup with not-so-user-friendly names, following company standards.

So, for example, the devices have names like:

blox1-code.dc1.city1.country.mycompany.com        A        123.123.100.11
blox2-code.dc2.city2.country.mycompany.com        A        123.123.200.11
etc ..

We would like to set up the authoritative DNS records for the main domain to show a more friendly name.
For example:

Infoblox > dig mycompany.com ns

;; AUTHORITY SECTION:
mycompany.com.    1800    IN      NS      ns1.mycompany.com.
mycompany.com.    1800    IN      NS      ns2.mycompany.com.
;; ADDITIONAL SECTION:
ns1.mycompany.com.    1800    IN      A       123.123.100.11
ns2.mycompany.com.    1800    IN      A       123.123.200.11

Instead of using the names associated to the devices. Because it just doesn't look good.

Even though we create the DNS A records for ns1 and ns2, we have found no way to add these IPs to a Name Server Group.
So, we haven't found a way to be able to implement what we would like to do.

Any ideas or suggestions would be greatly appreciated!

This also falls in the same category as using different server names for our customers.

If we have, for example, a customer with domain name:   customer.com
That wants to use our Trinzics as their DNS authoritative servers,
But wants to use their own DNS names..  for example:

Infoblox > dig mycompany.com ns

;; AUTHORITY SECTION:
customer.com.    1800    IN      NS      ns1.customer.com.
customer.com.    1800    IN      NS      ns2.customer.com.
;; ADDITIONAL SECTION:
ns1.customer.com.    1800    IN      A       123.123.100.11
ns2.customer.com.    1800    IN      A       123.123.200.11

.. using the same IP addresses.. the ones assigned to LAN1 and 2 of the trinzics..
How do we go about doing this?

Thanks!

-Javier

[#2]

In your nameserver groups, the friendly name should be set to External Secondary.  Set the non-friendly servers Grid Primary/Secondary with Stealth turned on so they don't show up as NS records.

This should accomplish what you need.  The only item that may be an issue is your ips- it may not like the same ip as a grid server and an external server.

[#3]

Hello Daniel,

Thanks for your reply.

I had tried the configuration that you suggested, and, indeed, it gave me an error that I couldn't have duplicate IPs listed in the group.

I even tried different combinations using MGMT or LAN IPs.  But, of course, the grid knows all the information, and doesn't allow me to include an external secondary's LAN IP of a server whose MGMT IP is already in the list. :-(

So, I'm still in the same boat.

Thanks though.

-Javier