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

[Ricky Nance]

Good information to know :), thanks for the update on this!

Ricky

On Fri, Sep 7, 2012 at 10:14 AM, Rowland Penny <repenny at f2s.com> wrote:

> On 07/09/12 15:42, Rowland Penny 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 yet again, answering my own question 'Why doesn't 127.0.0.1 work in
> /etc/resolv.conf'
>
> It doesn't work because the nameserver built into samba4 doesn't appear to
> listen on 127.0.0.1 !!!
>
> netstat -lnptu (produces amongst a list of others)
>
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State
>       PID/Program name
> tcp        0          0        192.168.0.5:53                     0.0.0.0:*
>         LISTEN      23660/samba
> udp       0          0        192.168.0.5:53                     0.0.0.0:*
>                          23660/samba
> tcp6      0          0        fe80::e2cb:4eff:fe06:53 :::*
>         LISTEN      23660/samba
> udp6     0          0        fe80::e2cb:4eff:fe06:53 :::*
>                          23660/samba
>
> No mention at all of 127.0.0.1:53
>
>
> Rowland
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>


--