Active Directory does not allow dns queries from computers on lan network

[m.traeumner (Michael Träumner)]

So it resolves internal addresses, but not external.
Only for trying, please set DNS at a client manually to 8.8.8.8. and try if you reach external addresses like nethserver.org after it?

I think external addresses are your problem, or not?

[Hitmoky_Hitter]

Not quite, I just noticed that I am using Google Chrome to access the webinterface, which uses 8.8.8.8 and 8.8.4.4 before using the local network it’s DNS. So I then tried it with Firefox, and I can’t access {host}.{domain}.{tld}:980

Pardon me for the confusion, I did not notice any sooner.

[m.traeumner (Michael Träumner)]

Is your domain only internal or external too? If it is an external domain have a look here:

Resolving domain name on intranet

NethServer Version: NethServer release 7.3.1611 (Final) Module: DNS Hi Everyone, I installed a fresh NS7 final on a laptop to test out. The internal network is behind a pfsense. NAT Port 80 and 443 is pointing to the nethserver internal IP. Installed the following components: Account provider: Samba Active Directory File server FTP server Instant messaging MariaDB (MySQL) server Nextcloud SOGo groupware Virtual machines manager Web server If i go to “Applications” on the GUI and …

And for others who read this and try to help, here a link to your other thread:

Samba certificates

System version: NethServer release 7.4.1708 (Final) Kernel release: 3.10.0-693.21.1.el7.x86_64 Module: Active Directory Hey support! ^^ I’d like to connect an external NextCloud server to the NethServer it’s Active Directory LDAP listener but I got the message that a more secure connection should used. I can seem to connect with Apache Directory Studio to both ldap (389) and ldaps (636). But when I try to connect NextCloud with ldap, it doesn’t seem to make the connection and produces the f…

[Hitmoky_Hitter]

I kind of went another way and re-installed Nethserver, checking the clients ability to request dns queries allong every part of the initial configuration, active directory implementation etc. Apparently there was never a problem… It was a custom firewall on the device itself that did not autostart when Windows did. If I knew sooner that this was the problem, I would not have posted, sorry for this.

Anyway, thanks for the help and again sorry for taking up precious time.

[m.traeumner (Michael Träumner)]

Hi,
nice to hear that you have solved your problem.

@Hitmoky_Hitter

If I knew sooner that this was the problem, I would not have posted, sorry for this.

It is good that you have posted it, because if others have the same problem it can help them.