Re: DNS and name resolution issues
- From: "Ash Dunn" <ash@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 11 Mar 2006 18:42:33 -0000
I forgot to add that I can ping if I use the FQDN of the host I am trying to
get to, but I shouldn't have to do this, should I?
"Ash Dunn" <ash@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:dut03g$bmp$1$8300dec7@xxxxxxxxxxxxxxxxxxx
Hi all,
I've been working late nights the last few days and my brain is a bit
fried. I have a problem with a new install and was wondering if anyone
could help.
I have several subnets, the newest has a Windows 2003 SP1 server which is
a DC also running DHCP, WINS and DNS. On the local subnet (10.4.x.x) I
can ping hosts by name if they are in the WINS database, and also by IP
address. If the host only appears in the DNS database I can't ping it nor
can I resolve the name to an IP address using NSLOOKUP. But, I can
resolve the IP address to a name using NSLOOKUP. It's almost as if the
clients on that subnet aren't able to interrogate the DNS server
correctly.
To further confuse issues I can sit on a different (10.2.x.x) and use
NSLOOKUP and point it to the DNS server on 10.4.x.x and I get the results
with no issues.
I have checked the clients on the problem subnet and they have the correct
DNS suffix, needless to say the DNS server has no issues using NSLOOKUP as
it is querying itself.
Any ideas?
.
- References:
- DNS and name resolution issues
- From: Ash Dunn
- DNS and name resolution issues
- Prev by Date: Re: Dynamic DNS w/DHCP
- Next by Date: Re: Hidden record
- Previous by thread: DNS and name resolution issues
- Next by thread: Re: DNS and name resolution issues
- Index(es):
Relevant Pages
|