[Samba] Delete second IP address from aipServerAddrs and aipListenAddrs DC

[lingpanda101]

On 3/10/2018 5:16 AM, Paul Littlefield via samba wrote:
> On 09/03/18 13:30, lingpanda101 via samba wrote:
>> On 3/9/2018 5:30 AM, Paul Littlefield via samba wrote:
>>> For some reason, the provision picked up 2 network IP addresses in 
>>> my VM.
>>>
>>> Snipped output below...
>>>
>>>
>>> root at dc1.example.com ~ $ (screen) samba-tool dns serverinfo dc1
>>>   dwVersion                   : 0xece0205
>>>   fBootMethod                 : DNS_BOOT_METHOD_DIRECTORY
>>>   fAdminConfigured            : FALSE
>>>   fAllowUpdate                : TRUE
>>>   fDsAvailable                : TRUE
>>>   pszServerName               : DC1.example.com
>>>   pszDsContainer              : 
>>> CN=MicrosoftDNS,DC=DomainDnsZones,DC=example,DC=com
>>>   aipServerAddrs              : ['192.168.122.8', '192.168.122.208']
>>>   aipListenAddrs              : ['192.168.122.8', '192.168.122.208']
>>>
>>>
>>> root at dc1.example.com ~ $ (screen) samba-tool dns query dc1 
>>> example.com @ ALL
>>>   Name=, Records=4, Children=0
>>>     SOA: serial=149, refresh=900, retry=600, expire=86400, 
>>> minttl=3600, ns=dc1.example.com., email=hostmaster.example.com. 
>>> (flags=600000f0, serial=149, ttl=3600)
>>>     NS: dc1.example.com. (flags=600000f0, serial=1, ttl=900)
>>>     A: 192.168.122.208 (flags=600000f0, serial=1, ttl=900)
>>>     A: 192.168.122.8 (flags=600000f0, serial=4, ttl=900)
>>>
>>>
>>> Is there a way to delete the second IP address from the DC LDAP 
>>> database?
>>>
>>> Thanks.
>>>
>>> Paully
>>>
>>>
>>>
>> You should be able to manually set with the following command in your 
>> smb.conf file.
>>
>> interfaces =
>>
>> Read the smb.conf man page for details but I would use the IP and not 
>> interface name.
>>
>>
>
> Alas no, that's not removing it from the LDAP Database.
>
>
You can try binding the interface in your smb.conf with the following.

'bind interfaces only = yes'

Are you using bind or the internal DNS? I don't know how to edit this 
inside LDAP unfortunately.

-- 
--
James