Topics

1

Installation and Upgrades / Choosing right DNS server

« on: October 27, 2012, 07:09:32 pm »

Hi,

This is my LAN setup:

• 192.168.1.1 - pfsense 2.0.1 (gateway) acting as DNS forwarder and DHCP server for LAN clients
  
• 192.168.1.2 - zentyal 3.0 (office PDC) also acting as DNS server for domain controller.

I ended up with two DNS (forwarders) servers. I still want to use 192.168.1.1 as only DNS server, but to join and use win clients with PDC, second one (192.168.1.2) has to be used.

I ended up with this solution. I setup 192.168.1.2 as DNS server on win clients. Then forward DNS requests on 192.168.1.2 to 192.168.1.1, and from 192.168.1.1 to Internet. Aldo this is working, I have problem resolving FQDN for local hosts:
This works

Code: [Select]

nslookup win1but this

Code: [Select]

nslookup win1.home.lan isn't.


I also tried another solution, to add dns record in primary (192.168.1.1) DNS server so that home.lan points to 192.168.1.2. Aldo dns resolution worked properly, win clients didn't found domain controller (join was not working).

Is there a better, nicer solution?

thanks

2

Installation and Upgrades / "Reinstall" Zentyal file server on new HW

« on: October 07, 2010, 01:12:04 pm »

Hi,
I want to move my Zentyal server to new hardware. Zentyal is configured as PDC domain controller (file server). Is this possible to transfer "PDC data&configuration" to new hw, without losing information of joined workstations (WinXPs), so that I don't have to rejoin all WinXPs?

3

Installation and Upgrades / [SOLVED] ntpd started twice

« on: September 29, 2010, 02:19:43 am »

After reboot ntp service is started twice, once as Zentyal ntp module and once as system service.
I removed system service with

Code: [Select]

update-rc.d -f ntp removeI also reinstall ntp module in Zentyal, but no success.

If manualy stop and start ntp with ebox

Code: [Select]

/etc/init.d/ebox ntp stop
/etc/init.d/ebox ntp startI get

Code: [Select]

ps aux | grep ntpd
root      8818  0.0  0.0   4416  1660 ?        Ss   02:13   0:00 /usr/sbin/ntpd -n -g
root      8825  0.0  0.0   4416   516 ?        S    02:13   0:00 /usr/sbin/ntpd -n -g
Any suggestions?

4

Installation and Upgrades / Dynamic domain (Dynamic DNS options)

« on: September 07, 2010, 11:14:18 pm »

Hi,
I wonder what is the purpose of Dynamic domain under DHCP > Dynamic DNS options?
Should Dynamic domain automatically provide host names of connected dhcp clients? Or am I wrong?
Well, I try to set-up with Dynamic domain functionality, but I didn't work ?  
This is an example of generated bind configuration /etc/bind/db.local.zzz I got:

Code: [Select]

$ORIGIN .
$TTL 259200     ; 3 days
local.zzz              IN SOA  ns.local.zzz. admin.example.com. (
                                2010090722 ; serial
                                28800      ; refresh (8 hours)
                                7200       ; retry (2 hours)
                                2419200    ; expire (4 weeks)
                                86400      ; minimum (1 day)
                                )
                        NS      ns.local.zzz.
$ORIGIN local.zzz.
$TTL 900        ; 15 minutes
dhcp-192-168-100-59     A       192.168.100.59
                        TXT     "31afeb082c3507946814d58deee2e2d839"
$TTL 259200     ; 3 days
ns                      A       127.0.0.1

As we can see DNS name dhcp-192-168-100-59 is generated name for IP 192.168.100.59.
1. Why isn't this name equal to host name provided by dhcp client?  
2. Also, nslooup dhcp-192-168-100-59 (dig, host) doesn't return IP...