How to assign Domain Controller to VLAN Systems

[stephenw10]

Yes, your firewall rules need rationalising at some point but they are not the cause of the issue here.

You are losing, at least, DNS resolution when the connection fails. The easiest thing to do here is to grab screenshot of the connection information from the Network Manager on a client when it is working and when it fails.

That will show the IP, subnet, gateway and DNS server(s) it's configured to use.

Steve

[slkamath]

@stephenw10 @johnpoz
Thank you very much.

Rules of Marketing-VLAN

Rules of Purchase-VLAN

System Info
Marketing

System Info
Purchase

IFCONFIG
Marketing

IFCONFIG
Purchase

DIG & NSLOOKUP
Marketing - - - -> dig mail.laxmielectronics.com & dig 142.4.7.34

DIG & NSLOOKUP
Purchase - - - -> dig mail.laxmielectronics.com & dig 142.4.7.34


Before Network - Disable/Enable - NSLOOKUP

After Network - Disable/Enable - NSLOOKUP

NETSTAT
Marketing

NETSTAT
Purchase

CAT/ETC/RESOLV.CONF
Marketing

CAT/ETC/RESOLV.CONF
Purchase

TRACEROUTE
Marketing


after the traceroute 142.4.7.34 -- traceroute mail.laxmielectronics.com is working

TRACEROUTE
Purchase

Lokesh Kamath

[johnpoz]

So your pointing to local cache for dns... Doesn't actually tell you where your dns points to...

When did I ever say do a dns lookup of the IP?? Dude - how are you in this field??? I don't need to see every freaking screenshot when it works!!! Or doesn't work for gosh sake... Can you not take basic info and understand what is happening??

I you can not resolve the name - then NO shit your never going to get there..

You need to figure out WHY you can not resolve.. Is your local dns cache is failing or the actual dns?? Do a simple nslookup for the name to the actual dns server vs the local cache.. of 127.0.0.1

Pfsense is your dns right??? So

dig @ipaddressofpfsenseforthatvlan mail.laxmielectronics.com

If that fails - then WHY????? That is your problem...

[stephenw10]

Ok, so I think what you are showing there is that the machine in the Marketing VLAN is working and the machine in the Purchase VLAN was not able to resolve the mail server until you disabled/enabled the adapter, right?

Both those machines are configured to use external DNS servers. If that Connection Information screenshot was taken when it was not working it looks OK though. So you have some DNS issue.

Is there some reason you're not handing out the interface IP as DNS in DHCP?

Also both those machines are now out of date, the one in Purchase by a long way!

Steve

[slkamath]

@stephenw10 @johnpoz
Thank you very much.

I think initially pfsense IP (192.168.10.1) was not been set as DNS. Now I removed External DNS fom LAN & VLAN and kept blank. Now I am getting Primary DNS as pfSense IP.

dig 192.168.10.1 mail.laxmielectronics.com
did this from Purchase-VLAN and i am getting answer for both.

dig 192.168.40.1 mail.laxmielectronics.com
did this from Purchase-VLAN and i am getting answer for both.

I did some changes:

1. Removed External DNS from LAN.
2. Now LAN IF CONFIG - IP: 192.168.10.2 SUBNET: 24 Gateway: 192.168.10.1 Primary DNS: 192.168.10.1 (No Secondary DNS) I think now pfSense is pointing as DNS
3. Removed External DNS (ISP Provided) from all VLANS.
4. Now VLAN IFCONFIG - IP: 192.168.30.60 SUBNET: 24 Gateway: 192.168.30.1 Primary DNS: 192.168.30.1 (No Secondary DNS)
5. Firewall VLAN Rules did few changes. (Same for other VLAN too)
   

I will test this today and update you.

Once again thanks for your time.

Lokesh Kamath

[johnpoz]

@slkamath said in How to assign Domain Controller to VLAN Systems:

Removed External DNS (ISP Provided) from all VLANS.

Your clients that are members of AD... Ie you have domain controllers should be pointing to your DC that running dns for your domain.. This will be the authoritative NS for your AD.. And have all your AD records in it..

This or these NS if you have more than 1 running your AD dns will either forward or resolve any domains it is not authoritative for.. Member machines of AD should always point to the NS for your AD.. That would not be pfsense out of the box running unbound.. You could prob do with the bind package.. But when you have AD, it makes little sense to not just run DNS for on one of the DCs if not multiples of them.

Pointing client machines to more than 1 NS that can not resolve the same stuff is going to lead you to nothing but problems since you can never be sure which NS your client is going to ask for specific query.

If your clients were pointing to multiple NS and 1 of them could not resolve your smtp servers fqdn, then yeah a reset of the interface would prob force it to query the 1st vs the 2nd, etc. Or who knows how you had them setup..

If your going to point your clients to pfsense for dns and you running an AD, your going to want to make sure you setup all the domain overrides for your AD dns, or your going to want to make sure pfsense points to your AD nameserver(s)..

[slkamath]

@johnpoz
Thank you very much.

I really forgotten the AD clients. Thank you so much for reminding.

Still disable & enable is must for only VLAN Clients.

Lokesh Kamath

[johnpoz]

Dude where are they pointing for DNS?? You do understand that showing 127.0.0.1 is pointing them to their own local running copy of dnsmasq - you need to know where that points!!!

[slkamath]

@johnpoz
Thank you very much.

In LAN few Ubuntu systems are there and those system also shows 127.0.0.1 but no issue with those (if system idle for anytime next moment it is working).

Those VLAN clients DNS pointing can I manually change to pfSense ??

Lokesh Kamath

[johnpoz]

Your clients should point to your AD for dns..

My point is your clients showing that they point to loopback doesn't tell you where they point... They are pointing to their own local cache..

[slkamath]

@johnpoz
Thank you so much.

I will do the changes by monday and let you know.

Once again thanks for your time.

Lokesh Kamath