Disabne DNS registration on interface

[dev246]

Hi.

I have freenas 9.2.1.5-RELEASE, witch 2 interfaces.
First interface is for management and AD integrations
Second is for data transfer (is isolated network).
After enable AD integration freenas began to register two IP addresses to DNS. So in DNS i have 2 records for this same name witch ip from 2 different separate network.
This creates a lot of problems and prevents the use of DNS name in UNCpath
How I can disable DNS registration for specific network interface, or completely off DNS registration ?

 

[dlavigne]

Did you ever find a solution for this?

 

[dev246]

Unfortunately not. My last hope was to this forum

 

[cyberjock]

I could be wrong but I don't think you can do what you are wanting to do through FreeNAS.

I'm not sure how your DNS server is setup, but there is probably a way to prevent the entry that you don't want from being used. It may take some creative thinking or it may be an obscure feature, but there is almost certainly a way to do what you want. ;)

 

[dev246]

The simplest method would be to completely disable DNS registration (unfortunately I can not find such an option) for FreeNAS and create a static entry for one IP address. The second option is to use an entirely different name than the name of the host as an A record that points at a single IP address. Both methods do not check if the main IP address is assigned by DHCP.

 

[mcw]

This issue was driving me crazy until I realized I was looking at it the wrong way. You can solve it by just adding dns entries.

Say your Freenas is joined to the domain as Freenas.example.com. It has a management nic (10.0.0.1) and a private storage network nic (192.168.0.1). As discussed, Freenas will register both addresses in DNS as Freenas.example.com.

Now, say you go to the DNS server and create two new static A records: Freenas-m.exaple.com, set to 10.0.0.1 and Freenas-s.example.com set to 192.168.0.1. Freenas will never attempt to modify either of these records, and both will work perfectly fine. Simply mount your shares as \\freenas-s\share and manage it from http://Freenas-m.example.com/. Problem solved.

 

[cyberjock]

Few comments:

If by 'management NIC' you mean the IPMI, then something is very wrong because the IPMI IP is unusable to the OS in terms of services like CIFS, NFS, etc.

There is some control over how Samba registers itself in DNS. Here's some background info...

Samba, as part of the service being started, registers itself in DNS. There are several options:

1. Don't use CIFS/Samba. Probably not a good option for most people, but it is an option.
2. (untested, but would like someone to test if they could). Set the CIFS auxiliary parameter to "allow dns updates = disabled". This should tell Samba not to try to update DNS.
3. (untested, but would like someone to test if they could). Set the CIFS auxiliary parameter to "dns update command = /usr/bin/true". This should tell Samba to run a command that won't actually update DNS, but will return as if it had properly updated DNS.

If someone could tell me if #2 and #3 actually work I would be very appreciative. ;)

Thanks.

 

[mcw]

I don't know about OP, but I was not referring to IPMI.

When I said "management NIC", I meant the interface/IP address used to manage Freenas via ssh and webgui. In my setup, I have one nic used for CIFS to windows workstations, as well as ssh and webgui access. My second nic is dedicated to vmware ESXi NFS mounts in a separate dedicated vlan.

I'd be happy to test the CIFS behavior for you - where do I set the parameters you mentioned? Some conf file in /etc/? Is it necessary to restart the CIFS daemon after the changes are made? If so, what is the command?

 

[cyberjock]

It's under the CIFS settings in the WebGUI. You should never, ever have to manually edit files on FreeNAS' base OS.

You will have to restart the CIFS service... and again you do that from the WebGUI.