seawolf Posted February 21, 2014 Posted February 21, 2014 So, your clients are getting a DHCP address properly, but not the DNS settings (as you seemed to indicate manually configuring 8.8.8.8 in your client DNS settings works)?
ccadit Posted February 21, 2014 Author Posted February 21, 2014 yes thats correct, if I give the clients manually the address of our proxy server they can get to the internet too.
seawolf Posted February 21, 2014 Posted February 21, 2014 Just looking at your original post. Have you tagged the ports on the core switch to the end point switch for the VLAN used for your switches (if you have one). We use a NET VLAN (2) that all of our switches as well as the firewall reside on. Also, have you untagged the ports going to the end point switch on the default VLAN (1)?
seawolf Posted February 21, 2014 Posted February 21, 2014 Also, if you don't have a NET VLAN that you have untagged the Meraki AP onto, then I would think it would also need to be untagged on the default VLAN.
ccadit Posted February 21, 2014 Author Posted February 21, 2014 The port that the Edge switch is plugged in to to the core is tagged for the wireless VLAN and untagged for the default VLAN.
ccadit Posted February 21, 2014 Author Posted February 21, 2014 Also, if you don't have a NET VLAN that you have untagged the Meraki AP onto, then I would think it would also need to be untagged on the default VLAN. The Meraki AP is tagged for the wireless VLAN and untagged for Default VLAN
seawolf Posted February 21, 2014 Posted February 21, 2014 What happens if you change the name server in your DHCP scope from 8.8.8.8 to one of your internal DNS servers?
ccadit Posted February 21, 2014 Author Posted February 21, 2014 same thing it never shows up in ipconfig /all and doesn't allow resolution. I want to say a big thanks so far for all your help.
seawolf Posted February 21, 2014 Posted February 21, 2014 So, the client isn't getting the DNS settings at all then. What about the default gateway, is the client receiving that from the DHCP server?
ccadit Posted February 21, 2014 Author Posted February 21, 2014 yes its getting everything else just not DNS, if I put it on the default VLAN everything is fine, somehow this VLAN is stopping DHCP propgating the DNS information to the clients. I can ping everything even accross subnets, can go to my servers on 172.16 via IP but just DNS isn't playing ball.
m25man Posted February 21, 2014 Posted February 21, 2014 (edited) What routing information does the DNS server have? route print Sound like the DNS/DHCP servers don't have a route back to the wireless VLAN all your replies are heading out the default gateway to nowhere? This would point to a RIP configuration issue. If you clients on both subnets are getting the correct default gateway (normally your core if that's doing the routing) make sure you have RIP configured correctly on the gateway device. It should tell the originators which gateway to send the packets back through. Edited February 21, 2014 by m25man
ccadit Posted February 21, 2014 Author Posted February 21, 2014 What routing information does the DNS server have? route print Sound like the DNS/DHCP servers don't have a route back to the wireless VLAN all your replies are heading out the default gateway to nowhere? What would I need to add?
seawolf Posted February 21, 2014 Posted February 21, 2014 yes its getting everything else just not DNS, if I put it on the default VLAN everything is fine, somehow this VLAN is stopping DHCP propgating the DNS information to the clients. I can ping everything even accross subnets, can go to my servers on 172.16 via IP but just DNS isn't playing ball. I think there is something up with the DHCP settings for this VLAN. Have you tried deleting the DHCP scope and recreating it? I use a dhcp3 server on Ubuntu for my DHCP (2008r2 AD and DNS though), and don't use the Windows DHCP, so the config a aren't what I'm used to on the DHCP server 1
ccadit Posted February 21, 2014 Author Posted February 21, 2014 I've tried doing that few time without any success.
ccadit Posted February 21, 2014 Author Posted February 21, 2014 All sorted now, a big thanks to FN-GM who pointed me in the direction of removing IP info from edge switch and seawolf for making my think that of trying scope on another DHCP server. All working now and its been an education.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now