Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - fatbob

Pages: 1 ... 5 6 [7]
91
Hi there

In relation to your first point nslookup on windows always seems to give output without the trailing dot ie
eg nslookup 91.189.94.156 gives:

Name: vostok.cannonical.com
Address: 91,189.94.156

in relation to your second point I tried with the trailing . ie nslookup xpbox.mydomain.lan. and had the same result nothing found. The request only gets sent to the forwarder if you request nslookup xpbox, if you use the FQDN then it never gets forwarded

In any case dispite your efforts I'm no closser to finding out why my forward lookups for windows domain pc's don't work (other then there is no dns entry for some reason)

92
tried dig with similar results. Also tried dig for my one xp machine that has the incorrect forward lookup. The result is definately coming from dns on the local box.

;; ANSWER SECTION:
xpbox.mydomain.lan. 900 IN   A   10.53.19.103 <--This is total boll*x it's .197

;; AUTHORITY SECTION:
mydomain.lan.   900   IN   NS   myserver.mydomain.lan.

93
Yeah no worries

EG:
windows host name: xpbox
windows IP; 10.56.19.134

nslookup 10.53.19.134
gives name = xpbox.mydomain.lan

nslookup xpbox gives not found on any windows machine
using FQDN:
nslookup xpbox.mydomain.lan gives not found on any machine

nslookup xpbox on zentyal gives one slightly odd response which is :

Non-authoritative answer:
Name:   xpbox
Address: 67.215.65.132

this resolves to hit-nxdomain.opendns.com. I use opendns as my forwarders and if you try to resolve an unknown host in a web browser for example this "trick" forwards you to there search page.

Other then that not found



94
Hi Christian

Yes it was my mistake to not reboot the XP box in between switching servers. However after further experimentation with another XP machine and a windows 7 machine I can simplify the problem a bit to the following

  • For windows machines that are not in the domain and for non windows devices both forward and revers lookups work as expected
  • For windows devices that are in the domain a reverse lookup (by ip address) will resolve to the correct host name however a forward lookup will not work. In all cases bar this one odd XP machine, no forward lookup wil work. If the machine is dropped out of the domain then it works fine.

I think that points the finger squarely at samba. But I have NO idea about what it's doing. Like you I only know isc dhcp and bind. :( Anyone else got any ideas:

Zentyal module versions
Zentyal Core: 3.0.13
Zentyal Samba: 3.0.13
Zentyal DNS: 3.0.5
Zentyal DHCP: 3.0.2

These are the latest as far as i can see


95
I now have another windows xp that doesn't get a forward lookup at all. The forward and reverse lookups for both machines function fine when not connected to the domain.

96
Hi Christian

To answer your question first the lease is 30 minutes, max lease is 2 hours and the problem still exits after the machine has been disconnected for 6 (overnight) (Ie it will happen again when the machine is powered up.

Firstly disregarding the involvement of the windows domain there are 2 questions raised by this
  • Why does the same machine with one nic / mac address appear to be assocaited with 2 ip addresses simultaneously
  • Why does the forward lookup on host name resolve to a different IP address then the one the machine has, perticualry when a revers record has been successfully created

Now coming back to the windows domain issue. The domain certainly has a dependancy on dns and I'm begining to suspect it actually has an impact on it too,

Let me explain the full details of what's happened leading up to this.

I'm switching from an old SuSE 11 server to a new Zentyal server, In fact it's the same machine I just have new set of hard drive with the zentyal build on them. I'll refer to them as if they are separate machines here for conveniece but  they would never both be connected to the same network simultaneously  ;)

Both servers are configured in a similar manner. Both have the same names, both were windows file server / domain controllers and both had dhcp that dynamically updated the dns server. Both handed out IP address in the same range (this is probably the important point). On the suse server the forward and revers records were added to the dns by the dhcp server. Both managed a windows domain of the same name

I had my old suse server running and the windows XP machine that is the source of the issue was connected to it. It had been leased an IP address by the suse server ending in 103. I dropped the XP machine off the old domain.

I powerd down the suse server and powered up the zentyal server. I then tried to connect the XP machine to the new domain. This resulted in the error "network path not found". At this point the XP machine still had the 103 address leased by the old suse server that was now powered down. The error occured because the zentyal dns server had no reverse dns entry for the XP machine and could not resolve the 103 address to the xp machines host name, since it had not leased that address out. This illustrates the dependancy on dns of the windows domain.

I executed an ipconfig /release followed by and ipconfig /renew on the XP machine and it was leased an IP address ending in 197. The reverse dns entry was created on the Zentyl server and this IP address successfully resolved to the XP machines host name. I then connected the XP machine to the domain successfully.

However having done this I made the following observersions

  • Executing Ipconfig on the XP machine revealed that it's IP address was ending 197 as expected. It has no reference to the 103 address
  • The 197 address correctly resolves to the host name of the xp machine
  • A forward lookup of the XP machines host name resolves to the 103 address. This is true on all machines on the lan.
  • A revers lookup of 103 address resloves to the XP machines host name
  • No machine on the lan actually has the 103 address
  • No machine shares the XP machines host name
  • Two leases show up simultaneously on the dasboard for the XP machines MAC. one ends 197 the other ends 103. Both leases appear simultaneously when the XP machine is powered on and connected to the lan
  • Both leases appear in /var/lib/dhcp/dhcp.leases
  • The 197 address becomes unresolvable to a host name when the lease expires and the XP machine has been shut down.
  • The XP machines host name stops resolving to the 103 address immediatly after the XP box is shut down
  • The 103 address is permanatly resolvable to the XP machine name
  • The 103 address appears in /var/lib/named db.x.x.x (where x.x.x are the other digits in the IP address range). Shutting down the name server, deleting the jnl file and removing it from this file does not fix the issue. Except in so much as 103 stops resolving to the host name. Once the  XP machine is powered on a 103 address is added back in
  • Dropping and renaming the XP machine has no effect on this problem. The same issue occures with the new host name

One final note on this. I believe I was once told that when a windows machine connects to a (conventional windows server run) windows domain that it updates the DNS records with it's host name / IP address. As supposed to the scenario I had on the suse box where the dhcp server did that. i wonder if there is some similar process in effect here as I know samba 4 has some dns support in order for it to perform in a manner expected by windows clients.

97
Do you get any error messages

98
Installation and Upgrades / [SOLVED] Samba won't update dns (still)
« on: February 24, 2013, 02:33:45 am »
NB have simplified the issue further down in the history of this post


Hi I have Zentyal Community box (Core version 3.0.13 )

It runs the dhcp service and is configured to do dynamic domain updates. It is also running as a Windows domain controller and file server.

One of the windows XP clients keeps appearing to get two leases. These show up on the dashboard and in /var/lib/dhcp/dhcp.leases

The result is that the reverse lookup (by ip) matches the IP address handed out by the DHCP server on the zentyal box. The forward look up of the name comes up with a different IP.  :o

Interestingly if the machine is dropped out of the domain the dynamic IP address seems to work with both forward and revers lookups correct. If it's added back in to the domain then the problem reoccurs

I've tried changing the name of the windows box and manually hacking the dhcp.leases file and the forward lookup file for bind in /var/lib/bind (having stopped bind and deleted the journal.

At the moment the machine appears to work ok on the domain but it is annoying.

Anybody got any ideas?

99
Just created a group for each email address and added the users into the group. This worked fine :)

100
Hi

Have Zentyl community eddition 3.

Have changed the option zarafa_always_send_delegates to yes in /etc/zentyal.conf

Have created aliases under create mail aliases in the user config

Still f*kin zarafa won't let me send as an alias. No error at all. If I change the from address it just ignores it.

Any ideas.?




101
This worked perfectly using the configuration supplied by christian

To summarise the problem. My real email is delivered to a mail provider that handles mail for my domain (mydomain.com). Each user has a pop3 account at the mail provider. I want local users to receive email from this domain on the server and be able to send from the server web mail / zarafa client.

1) Created a virtual mail domain "mydomain.com" on the server and set as the default email domain for users.
2) Created a new email address for each user that matched there public mydomain.com email address.
3) Set the smart host for the mail server to be the smtp gateway for my mail provider. This is important. It means that emails in mydomain.com come from the correct source and prevents mails being rejected as spoof email addresses by recipients.
4) Configured the external mail retrieval for each user to pull mail from there pop3 account on the mail providers server on to my own server.

This set-up means that i have the security of a mail provider and all the advantages of a locally managed mail server (no limints on mail storage, access to the archive of mail and the ability to switch mail provicders easily or even manage it my self if I want to).

Fantasic

Thanks again to Christian

102
[SOLVED]
Hi there


I have the following scenario:

My zentyal box (v3.01) is on a dynamic ip address and I don't have any intention to use it as my primary public mail server.

I have an external mail provider that recieves and sends mail for mydomain.com. Each user has a mail account on this provider

I want to replicate the setup I had on my previous suse box that works as follows:

Mail is downloaded from my mail provider to each users local mail box - this would be done using the "Mail retrieval from external accounts" option under the users configuration.

I would like the user setup so that when they reply to an email in Zarafa it is sent from there mydomain.com address.

I would like all mails to be relayed via my external mail providers smtp.

I should point out that the user names for the local user and the remote mailbox is the same. Ie a local user with a user name of "bob" would have a remote email address of "bob@mydomain.com"

It doesn't matter if a user sends a mail to another user using Zarafa and that mail is only sent internally. Ie if bob@mydomain.com emails alice@mydomain.com and the email goes to alices internal mail box but not to her external one, this is fine. However any mail bob sends externally must appear to come from bob@mydomain.com and must be relayed through the mail providers smtp. The users do not have any other email address they will send from.

I've seen lots of mails on here that seem similar but I'm not sure about it.

Cheers
fb

Pages: 1 ... 5 6 [7]