can't resolve host (A) but FQDN is fine
Posted
by
user1431356
on Server Fault
See other posts from Server Fault
or by user1431356
Published on 2013-07-03T02:01:47Z
Indexed on
2013/07/03
5:08 UTC
Read the original article
Hit count: 553
I am getting inconsistent name resolution locally with DNS
I have 3 2012 Standard servers and some weirdness on 1.
It is a standard install with IIS role added.
TEST01 is a dev server. 192.119.1.220 with a host header of TEST01.
DATA01 runs internal DNS on .240 and all servers and clients point here for DNS. There is a forward in DNS to 192.119.1.1 (router) with ISP external DNS #s mapped.
if I ping TEST01 from a non AD machine, it I get "Could not find Host TEST01"
If I ping TEST01 from a domain machine(another server), it resolves the IP but does not respond.
if I ping TEST01.AD.local, DNS resolves the IP, but times out.
I can access IIS by entering http://test.WWWDOMAIN.com and I can RDP to it, just not ping.
Any idea where I should start?
© Server Fault or respective owner
