enabling internal DNS

[Daniele Dario]

Hi Kai,

On Mon, 2012-09-17 at 13:52 +0200, Daniele Dario wrote:
> Hi Kai,
> 
> On Mon, 2012-09-17 at 13:27 +0200, Kai Blin wrote:
> > On 2012-09-17 13:18, Daniele Dario wrote:
> > 
> > Hi Daniele,
> > 
> > >> I updated the secondary DC to rc1 and added the dns forwarder = IP1 IP2
> > >> line and all seems to be OK. Tomorrow I'll update also the primary one
> > >> and do the same job.
> > 
> > Currently you can only set one forwarder. Our DNS library doesn't
> > support more than that at the moment.
> > 
> > Cheers,
> > Kai
> > 
> 
> at the moment I have added in smb.conf
> 	dns forwarder = 82.193.37.1
> 
> Now, when I start samba no errors are fired for the dns forwarder
> parameter.
> 
> resolv.conf contains
> domain saitelitalia.local
> search saitelitalia.local
> nameserver 192.168.12.2
> nameserver 192.168.12.5
> 
> where 192.168.12.2 is kdc02 (the DC I've updated to rc1+s3fs+internal
> dns) while 192.168.12.5 is kdc01 (the primary DC with beta3+bind9+dlz).
> 
> On kdc02 looking for hosts on my domain I have:
> [root at kdc02:~]# nslookup filesrv01
> Server:		192.168.12.2
> Address:	192.168.12.2#53
> 
> Name:	filesrv01.saitelitalia.local
> Address: 192.168.12.6
> 
> which seems to be correct: the DC/DNS is looking inside itself to find
> the answer but looking for some host outside my domain i have:
> 
> [root at kdc02:~]# nslookup www.google.it
> Server:		192.168.12.5
> Address:	192.168.12.5#53
> 
> Non-authoritative answer:
> Name:	www.google.it
> Address: 173.194.35.151
> Name:	www.google.it
> Address: 173.194.35.159
> Name:	www.google.it
> Address: 173.194.35.152
> 
> which tells me kdc02 "forwards" the request to kdc01.
> 
> When I perform the request on kdc02, in the log.samba appears
> 
> ../source4/dns_server/dns_query.c:604(dns_server_process_query_send)
>   Not authoritative for 'www.google.it', forwarding
> 
> but it does not forward to the forwarder but to the other DC.
> 
> What am I doing wrong?
> 
> Thanks in advance,
> Daniele.
> 

SORRY!!
I was using the wrong IP address for the forwarder. Using the right one
the answer is as expected.

AGAIN SORRY!!

Thanks,
Daniele.