I like to open a little talk about networking and netshserver.
Actually I have HP gen10 with 2 lan
One LAN is connected as green for internal network
There is a bridge created automagically by the sistem for AD
-The other LAN is unused at the moment
I have all WINDOWS/LINUX client under the same network 192.168.X.Y/24
I have added the NETHSERVER as 192.168.X.11 (wuebui and shared folder) 192.168.X.10 (AD)
I have a the main ROUTER as 192.168.X.1 it has DHCP (from 192.168.X.100 to 192.168.X.250)- VPN(a lot) site to site and it connect to main internet router under ip space 192.168.Z.W/24
I know that using AD we have to set nethserver bridge interface as DNS resolver. This is a problem because WINDOWS become crazy and can’t resolve any internet address.
So at the moment a light and fast solution is to set the 8.8.8.8 as primary dns and nethserver as secondary. I have to inspect better with dns inpection tool.
But…
what is the idea behind nethserver netwokink.
DNS if configured is under green real interface 192.168.X.11 and bridge 192.168.X.10 has only the resolution for AD server name.
If I set the the default DNS as gereen interface and add inside neth a resolution rule for AD to the bridge ip and other to be forwareded to my default router, is this possible? is it a nice idea or open to a lot of problems?
Nethserver uses dnsmasq which is a DNS and DHCP server so I recommend to use both services on Nethserver. This way DNS knows about given DHCP addresses. A resolution rule (you’ll need it on the main internet router) would work but does not solve the DNS/DHCP problem.
Nethserver should use your main internet router as gateway and a working DNS server (Google is default).
The clients should use your main internet router as gateway and Nethserver as DNS. Mixing DNS servers that know about your (internal/AD domain) with ones that don’t know is a bad idea.
Ok now I have the connection to the interface but how to rebuild the AD without loosing config of AD
I have no outgoing packet ping don’t ping but machine is finally pingable.
I’m sure it is a problem between HW or configuration because i Use it on a switch (new buyed for the occasion) where I have machine and Another win PC.
I know that it is a VM but where is the relation between
Are you sure there is no hardware failure on your NethServer interface? I had a problem with a networkinterface on a HP gen7 microserver. The server has 1 interface of itself on the motherboard. Since it is used as gateway for the LAN, it needed a 2nd interface. I had a dual Gb adapter lying around and I added that on the HP microserver.
After a year or so, the Red interface became inresponsive. All settings seemed ok but no traffic was going through the interface.
I configured the onboard interface as Red interface instead of one of the dual interface nic ports, and voila… all was fixed. It turned out to be a hardware problem.
Thans @robb tomorrow I plan to install new firmare on nic card so network can be inspected better also via BIOS.
So to ensure that this is not an hw proble I’ll order a dual gigabit card for test some suggestion on chipset I know about some problem in Intel.
If i understand correctly, you have a router for internet access, which also give DHCP for you LAN.
In this case, the DNS forwarder/resolver for Internet access is the router. All your LAN clients have the LAN IP of the router as DNS.
You have added NethServer (ONE NIC) to prvide AD services for your LAN.
In this case, the DNS resolver for your LAN is the NS but not also forwarder!
In your case, for everythink to work well, you have some options:
1 - move your DHCP services from router to NS
set your NS NIC as follow:
IP: 192.168.X.11 (DHCP: 192.168.X.100 - 192.168.X.250)
NM: 255.255.255.0
GW: 192.168.X.1
DNS: 192.168.X.1
In this case, the NS will act as DNS forwarder/resolver for Internet access and as DNS resolver for your LAN.
Te external DNS (8.8.8.8) is set ONLY on router!
2 - keep DHCP on router
on router, if the router has this option, add NS as new host.
set your NS NIC as follow:
IP: 192.168.X.11
NM: 255.255.255.0
GW: 192.168.X.1
DNS: 192.168.X.1
In this case, the router will act as DNS forwarder/resolver for Internet access and as DNS resolver for your LAN.
Te external DNS (8.8.8.8) is set ONLY on router!
Thanks it’s never late and all Information are useful.
Yes I have added the AD and to use it I need NS to be a DNS.
At the beginning i had configured the server under networking to have IP .41 (real) .40(AD) GW IProuter DNS a sequence of 8.8.8.8,8.8.4.4,RouterIP.
The host use NS as as primary DNS and router as gateway but dns query are not forwarded.