Re: Non-existent A record being returned...
- From: "Ace Fekay [MCT]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 31 Jul 2009 19:15:54 -0400
"Ray Van Dolson" <rvandolson@xxxxxxxx> wrote in message news:9820cc39-6bad-4337-8880-8740d99af60a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
When querying hostname.tld.com from our Windows 2003 DNS servers, the
record is returned as follows (for multiple queries:
; Query 1
hostname.tld.com. 557 IN A 10.49.104.226
; Query 2
hostname.tld.com. 556 IN A 10.49.104.226
The DNS server(s) being queried are SOA's for tld.com. Other records
queried from these servers are not returned with a decrementing TTL.
So it seems like the host above is part of the cache on the server,
but looking at the cache for tld.com the entry isn't there. We don't
have an A record defined at all for hostname.tld.com.
These DNS servers are set up to forward queries to two other DNS
servers, but a packet dump and query log examination show that queries
for hostname.tld.com are not being forwarded...
Maybe flushing the cache would help, but haven't tried it yet.
I did dump the entire tld.com zone with dnscmd. Searchin through for
the IP comes up with one A record pointing to that IP address, but
it's something completely different....
Could this record somehow be hiding in the cache but not visible to
tools? Maybe it would be pruned by initiating scavenging?
Anyone have any thoughts?
I assume you are using nslookup? Nslookup has it's own resolver service, and doesn't rely or use Windows resolver service, or the local cache (ipconfig /flushdns doesn't work with nslookup), but rather directly queries DNS, where I'm assuming you're referring to clearing the DNS server cache?
Does it exist in your reverse zone?
I can't see, nor heard of 'hidden' records existing, unless possibly using WINS integration? But then again, that would return the name 'wins' in the query's FQDN result.
Check the zone's properties, Nameserver tab, and see if it's in there.
There isn't any rogue apps/spyjunk on the machine, possibly?
Try the query with all of your other DNS servers, too, using nslookup interactive mode, instead of batch (as your examples indicated). Simply change the server it's using with the 'server' command, such as the following. I would be curious if they all return the IP, including your forwarders that you've stated you are forwarding to (assuming internally) and not just this one DNS you're presently querying in nslookup.
C:\>nslookup
Default Server: ace-dc-01.mydomain.com
Address: 192.168.30.55
server 192.168.30.someothersever<enter>
hostname.tld.com
btw - "TLD" stands for Top Level Domain, which is the root of the FQDN, such as .com, .local, .net, etc. So in the example, 'hostname.domain.com,' the 'com' is the TLD, and the name 'domain' can be looked at (depending on who you talk to) as the '1st level domain name' or the 2nd level domain name.' When the name 'domain' is looked at as the second level name, those folks will call the TLD (com, net, etc) a first level, then domain would be second level, etc. I've seen various websites in the past refer to it either one way or the other, but the root name is definitely called the TLD.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
Please reply back to the newsgroup or forum to benefit from collaboration among responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
.
- Follow-Ups:
- Re: Non-existent A record being returned...
- From: Ray Van Dolson
- Re: Non-existent A record being returned...
- References:
- Non-existent A record being returned...
- From: Ray Van Dolson
- Non-existent A record being returned...
- Prev by Date: Non-existent A record being returned...
- Next by Date: Re: Non-existent A record being returned...
- Previous by thread: Non-existent A record being returned...
- Next by thread: Re: Non-existent A record being returned...
- Index(es):
Relevant Pages
|
Loading