[SOLVED] Remove 127.0.0.1 from resolv.conf ??

[christian]

If i use zentyal as primary dns server dhcpclient don't have internet connection :/

This is not matter of "connection" but failure to resolve internet names    which is mandatory as you use transparent proxy.
It doesn't work mostly, I believe, because you did not set your local DNS to transparently cache, did you?

[codedmind]

I'm running 3.0 updated

i can't ping from zentyal(or any computer) none of dhclients by theirs hostaname.

Any suggestion?


dmps@zentyal:~$ ping 192.168.1.123
PING 192.168.1.123 (192.168.1.123) 56(84) bytes of data.
64 bytes from 192.168.1.123: icmp_req=1 ttl=128 time=0.414 ms
64 bytes from 192.168.1.123: icmp_req=2 ttl=128 time=0.265 ms
64 bytes from 192.168.1.123: icmp_req=3 ttl=128 time=0.296 ms
^C
--- 192.168.1.123 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.265/0.325/0.414/0.064 ms
dmps@zentyal:~$ nslookup documentacao02
Server:      127.0.0.1
Address:   127.0.0.1#53

** server can't find documentacao02: NXDOMAIN

dmps@zentyal:~$ cat /etc/resolv.conf
search cariano.local
nameserver 127.0.0.1
nameserver 192.168.1.254
nameserver 81.92.193.1
nameserver 81.92.192.2
nameserver 81.92.192.3
nameserver 8.8.8.8
nameserver 8.8.8.4
dmps@zentyal:~$

[christian]

did you check that you clients inherit from the right domain name and did you set up "search domain" field ?

well, I  notice you perform this test from Zentyal itself. Is "search domain" in Network/dns section defined ?
what if you look for FQDN instead of hostname ?

[codedmind]

Yes i have confirmed everything

from zentyal i can ping server01 (and in the ping the ping put the search domain) (but server01 is static The problem is other computers.

In dhcp i put wins 192.168.1.2 should i put 192.168.1.254 ?

The main problem in my opinio is the 127.0.0.1 because when i try the nslookup is the server who response.

dmps@zentyal:~$ nslookup zentyal
Server:      127.0.0.1
Address:   127.0.0.1#53

Name:   zentyal.cariano.local
Address: 192.168.1.254
Name:   zentyal.cariano.local
Address: 94.46.225.18
Name:   zentyal.cariano.local
Address: 192.168.0.1

dmps@zentyal:~$ nslookup server01
Server:      127.0.0.1
Address:   127.0.0.1#53

Name:   server01.cariano.local
Address: 192.168.1.2

dmps@zentyal:~$ nslookup documentacao02
Server:      127.0.0.1
Address:   127.0.0.1#53

** server can't find documentacao02: NXDOMAIN

[christian]

is documentacao02 DHCP client? If not, is this server defined as hostname in Zentyal DNS?

Regarding WINS: which one is your real WINS server ? Windows or did you also set up Samba (file sharing) in Zentyal. In any case, in order to avoid ping pong game, you should have only one master browser. If Windows server is to be kept as file server, keep it as WINS server too. Emulating Windows is never better done than by Windows servers 

[codedmind]

Yes documentacao02 is dhcp client.

And yes, windows 03 server is to keep and is ip is 192.168.1.2

[christian]

look at you DHCP client and check what is the IP config. Is domain aligned with Zentyal domain?
What does "static domain" contain in the DHCP/Dynamic domain section ?

[codedmind]

Dhcp client

receive 192.168.1.254 as gw
dns 8.8.8.8 and 8.8.8.4 and search domain is cariano.local

The same goes to resolv.conf in zentyal

dmps@zentyal:~$ cat /etc/resolv.conf
search cariano.local
nameserver 127.0.0.1
nameserver 192.168.1.254
nameserver 81.92.193.1
nameserver 81.92.192.2
nameserver 81.92.192.3
nameserver 8.8.8.8
nameserver 8.8.8.4

[christian]

In Zentyal, "nameserver 127.0.0.1" & "nameserver 192.168.1.254" in resolv.conf are strange as both point, at the end, to same DNS server isn't it?

Regarding your DHCP client, what is missing to confirm we have the right setting, if client FQDN.
Is or not your client part of "cariano.local" domain ?

Search domain and DNS domain can be different. you could f.i have DNs domain = dynamic.cariano.local but search only for cariano.local because all servers are at the root level.
In such a case and with such search domain in Zentyal, you will never find client.dynamic.cariano.local

BTW, did you try, as I asked you, to resolve FQDN, just to be sure we do not take in account in our long debugging session, potential issues due to search domain.

[codedmind]

Yes.

documentacao02 is part of domain cariano.

dmps@dmps-desktop:~$ nslookup documentacao02
Server:      127.0.0.1
Address:   127.0.0.1#53

** server can't find documentacao02: NXDOMAIN

dmps@dmps-desktop:~$ nslookup documentacao02.cariano.local
Server:      127.0.0.1
Address:   127.0.0.1#53

** server can't find documentacao02.cariano.local: NXDOMAIN

dmps@dmps-desktop:~$ dig documentacao02

; <<>> DiG 9.8.1-P1 <<>> documentacao02
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57459
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;documentacao02.         IN   A

;; AUTHORITY SECTION:
.         1762   IN   SOA   a.root-servers.net. nstld.verisign-grs.com. 2012092000 1800 900 604800 86400

;; Query time: 84 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 20 16:22:26 2012
;; MSG SIZE  rcvd: 107

dmps@dmps-desktop:~$ dig documentacao02.cariano.local

; <<>> DiG 9.8.1-P1 <<>> documentacao02.cariano.local
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18733
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;documentacao02.cariano.local.   IN   A

;; AUTHORITY SECTION:
.         1755   IN   SOA   a.root-servers.net. nstld.verisign-grs.com. 2012092000 1800 900 604800 86400

;; Query time: 56 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 20 16:22:32 2012
;; MSG SIZE  rcvd: 121

dmps@dmps-desktop:~$


About resolv.conf the 127.0.0.1 i can't remove, i can remove 192.168.1.254.. but don't change nothing :|



Uploaded with ImageShack.us

[christian]

so remove this useless "192.168.1.254"  it will avoid to request local Zentyal DNS once from localhost and once from internal NIC

As you play with "dig", why not trying "dig documentacao02.cariano.local." ?   (notice the leading dot here)

[codedmind]

removed 192.168.1.254 from resolv.conf

the dig result

; <<>> DiG 9.8.1-P1 <<>> documentacao02.cariano.local.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17528
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;documentacao02.cariano.local.   IN   A

;; AUTHORITY SECTION:
cariano.local.      86400   IN   SOA   zentyal.cariano.local. hostmaster.cariano.local. 2012092042 28800 7200 2419200 86400

;; Query time: 8 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 20 16:33:33 2012
;; MSG SIZE  rcvd: 101

[christian]

So, clearly, your "documentacao02" server is not yet registered in your Zentyal DNS server.
Can you see it in the DHCP leases (dashboard) ? if yes, then I suppose there is either misconfiguration or bug (I didn't try Zentyal 3.0 DHCP yet)

[codedmind]

yes i can see it there. so i can see the ip address and then ping it :/

[christian]

So, to summarize:
- DHCP is configured with dynamic DNS
- clients get IP and are in the right domain (cross check this twice and check again, in DNS section that your domain is shown as "dynamic")

but you can't resolve names for DHCP client.

In such case, I suggest you create a ticket.

BTW, you should also change, in DHCP, primary DNS setting: there is no reason to use 8.8.8.8 as Zentyal DNS will act as local cache and save you some bandwidth and latency.