search for: drucker2

...Expire 3H ) ; NX (TTL Negativ Cache) ; Nameservers IN NS srv.wie. ; name servers - A records srv.wie. IN A 192.168.1.50 ; Hostname records router.wie. IN A 192.168.1.1 drucker.wie. IN A 192.168.1.25 drucker2.wie. IN A 192.168.1.26 wiesrv.wie. IN A 192.168.1.51 smb.wie. IN A 192.168.1.55 zones/db.1.168.192: $TTL 2D @ IN SOA srv.wie. ns.wie. ( 3 ; Serial 8H...

...3H ) ; NX (TTL Negativ Cache) > ; Nameservers > IN NS srv.wie. > ; name servers - A records > srv.wie. IN A 192.168.1.50 > ; Hostname records > router.wie. IN A 192.168.1.1 > drucker.wie. IN A 192.168.1.25 > drucker2.wie. IN A 192.168.1.26 > wiesrv.wie. IN A 192.168.1.51 > smb.wie. IN A 192.168.1.55 > > zones/db.1.168.192: > $TTL 2D > @ IN SOA srv.wie. ns.wie. ( > 3 ; Serial >...

> > This sounds like a dns problem, are your windows machines using the DC > as their nameserver ? > yes they are using the server as dns. DNS is done through bind9 and implemented in samba via bind9_dlz. All looks fine: $ host -t A smb.wie smb.wie has address 192.168.1.50 $ host -t SRV _kerberos._udp.smb.wie _kerberos._udp.smb.wie has SRV record 0 100 88 srv.smb.wie. $ host -t SRV