Router can ping by IP/domain, LAN (NAT) Client Can only ping by IP

[T_K]

I am having difficulty determining where my, apparent, DNS issue is occurring.  The 4331 is able to ping 8.8.8.8, and is able to ping www.google.com, but my LAN Client can only ping 8.8.8.8, LAN Client attempts to ping www.google.com indicate that the host cannot be found (Windows 10 Client with static DNS server 8.8.8.8 assigned, connected directly to 4331's GE 0/0/1 interface, Client performs as expected when connected directly to ISP GW and assigned the 4331's static IP address).  The 4331's configuration is, with some differences due to interface numbering and OS versions, the same as the 2851's that I am replacing (ACLs, IP Address, SM, GW of last resort, etc.)  My hope is that someone here will notice something that I have missed/am missing, or have some guidance on how to investigate this more efficiently than I have been able (over the past few days).  I have attached a sanitized copy of the 4331's configuration to this post.  Thank you for any assistance that you are able provide.

[MHM Cisco World]

dns-server 10.245.161.15 10.245.165.5 <<- change this under dhcp pool to be 8.8.8.8 if you can 

[T_K]

@MHM Cisco World Thank you for your reply.  I have removed the static dns entry from the Windows client, made the recommended change to the 4331's dhcp pool's dns-server, released and renewed the client ip, verified the dhcp dns assignment reflected on the client, flushed the client's cache, and attempted several pings again.  Unfortunately, the client is still only able to ping 8.8.8.8 and is unable to ping by name. 

[MHM Cisco World]

do 
nslookup google.com
check if the client resolve the IP-Name 
share result here 

[T_K]

nslookup returned DNS request timed out

[MHM Cisco World]

then do 
show ifconfig of client you use 

[T_K]

Windows IP Configuration

Host Name . . . . . . . . . . . . : <Removed>
Primary Dns Suffix . . . . . . . : <RemovedA>
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : <RemovedA>

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : <RemovedA>
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : B0-4F-13-C7-01-84
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::cf1b:b8b2:ab15:9141%15(Preferred)
IPv4 Address. . . . . . . . . . . : 10.245.161.26(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, March 9, 2023 10:39:58 AM
Lease Expires . . . . . . . . . . : Friday, March 10, 2023 10:41:31 AM
Default Gateway . . . . . . . . . : 10.245.161.254
DHCP Server . . . . . . . . . . . : 10.245.161.254
DHCPv6 IAID . . . . . . . . . . . : 128995091
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-CA-7D-06-B0-4F-13-C7-01-84
DNS Servers . . . . . . . . . . . : 8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled

[balaji.bandi]

that looks ok

can you ping 8.8.8.8 from Pc ? (post the output)

try below example in the windows command line post all the messages here ?

type in the command line nslookup

>server  151.164.1.8

>google.com  

[MHM Cisco World]

only reason this network is that there is FW that block DNS request from some IP?
are there any FW
if there then do try following 

1-ip domain lookup 
2-

dns-server 10.245.161.15 10.245.165.5 <<- keep router IP as DNS server for all client 

3-

ip name-server 151.164.1.8 

ip name-server  8.8.8.8

[MHM Cisco World]

dns-server 10.245.161.15 10.245.165.5 <<- keep router IP as DNS server for all client 

[T_K]

There is not a firewall between the 4331 and the ISP's gateway device.  Client's behind the 2851, on same IP block, are able to utilize, and receive, dns resolution from 8.8.8.8 and removing the 4331, and assigning the Client the 4331's WAN IP, allows the Client to receive DNS resolution from 8.8.8.8.

[MHM Cisco World]

even if there is no FW, try the three steps I mention above and I think your issue will solve. 

[T_K]

My apologies, I thought you meant to try the steps if there was a firewall.  For my clarification:
Step 1:  verify "ip domain lookup" is configured
Step 2:  change DHCP pool's dns-server to be LAN interface of router (10.245.161.254)
Step 3.  verify ip name servers are 151.164.1.8 and 8.8.8.8

Am I understanding correctly?

[MHM Cisco World]

Yes but config the ip name server not in same line 
add then in different line 
i.e.
ip name server 151.164.1.8
ip name server 8.8.8.8
this way, because I see all DNS request send to 151.164.1.8 and never failover to 8.8.8.8, that why the timeout and DNS resolve issue. 
try this way and update us 

[T_K]

Thank you for the verification.  I have verified ip domain lookup is configured on the 4331.  For the DHCP pool, I have configured the dns-server to be 10.245.161.254.  Unfortuntatley, I couldn't get the name-servers to split to seperate lines, issuing the commands seperately shows them combined as one line when running config is viewed; given this, and my understanding of your reasoning, I removed 151.164.1.8 and left only 8.8.8.8.  After releasing and renewing client's dhcp, verifying that dns shows 10.245.161.254, and flushing the ip cache I am still unable to ping by name and nslookups still time out on the client; pinging by ip address still works for the client.

Excerpts of current config:
ip name-server 8.8.8.8

ip dhcp pool <removed>
network 10.245.161.0 255.255.255.0
default-router 10.245.161.254
domain-name <RemovedA>
option 150 ip 10.245.161.6
dns-server 10.245.161.254

[balaji.bandi]

if you want your Router to be act as DNS Server

add below command  :

ip dns server

then if you do Windows server ipconfig /all ( you should see DNS Server 10.245.161.254)

then try nslookup google.com and let us know how it does.