ā07-18-2023 07:26 AM
When I ping the DC-01 it resolves the public IP address, not the internal DNS
I have added the two DNS
10.100.20.10
8.8.8.8
when I remove the 8.8.8.8 its reaching the dc-01 which looks good but when I add 8.8.8.8 and ping its showing the public ip address
how can we force host to reach dc-01 ip address not public address
ā07-18-2023 08:31 AM
Hi @ankitohc
Is it PacketTracer?
ā07-18-2023 08:51 AM
Its on production enviroment
ā07-19-2023 05:37 AM - edited ā07-19-2023 05:41 AM
these are two different things
1) DNS resolving -> lookup DNS name to obtain IP-address
2) configuring DNS servers on the client -> to specify what DNS servers to use
google does not know anything about your internal addresses
so if you use 8.8.8.8 (google-dns) as DNS server to query, only public ip-addresses are returned
if you use 10.100.20.10 (internal-dns) your internal address is returned
-> this is expected behavior
1) depending on the OS you may specify a primary and secundary,
where the primary is used first and the secundary if the primary is unavailable
2) if query is alternating between DNS, then you get alternating ip-address returned
3) if the query is sent to both DNS you get random response depending on which response is received first
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide