first the data:
Model name: TS-453A
Firmware version: 4.2.2 (2016/09/01)
Operation System (OS): Windows 7/10
OS Language: English/Dutch
Number of HDDs: 3
HDD model: HGST HDN724040ALE640 (SATA)
HDD capacity: 4TB
RAID configuration: 1 and none
Services enabled, e.g. Linux Station, Domain Controller (Control Panel > Domain Controller)
I am trying to use the QNAP as domain controller and have set things up according to the manual. I have created the domain, created users and was able to join a (windows 7) pc to the domain after changing its DNS setting to point to the QNAP.
On the QNAP in the network settings the primary DNS entry points to the router/firewall.
The problem is now that the QNAP does not seem to be forwarding DNS requests that it cannot resolve itself (outside of AD). That means the pc can either join the domain, or have a working internet connection, but not both.
The smb.conf contains "dns forwarder = 127.0.0.1", which seems odd as I would expect it to say "dns forwarder = firewall.ip.address"?
Manually editting /etc/config/smb.conf (or /etc/config/smb.conf_addc) and manually restarting samba with /etc/init.d/smb.sh restart seems to somehow involve overwriting smb.conf meaning the changed setting has reverted back to 127.0.0.1. So at this point I don't know if setting it to the firewall ip would fix the problem, nor why it is wrong in the first place if this is the problem.
I am relatively familiar with linux and samba, but not with AD, nor with the peculiarities of QNAP-linux. Any pointers would be highly appreciated!
Questions about using Windows AD service.
2 posts • Page 1 of 1
- First post
- Posts: 1
- Joined: Tue Sep 20, 2016 10:11 pm
- New here
- Posts: 5
- Joined: Mon Jul 23, 2018 11:26 pm
Same problem here...
Who is online
Users browsing this forum: No registered users and 1 guest