[Samba] DNS information, again...
Ryan Ashley
ryana at reachtechfp.com
Sat Nov 1 17:25:57 MDT 2014
Certainly. Here you go!
ddns-update-style none;
option domain-name "kigm.local";
option domain-name-servers 192.168.0.2, 192.168.0.1;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
subnet 192.168.0.0 netmask 255.255.252.0 {
option routers 192.168.0.254;
option domain-search "kigm.local";
range 192.168.2.101 192.168.2.200;
}
Note that on DC01 (the current dead DC due to a bad RAID controller) the
file is the same, except for the name-server addresses being reversed
and DC01 handing out IP addresses from 192.168.2.1 through
192.168.2.100. This way they both function when both servers are up AND
I have failover if one dies, as is my case right now.
On 11/1/2014 8:52 AM, Rowland Penny wrote:
> On 01/11/14 12:18, Ryan Ashley wrote:
>> Alright, I believe something is very wrong here, but I have no idea
>> what it is. DNS is not updating to my Linux servers running Samba,
>> DNS, and DHCP. However, on a virtual domain using Server 2008 R2 and
>> WIndows 7 clients, DNS gets updated. The following was done from a
>> domain controller on the domain in question. I also ran
>> "samba_dnsupdate --verbose" and it claims that no updates are required.
>>
>> root at dc02:~# host balcony.kigm.local
>> balcony.kigm.local has address 192.168.2.32
>> root at dc02:~# nbtscan 192.168.2.0/24
>> Doing NBT name scan for addresses from 192.168.2.0/24
>>
>> IP address NetBIOS Name Server User MAC address
>> ------------------------------------------------------------------------------
>>
>> 192.168.2.106 BALCONY <server> <unknown>
>>
>> As you can see, this is a conflict. The correct address ends in 106
>> today, but it may be 1 tomorrow thanks to DHCP. So is there something
>> extra I need to do to get WIndows 7 clients to update DNS entries?
>> This is causing a few problems with mapped drives and such.
> Hi, can you post your dhcpd.conf file.
>
> Rowland
>
More information about the samba
mailing list