How to configure DNS on switch cisco?

How do I change my DNS server on a switch?

I recently setup a Cisco 2960G-48T switch with VDSL2 for Internet and IPTV connections.

I've configured the DNS servers on the main router to allow only those IPs that are in this subnet. This also applies for clients connected on my subnet. Now, when clients go in their subnets, the clients can access my servers but they cannot access me. If you type address of client into the browser then the browser replies that there was no such IP number. The problem is only in my switch. It's not a DNS server problem as I am able to make it works via DHCP (IPv4 addresses). Also, I am using Windows 2025 and the latest version of NMSC. I'm aware that the solution is for me to switch off the dynamic IP address assigned to all clients on my subnet (ie static configuration). What do you think? Thank you. :)

If you configure the LAN subnet for clients and have that LAN IPs be restricted (for example 192.168.3.), then you should be able to add more static DHCP addresses to the subnet. This could help you.

How do I configure my DNS server?

We will use a DNS server.

I have already installed a new DNS server. I configured it and then when the network restarted everything went crazy! It seems as if the DNS server and the rest of my network is in conflict with each other. For example, when I enter a website the IP address of the page does not match what is stored on the DNS server. The problem is that when the network is restarted the DNS settings are all reset to default and I can't even change them. I don't want the server itself to be connected to the network and I don't want it to control my routers, so I think that this has something to do with DHCP. How do I configure this?

If you have configured the DNS server to be connected to the network, but would like to be able to access it from outside the network, you will need to set up a VPN to connect the internal network to the internet. That would be the case with any internal network. If you run a DHCP server for the internal network you can be running a DHCP server one machine and a DNS server on another.

The only reason that the IP address of your DNS server should not change is because you're running the configuration scripts that configure and reconfigure the IP settings on the router with your internal router. You may want to setup a static IP address for the DNS server and configure it accordingly.

If you want a dns server, you should set it up on the internal lan network. And then it should work as is.

When I tried to edit the resolv.conf file using vi, it said that I didn't have permission to do so.

Quote: Originally Posted by kreindlers. I don't want to run a DNS server on the internal network though.

How to configure DNS in Cisco AP?

DNS in Cisco RAS server has been an interesting topic of late, because a lot of questions come up about how to configure DNS parameters.

In this blog, I will explain few things about DNS configuration for Cisco RAS server and also help you configure your RAS server.

Here is a screenshot of our server interface: As we can see, when a client initiates a connection with our VPN gateway (server), our AP will look up our internal DNS server to resolve its IP address. In this way, our internal domain www.abcxyz.com will resolve to the IP address of our VPN gateway (which is 172.16.3). As far as I know, this is the default configuration that Cisco uses and it is not specific to any RAS server in particular. So if your interface/AP looks like this, then you can skip this part of the blog.

If you haven't already, make sure you know how to setup static routes with your VPN in advanced settings. As far as the DNS is concerned, the process is pretty much the same.

Step 1. Create Zone A zone can only contain one primary name server (ns1.yourdomain.com or your internal primary nameserver), though it can have multiple secondary or additional name servers (ns2.com or additional name servers). If we go to step 3, you would see this screen:

Step 2. Configure Forwarders We usually set it to Forward and forward all. This is the reason why we configure the forwarders and forwarders except. I have never configured my server with anything other than the forward and forward all mode (unless we are changing a zone, etc), as the forwarders are optional in this scenario and also I do not want to give them any real control over the DNS traffic as they do not really have a purpose in this regard.

If we go to Step 3, we should be asked to select the host, that we want to resolve as a DNS forwarder. If we select the current server and click OK, we should be asked to specify the target records (TXT), such as NS, A, PTR, etc. These TXT entries would be added to the zone.