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.
76
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 11:42:58 pm »
Oh by the way thanks for all the effort !! : ) very much appreciated!
77
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 11:38:43 pm »
ok so I took your advice on board - don't get excited same old behaviour so far:
so on zentyal - removed the DNS forwarders, disabled the transparent dns cache, and removed the 10.53.19.1 secondary dns server from the dhcp config
Rebooted the server
Rebooted newboy and once rebooted did a ipconfig /release followed by ipconfig /renew
P.S using newboy as it doesn't have any "complicated" behaviour it just gets a reverse lookup but no forward lookup unlike the other thing with it's odd 103 address. Lets try and sort out the lack of forward lookup first
. That problem is consistent across all boxes at least.
same story again. 10.53.19.100 resolves to newboy but newboy doesn't resolve to anything when using nslookup on windows and on the zentyal box
And still running dig on the zentyal box gives no results for newboy / 10.53.19.100 when running dig oilmovements.lan AXFR
so on zentyal - removed the DNS forwarders, disabled the transparent dns cache, and removed the 10.53.19.1 secondary dns server from the dhcp config
Rebooted the server
Rebooted newboy and once rebooted did a ipconfig /release followed by ipconfig /renew
P.S using newboy as it doesn't have any "complicated" behaviour it just gets a reverse lookup but no forward lookup unlike the other thing with it's odd 103 address. Lets try and sort out the lack of forward lookup first
. That problem is consistent across all boxes at least.same story again. 10.53.19.100 resolves to newboy but newboy doesn't resolve to anything when using nslookup on windows and on the zentyal box
And still running dig on the zentyal box gives no results for newboy / 10.53.19.100 when running dig oilmovements.lan AXFR
78
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 11:15:37 pm »
Ok ii'll disable the transparent dns cache, removed the forwarders + the router as a secondary dns and reboot.
The reson I had that set up was because I was using the windows boxes to download stuff (some automated scripted stuff) that I wanted them to carry on with whilst I messed about with the server. The basic router (10.53.19.1) can answer dns querys for the internet but has no specific dns functionality in regards to the lan.
The reson I had that set up was because I was using the windows boxes to download stuff (some automated scripted stuff) that I wanted them to carry on with whilst I messed about with the server. The basic router (10.53.19.1) can answer dns querys for the internet but has no specific dns functionality in regards to the lan.
79
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 11:11:11 pm »
Ah sorry I grabbed the closet machine that was representative of the issue. The windows network config on mumsoldgit (103 which is actually 197) and the output of the config aquired from dhcp looks like the attached file.
Im still not clear what you need from me sorry
Are you looking for the output of the dialogue between the dhcp server and the windows box. I don't really know how to get that ? any ideas?
Im still not clear what you need from me sorry
Are you looking for the output of the dialogue between the dhcp server and the windows box. I don't really know how to get that ? any ideas?80
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 10:58:08 pm »
Finally ipconfig /all from the windows xp box (
81
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 10:57:16 pm »
dns config including check box indicating a dyanamic dns domain
82
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 10:56:34 pm »
dhcp config 2 --> dyamic dns
83
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 10:56:10 pm »
dhcp config 1 - basic dhcp settings
84
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 10:55:35 pm »
windows lan config
85
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 10:41:03 pm »
Will get you config from windoze
No there's one lan 10.53.19.20
Default route is 10.53.19.1
ignore the 192.168.100.1 address it's the modem
Its like this
[ vmhost (zentyal server) ] [router ] [modem ]
[ 10.53.19.20 ] ------------> [10.53.19.1]------>[192.168.100.1] ----------> Global interweb -----> zentyal form
No there's one lan 10.53.19.20
Default route is 10.53.19.1
ignore the 192.168.100.1 address it's the modem
Its like this
[ vmhost (zentyal server) ] [router ] [modem ]
[ 10.53.19.20 ] ------------> [10.53.19.1]------>[192.168.100.1] ----------> Global interweb -----> zentyal form
86
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 10:18:06 pm »
In aswer to the question from your previous post about where I ran dig, all the investigation is being run on the zentyal box itself. dig was run on there as was my lasted nslookup command
The server identified by nslookup was:
Server: 127.0.0.1
Address: 127.0.0.1#53
There are only 3 machines and the server on my test lan nothing else. There all windows boxes and none of them has any sort of dns server on them - unless they've been hacked by some mysterious dns mugger
The server identified by nslookup was:
Server: 127.0.0.1
Address: 127.0.0.1#53
There are only 3 machines and the server on my test lan nothing else. There all windows boxes and none of them has any sort of dns server on them - unless they've been hacked by some mysterious dns mugger
87
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 10:06:22 pm »
Modem is odd it has a 192.168.100.1 address that is only accessible to the lan side - it's an adsl thing sits the other side of the firewall - accessable via the default route.
Yeah it's just getting even more odd
dig on 10.53.19.100 returns nothing
but nslookup returns: 100.19.53.10.in-addr.arpa name = newboy.oilmovements.lan.
and nslookup newboy.oilmovements.lan. returns nothing (with or without the trailing .)
Yeah it's just getting even more odd
dig on 10.53.19.100 returns nothing
but nslookup returns: 100.19.53.10.in-addr.arpa name = newboy.oilmovements.lan.
and nslookup newboy.oilmovements.lan. returns nothing (with or without the trailing .)
88
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 09:47:56 pm » Old home machines I'm using for testing hehe. My folks and I seem to collect emYeah have tried ipconfig /release /renew cycle - no joy
89
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 09:32:24 pm »
And yet more - it would seem samba is trying to update the zone but being rejected:
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: starting transaction on zone oilmovements.lan
24/02/2013 20:30:14 vmhost named[15927] client 10.53.19.100#62149: update 'oilmovements.lan/IN' denied
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: cancelling transaction on zone oilmovements.lan
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: starting transaction on zone oilmovements.lan
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: disallowing update of signer=newboy\$\@OILMOVEMENTS.LAN name=newboy.oilmovements.lan type=A error=insufficient access rights
24/02/2013 20:30:14 vmhost named[15927] client 10.53.19.100#49186: updating zone 'oilmovements.lan/NONE': update failed: rejected by secure update (REFUSED)
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: cancelling transaction on zone oilmovements.lan
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: starting transaction on zone oilmovements.lan
24/02/2013 20:30:14 vmhost named[15927] client 10.53.19.100#62149: update 'oilmovements.lan/IN' denied
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: cancelling transaction on zone oilmovements.lan
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: starting transaction on zone oilmovements.lan
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: disallowing update of signer=newboy\$\@OILMOVEMENTS.LAN name=newboy.oilmovements.lan type=A error=insufficient access rights
24/02/2013 20:30:14 vmhost named[15927] client 10.53.19.100#49186: updating zone 'oilmovements.lan/NONE': update failed: rejected by secure update (REFUSED)
24/02/2013 20:30:14 vmhost named[15927] samba_dlz: cancelling transaction on zone oilmovements.lan
90
Installation and Upgrades / Re: Incorrect or no forward dns for Windows clients on domain with dyanmic IP
« on: February 24, 2013, 09:28:27 pm »
I've attached the output of your command to this post.
Interstingly I saw this in the log ---
24/02/2013 20:20:17 myserver named[15927] client 10.53.19.197#53332: updating zone 'mydomain.lan/NONE': update failed: rejected by secure update (REFUSED)
Now I wonder if this is the windows client trying to update the zone.
Interstingly I saw this in the log ---
24/02/2013 20:20:17 myserver named[15927] client 10.53.19.197#53332: updating zone 'mydomain.lan/NONE': update failed: rejected by secure update (REFUSED)
Now I wonder if this is the windows client trying to update the zone.