[PATCH] Switch to internal dns server as default for provision

[Rowland Penny]

On 07/09/12 18:50, Rowland Penny wrote:
> On 07/09/12 18:22, steve wrote:
>> On Fri, 07 Sep 2012 15:42:58 +0100
>> Rowland Penny<repenny at f2s.com>  wrote:
>>
>>> On 07/09/12 12:33, Rowland Penny wrote:
>>>> On 07/09/12 12:15, steve wrote:
>>>>> On 06/09/12 20:22, Ricky Nance wrote:
>>>>>> Steve,
>>>>>>
>>>>>> This was straight from Kai on irc: 'Simply power down bind, add
>>>>>> "server services = +dns" to your smb.conf'.
>>>>> Hi Ricky
>>>>>
>>>>> Tried that. Nothing. No DNS. No internet. Is there something I
>>>>> must add to the samba command line? Is there a conversion script
>>>>> to take my /etc/bind.conf and translate it to Internal?
>>>>>
>>>>> I think we need some doco along the lines of 'switching from bind
>>>>> dns to samba4 internal dns', perhaps.
>>>>> Cheers,
>>>>> Steve
>>>>>
>>>>>
>>>>>
>>>> Hi, I will second that.
>>>>
>>>> The command 'host -t SRV _ldap._tcp.home.lan.' Returns
>>>> ;; connection timed out; no servers could be reached
>>>>
>>>> I do not seem to have a nameserver, this is on a newly compiled git
>>>> pull -- Samba 4.0.0beta9-GIT-d0159f6
>>>>
>>>> provisioned with:
>>>>
>>>> provision --realm=home.lan --domain=HOME --adminpass=<MYPASS>
>>>> --dns-backend=SAMBA_INTERNAL --use-rfc2307 --server-role=dc
>>>>
>>>> What are we missing?
>>>>
>>>> Rowland
>>>>
>>> Hi again, I think that I have found the problem, it doesn't like
>>> 127.0.0.1 in /etc/resolv.conf.
>>>
>>> if /etc/resolv.conf contains
>>> nameserver 127.0.0.1
>>> search home.lan
>>>
>>> host -t SRV _ldap._tcp.home.lan.
>>> ;; connection timed out; no servers could be reached
>>>
>>> if you change /etc/resolv.conf to contain the servers ipaddress
>>> nameserver 192.168.0.5
>>> search home.lan
>>>
>>> host -t SRV _ldap._tcp.home.lan.
>>> _ldap._tcp.home.lan has SRV record 0 100 389 hda.home.lan.
>>>
>>> host -t SRV _kerberos._udp.home.lan.
>>> _kerberos._udp.home.lan has SRV record 0 100 88 hda.home.lan.
>>>
>>> host -t A hda.home.lan.
>>> hda.home.lan has address 192.168.0.5
>>>
>>> ping -c1 www.google.com
>>> PING www.google.com (74.125.79.99) 56(84) bytes of data.
>>> 64 bytes from ey-in-f99.1e100.net (74.125.79.99): icmp_req=1 ttl=51
>>> time=41.0 ms
>>>
>>> --- www.google.com ping statistics ---
>>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>>> rtt min/avg/max/mdev = 41.036/41.036/41.036/0.000 ms
>>>
>>> Why doesn't 127.0.0.1 work in /etc/resolv.conf it does with bind9
>>>
>>> Rowland
>>
>> Hi Rowland
>> Thanks so much for your help on this. I now have the Internal DNS
>> working, but purely internally. As soon as it hits the forwarder, it
>> crashes. I've had this before. Will start another thread
>> Cheers,
>> Steve
>>
>>
> Hi Steve,
> Strange, mine works fully (on Ubuntu 12.04 server) and I seem to have 
> got the ISC dhcp server to work with it, but time will tell.
> We just need Kai to make it listen on 127.0.0.1
>
> Rowland
>
Hi all,
Well time has told and no, ddns from the dhcp server is not working. I 
have a setup which works ok with bind 9.9.1 but the same setup does not 
work with the internal nameserver. I turned on debug in the script and 
got this 'could not find enclosing zone', so I added the zone info to 
the script and got this
'dns_tkey_negotiategss: TKEY is unacceptable'.
No matter what I do, I cannot get past this, anybody got any ideas?

Rowland


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.