New VLAN pointing to DNS, how to add zone

[abillybob]

Hi All

 

Hoping one of you guys can help me. I have a VLAN that I've created with a new range, the DHCP is done on the Core Switch but I need to point it at our internal DNS server. How do I create the relevant zones in DNS to make it work as it currently can't resolve and computer/server names internally on the network!

 

Any help would be appreciated

 

Thanks

[Liam]

In dns go to add new zone and put in the network details if necessary but don’t really need to m. Bear in mind they won’t communicate without routing / properly configured gateways at device level this would need to be configured by your dhcp options. The gateway would need to be the vlan interface ip. I’d also consider using some kind of ip helper and using your windows dhcp server assuming you have one Edited January 25, 2018 by Liam

[Davit2005]

With DHCP done on the core switch have you set the DNS options?

 

What core switch are you using.

 

To be honest you should not need to do anything special on the DNS server as long as the clients are set to use. The only you may need is reverse lookup zones for PTRs etc.

[abillybob]

With DHCP done on the core switch have you set the DNS options?

 

What core switch are you using.

 

To be honest you should not need to do anything special on the DNS server as long as the clients are set to use. The only you may need is reverse lookup zones for PTRs etc.

Yes I have set that so the dhcp is pointing that VLAN to 193.168.33.2 (Our DNS server) the DNS server is on a separate VLAN by the way but is able to ping clients on the new VLAN.

 

I have tried setting up a new forward zone but the wizard doesn't ask for any IP information it just asks for a Zone Name. I have added the reverse lookup zone but it doesn't populate with anything?

 

The issue is if you try to ping an internal computer and your on the new VLAN but the computer you're trying to ping is on the Old VLAN when using DNS names it says unknown host... I'm so confused as I thought if you pointed a new VLAN to the DNS server as long as that new VLAN can talk with the DNS server there wouldn't be a problem and all you need to do is setup reverse lookup, is this right?

 

Sorry I know it's a bit confusing it's hard to explain on here :|

 

Here's the model of the core switch,

Edited January 25, 2018 by abillybob

[Liam]

Does it ping by ip? Can you link tbe dns server by both fqdn/netbios and ip?

[Liam]

Firewall?

[abillybob]

Does it ping by ip? Can you link tbe dns server by both fqdn/netbios and ip?

I can ping by IP from the new VLAN to the DNS perfectly fine and the FQDN seems to work but not the netbios is just says unknown host?

[Davit2005]

Yes I have set that so the dhcp is pointing that VLAN to 193.168.33.2 (Our DNS server) the DNS server is on a separate VLAN by the way but is able to ping clients on the new VLAN.

 

I have tried setting up a new forward zone but the wizard doesn't ask for any IP information it just asks for a Zone Name. I have added the reverse lookup zone but it doesn't populate with anything?

 

The issue is if you try to ping an internal computer and your on the new VLAN but the computer you're trying to ping is on the Old VLAN when using DNS names it says unknown host... I'm so confused as I thought if you pointed a new VLAN to the DNS server as long as that new VLAN can talk with the DNS server there wouldn't be a problem and all you need to do is setup reverse lookup, is this right?

 

Sorry I know it's a bit confusing it's hard to explain on here :|

 

Here's the model of the core switch, [ATTACH=CONFIG]47311[/ATTACH]

 

You should not need to add a new forward zone if adding a new vlan, all the different IP address should be in the one zone as long as it is the same domain.

 

On a client with the issue try referencing the server by its FQDN. Or try an NSLOOKUP.

 

On the client if you do a ipconfig all does it show the correct IP address. As others have said could it be an firewall or access control list?

 

To be honest I've never used a switch to do DHCP server before, only as a DHCP relay.

[roc1479]

Sounds like you may need to enable routing on the vlan interfaces