Missing A records in cache

Hello,

I am having a strange problem with resolving names to one specific internet
domain. On occasion my DNS servers will lose the ability to resolve the
t-systems.at domain. Clearing the cache re-enables the servers ability to
resolve the t-systems.at domain. When I click on advanced view and look at
the cache I see that the t-systems folder contains the following:

(same as parent folder) - Name Server (NS) - ns1.t-systems.at.
ns1 - Host(A) - 212.31.86.100

On the occasions when I cannot resolve the domain I have noticed that the
cache record for t-systems.at is missing the A record. It only contains the
NS record for ns1.t-systems.at.

My best guess is that without this A record, the ns1.t-systems.at name
server is unresolveable and clearing the cache forces my dns server to issue
a query out to get the t-systems.at information. Thus name lookups fail
until the cache is cleared and the t-systems folder is repopulated.

Can anyone shed some light on why the cache might be missing this
information. It prevents us from sending email to this domain.

Thanks in advance,
Chris

Read inline please.

In news:BF2473E1-A90E-42BF-83D8-,
Chris Ramsay <> typed:
> Hello,
>
> I am having a strange problem with resolving names to one specific
> internet domain. On occasion my DNS servers will lose the ability to
> resolve the t-systems.at domain. Clearing the cache re-enables the
> servers ability to resolve the t-systems.at domain. When I click on
> advanced view and look at the cache I see that the t-systems folder
> contains the following:
>
> (same as parent folder) - Name Server (NS) - ns1.t-systems.at.
> ns1 - Host(A) -
> 212.31.86.100
>
> On the occasions when I cannot resolve the domain I have noticed that
> the cache record for t-systems.at is missing the A record. It only
> contains the NS record for ns1.t-systems.at.
>
> My best guess is that without this A record, the ns1.t-systems.at name
> server is unresolveable and clearing the cache forces my dns server
> to issue a query out to get the t-systems.at information. Thus name
> lookups fail until the cache is cleared and the t-systems folder is
> repopulated.
>
> Can anyone shed some light on why the cache might be missing this
> information. It prevents us from sending email to this domain.

The NS record has a Ttl of 86400 seconds (1 day), while the A record has a
Ttl of only 300 seconds. Even after the Ttl expires on the A record, DNS
will use recursion to resolve the A record, because it knows the name to
look for and start the 300 second countdown again.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Hello,

Thanks for the response.

I would think that is what is happening but it is not. Once the A record
disappears from cache, the name becomes unresolveable until the cache is
cleared and repopulated with both the A and NS records. As I mentioned this
only happens with this one site. Any idea why my DNS server would not look
up the A record again?

Thanks,
Chris

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Read inline please.
>
> In news:BF2473E1-A90E-42BF-83D8-,
> Chris Ramsay <> typed:
> > Hello,
> >
> > I am having a strange problem with resolving names to one specific
> > internet domain. On occasion my DNS servers will lose the ability to
> > resolve the t-systems.at domain. Clearing the cache re-enables the
> > servers ability to resolve the t-systems.at domain. When I click on
> > advanced view and look at the cache I see that the t-systems folder
> > contains the following:
> >
> > (same as parent folder) - Name Server (NS) - ns1.t-systems.at.
> > ns1 - Host(A) -
> > 212.31.86.100
> >
> > On the occasions when I cannot resolve the domain I have noticed that
> > the cache record for t-systems.at is missing the A record. It only
> > contains the NS record for ns1.t-systems.at.
> >
> > My best guess is that without this A record, the ns1.t-systems.at name
> > server is unresolveable and clearing the cache forces my dns server
> > to issue a query out to get the t-systems.at information. Thus name
> > lookups fail until the cache is cleared and the t-systems folder is
> > repopulated.
> >
> > Can anyone shed some light on why the cache might be missing this
> > information. It prevents us from sending email to this domain.
>
> The NS record has a Ttl of 86400 seconds (1 day), while the A record has a
> Ttl of only 300 seconds. Even after the Ttl expires on the A record, DNS
> will use recursion to resolve the A record, because it knows the name to
> look for and start the 300 second countdown again.
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>

Read inline please.

In news:63ED39CA-A8F7-49CF-B6CB-,
Chris Ramsay <> typed:
> Hello,
>
> Thanks for the response.
>
> I would think that is what is happening but it is not. Once the A
> record disappears from cache, the name becomes unresolveable until
> the cache is cleared and repopulated with both the A and NS records.
> As I mentioned this only happens with this one site. Any idea why my
> DNS server would not look up the A record again?

Does that DNS server have a forwarder?
If it does, check that the forwarder supports recursion.
Check that the DNS server is able to use recursion. Use the Monitoring tab
to test that it can do simple and recursive lookups.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Hello,

Yes recursion is enabled and the DNS server works just fine using standard
root hints. The problem seems to be that if the server finds a folder with
the domain name in its cache file, it will not use recursion to find any
missing or incomplete information inside of that folder.

The proof of this is that I can delete just the t-systems folder from cache
and the dns server begins resolving the name normally again. A while later
though, the A records disappear from the t-systems folder leaving just the ns
records and dns queries for t-systems fail until I remove the folder again.

Thanks,
Chris

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Read inline please.
>
> In news:63ED39CA-A8F7-49CF-B6CB-,
> Chris Ramsay <> typed:
> > Hello,
> >
> > Thanks for the response.
> >
> > I would think that is what is happening but it is not. Once the A
> > record disappears from cache, the name becomes unresolveable until
> > the cache is cleared and repopulated with both the A and NS records.
> > As I mentioned this only happens with this one site. Any idea why my
> > DNS server would not look up the A record again?
>
> Does that DNS server have a forwarder?
> If it does, check that the forwarder supports recursion.
> Check that the DNS server is able to use recursion. Use the Monitoring tab
> to test that it can do simple and recursive lookups.
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>

Read inline please.

In news:E2505B9F-DD2E-4A1B-AAD1-,
Chris Ramsay <> typed:
> Hello,
>
> Yes recursion is enabled and the DNS server works just fine using
> standard root hints. The problem seems to be that if the server
> finds a folder with the domain name in its cache file, it will not
> use recursion to find any missing or incomplete information inside of
> that folder.
>
> The proof of this is that I can delete just the t-systems folder from
> cache and the dns server begins resolving the name normally again. A
> while later though, the A records disappear from the t-systems folder
> leaving just the ns records and dns queries for t-systems fail until
> I remove the folder again.

The TTl on the A record is only 5 minutes. There sould be no reason why it
cannot resolve the A record even with the NS record in cache, because it
would get the A record from the at TLD servers.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

For several hours I'm getting this same problem but not for one domain but
for all remote domains! It's happening for 4 different servers in different
locations, all Windows 2003 R2. My DNS system is unusable. Local domain
resolving works normal.

Please help!
Przemo

"Kevin D. Goodknecht Sr. [MVP]" <> wrote in message
news:...
> Read inline please.
>
> In news:E2505B9F-DD2E-4A1B-AAD1-,
> Chris Ramsay <> typed:
>> Hello,
>>
>> Yes recursion is enabled and the DNS server works just fine using
>> standard root hints. The problem seems to be that if the server
>> finds a folder with the domain name in its cache file, it will not
>> use recursion to find any missing or incomplete information inside of
>> that folder.
>>
>> The proof of this is that I can delete just the t-systems folder from
>> cache and the dns server begins resolving the name normally again. A
>> while later though, the A records disappear from the t-systems folder
>> leaving just the ns records and dns queries for t-systems fail until
>> I remove the folder again.
>
> The TTl on the A record is only 5 minutes. There sould be no reason why it
> cannot resolve the A record even with the NS record in cache, because it
> would get the A record from the at TLD servers.
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>

Read inline please.

In news:OTF%,
Przemo Karlikowski <> typed:
> For several hours I'm getting this same problem but not for one
> domain but for all remote domains! It's happening for 4 different
> servers in different locations, all Windows 2003 R2. My DNS system is
> unusable. Local domain resolving works normal.

Do you have forwarding enabled to your ISP (or router if it supports) on the
Forwarders tab?



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Read inline please.

In news:E2505B9F-DD2E-4A1B-AAD1-,
Chris Ramsay <> typed:
> Hello,
>
> Yes recursion is enabled and the DNS server works just fine using
> standard root hints. The problem seems to be that if the server
> finds a folder with the domain name in its cache file, it will not
> use recursion to find any missing or incomplete information inside of
> that folder.

Are you still having a problem?
I notice that there has been a change in the TTL for both the NS record and
A record, both now have TTL of 3 hours.

When you run nslookup ns1.t-systems.at. against your DNS does it fail?

>
> The proof of this is that I can delete just the t-systems folder from
> cache and the dns server begins resolving the name normally again. A
> while later though, the A records disappear from the t-systems folder
> leaving just the ns records and dns queries for t-systems fail until
> I remove the folder again.

Are you using a Forwarder?
If so, what is the forwarder's IP address?
Does the forwarder answer correctly when you run
nslookup -qtype=ns t-systems.at <ForwarderIP>

IF it doesn't run it with the debug switch
nslookup -d2 -qtype=ns t-systems.at <ForwarderIP>

Create two batch files, one with the NameServer lookup against the at
servers and one with the a record lookup for ns1.t-systems.at.
Use this command and attach the txt file output to your next post.



nslookup -qtype=ns t-systems.at. 193.171.255.2
nslookup -qtype=ns t-systems.at. 192.92.125.2
nslookup -qtype=ns t-systems.at. 81.91.161.98
nslookup -qtype=ns t-systems.at. 87.233.175.130
nslookup -qtype=ns t-systems.at. 192.76.243.2
nslookup -qtype=ns t-systems.at. 195.66.241.82
nslookup -qtype=ns t-systems.at. 204.152.184.202
nslookup -qtype=ns t-systems.at. 206.65.170.101
nslookup -qtype=ns t-systems.at. 210.81.13.181

nsbatchfilename.bat >t-systemsNS.txt

nslookup -qtype=a ns1.t-systems.at. 193.171.255.2
nslookup -qtype=a ns1.t-systems.at. 192.92.125.2
nslookup -qtype=a ns1.t-systems.at. 81.91.161.98
nslookup -qtype=a ns1.t-systems.at. 87.233.175.130
nslookup -qtype=a ns1.t-systems.at. 192.76.243.2
nslookup -qtype=a ns1.t-systems.at. 195.66.241.82
nslookup -qtype=a ns1.t-systems.at. 204.152.184.202
nslookup -qtype=a ns1.t-systems.at. 206.65.170.101
nslookup -qtype=a ns1.t-systems.at. 210.81.13.181

Alookupbatch.bat >t-systemsA.txt


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Hello,

thanks for your time on this. I pasted the results below. One interesting
thing is that I went ahead and as a test, added an explicit forwarder for
t-systems.at and pointed it to the IP addresses for ns1.t-systems.at and
ns2.t-systems.at. When I did that, the A records were added back into the
cache as expected and everything began to work fine. This prompted me to
check my root hints server list hoping it was out of date, unfortunately
(depending on how you look at it), the root hints were all current. Here is
the result of the two bat files:


----------------------------------------------------------------------------------------------
H:\>nslookup -qtype=ns t-systems.at. 193.171.255.2
(root) nameserver = l.root-servers.net
(root) nameserver = m.root-servers.net
(root) nameserver = a.root-servers.net
(root) nameserver = b.root-servers.net
(root) nameserver = c.root-servers.net
(root) nameserver = d.root-servers.net
(root) nameserver = e.root-servers.net
(root) nameserver = f.root-servers.net
(root) nameserver = g.root-servers.net
(root) nameserver = h.root-servers.net
(root) nameserver = i.root-servers.net
(root) nameserver = j.root-servers.net
(root) nameserver = k.root-servers.net
a.root-servers.net internet address = 198.41.0.4
a.root-servers.net AAAA IPv6 address = 2001:503:ba3e::2:30
b.root-servers.net internet address = 192.228.79.201
c.root-servers.net internet address = 192.33.4.12
d.root-servers.net internet address = 128.8.10.90
e.root-servers.net internet address = 192.203.230.10
f.root-servers.net internet address = 192.5.5.241
f.root-servers.net AAAA IPv6 address = 2001:500:2f::f
g.root-servers.net internet address = 192.112.36.4
h.root-servers.net internet address = 128.63.2.53
h.root-servers.net AAAA IPv6 address = 2001:500:1::803f:235
i.root-servers.net internet address = 192.36.148.17
j.root-servers.net internet address = 192.58.128.30
Server: UnKnown
Address: 193.171.255.2:53

t-systems.at nameserver = ns2.t-systems.at
t-systems.at nameserver = ns1.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

H:\>nslookup -qtype=ns t-systems.at. 192.92.125.2
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
Server: UnKnown
Address: 192.92.125.2:53

t-systems.at nameserver = ns2.t-systems.at
t-systems.at nameserver = ns1.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

H:\>nslookup -qtype=ns t-systems.at. 81.91.161.98
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
Server: UnKnown
Address: 81.91.161.98:53

t-systems.at nameserver = ns2.t-systems.at
t-systems.at nameserver = ns1.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

H:\>nslookup -qtype=ns t-systems.at. 87.233.175.130
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
Server: UnKnown
Address: 87.233.175.130:53

t-systems.at nameserver = ns1.t-systems.at
t-systems.at nameserver = ns2.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

H:\>nslookup -qtype=ns t-systems.at. 192.76.243.2
Server: UnKnown
Address: 192.76.243.2:53

t-systems.at nameserver = ns1.t-systems.at
t-systems.at nameserver = ns2.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

H:\>nslookup -qtype=ns t-systems.at. 195.66.241.82
Server: UnKnown
Address: 195.66.241.82:53

t-systems.at nameserver = ns1.t-systems.at
t-systems.at nameserver = ns2.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

H:\>nslookup -qtype=ns t-systems.at. 204.152.184.202
Server: UnKnown
Address: 204.152.184.202:53

t-systems.at nameserver = ns1.t-systems.at
t-systems.at nameserver = ns2.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

H:\>nslookup -qtype=ns t-systems.at. 206.65.170.101
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
Server: UnKnown
Address: 206.65.170.101:53

t-systems.at nameserver = ns1.t-systems.at
t-systems.at nameserver = ns2.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

H:\>nslookup -qtype=ns t-systems.at. 210.81.13.181
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
Server: UnKnown
Address: 210.81.13.181:53

t-systems.at nameserver = ns1.t-systems.at
t-systems.at nameserver = ns2.t-systems.at
ns1.t-systems.at internet address = 212.31.86.100
ns2.t-systems.at internet address = 212.31.88.100

-------------------------------------------------------------------------------

H:\>nslookup -qtype=a ns1.t-systems.at. 193.171.255.2
(root) nameserver = i.root-servers.net
(root) nameserver = j.root-servers.net
(root) nameserver = k.root-servers.net
(root) nameserver = l.root-servers.net
(root) nameserver = m.root-servers.net
(root) nameserver = a.root-servers.net
(root) nameserver = b.root-servers.net
(root) nameserver = c.root-servers.net
(root) nameserver = d.root-servers.net
(root) nameserver = e.root-servers.net
(root) nameserver = f.root-servers.net
(root) nameserver = g.root-servers.net
(root) nameserver = h.root-servers.net
a.root-servers.net internet address = 198.41.0.4
a.root-servers.net AAAA IPv6 address = 2001:503:ba3e::2:30
b.root-servers.net internet address = 192.228.79.201
c.root-servers.net internet address = 192.33.4.12
d.root-servers.net internet address = 128.8.10.90
e.root-servers.net internet address = 192.203.230.10
f.root-servers.net internet address = 192.5.5.241
f.root-servers.net AAAA IPv6 address = 2001:500:2f::f
g.root-servers.net internet address = 192.112.36.4
h.root-servers.net internet address = 128.63.2.53
h.root-servers.net AAAA IPv6 address = 2001:500:1::803f:235
i.root-servers.net internet address = 192.36.148.17
j.root-servers.net internet address = 192.58.128.30
Server: UnKnown
Address: 193.171.255.2:53


H:\>nslookup -qtype=a ns1.t-systems.at. 192.92.125.2
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
Server: UnKnown
Address: 192.92.125.2:53


H:\>nslookup -qtype=a ns1.t-systems.at. 81.91.161.98
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
(root) nameserver = C.ROOT-SERVERS.NET
Server: UnKnown
Address: 81.91.161.98:53


H:\>nslookup -qtype=a ns1.t-systems.at. 87.233.175.130
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
Server: UnKnown
Address: 87.233.175.130:53


H:\>nslookup -qtype=a ns1.t-systems.at. 192.76.243.2
Server: UnKnown
Address: 192.76.243.2:53


H:\>nslookup -qtype=a ns1.t-systems.at. 195.66.241.82
Server: UnKnown
Address: 195.66.241.82:53


H:\>nslookup -qtype=a ns1.t-systems.at. 204.152.184.202
Server: UnKnown
Address: 204.152.184.202:53


H:\>nslookup -qtype=a ns1.t-systems.at. 206.65.170.101
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
Server: UnKnown
Address: 206.65.170.101:53


H:\>nslookup -qtype=a ns1.t-systems.at. 210.81.13.181
(root) nameserver = A.ROOT-SERVERS.NET
(root) nameserver = B.ROOT-SERVERS.NET
(root) nameserver = C.ROOT-SERVERS.NET
(root) nameserver = D.ROOT-SERVERS.NET
(root) nameserver = E.ROOT-SERVERS.NET
(root) nameserver = F.ROOT-SERVERS.NET
(root) nameserver = G.ROOT-SERVERS.NET
(root) nameserver = H.ROOT-SERVERS.NET
(root) nameserver = I.ROOT-SERVERS.NET
(root) nameserver = J.ROOT-SERVERS.NET
(root) nameserver = K.ROOT-SERVERS.NET
(root) nameserver = L.ROOT-SERVERS.NET
(root) nameserver = M.ROOT-SERVERS.NET
Server: UnKnown
Address: 210.81.13.181:53



"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Read inline please.
>
> In news:E2505B9F-DD2E-4A1B-AAD1-,
> Chris Ramsay <> typed:
> > Hello,
> >
> > Yes recursion is enabled and the DNS server works just fine using
> > standard root hints. The problem seems to be that if the server
> > finds a folder with the domain name in its cache file, it will not
> > use recursion to find any missing or incomplete information inside of
> > that folder.
>
> Are you still having a problem?
> I notice that there has been a change in the TTL for both the NS record and
> A record, both now have TTL of 3 hours.
>
> When you run nslookup ns1.t-systems.at. against your DNS does it fail?
>
> >
> > The proof of this is that I can delete just the t-systems folder from
> > cache and the dns server begins resolving the name normally again. A
> > while later though, the A records disappear from the t-systems folder
> > leaving just the ns records and dns queries for t-systems fail until
> > I remove the folder again.
>
> Are you using a Forwarder?
> If so, what is the forwarder's IP address?
> Does the forwarder answer correctly when you run
> nslookup -qtype=ns t-systems.at <ForwarderIP>
>
> IF it doesn't run it with the debug switch
> nslookup -d2 -qtype=ns t-systems.at <ForwarderIP>
>
> Create two batch files, one with the NameServer lookup against the at
> servers and one with the a record lookup for ns1.t-systems.at.
> Use this command and attach the txt file output to your next post.
>
>
>
> nslookup -qtype=ns t-systems.at. 193.171.255.2
> nslookup -qtype=ns t-systems.at. 192.92.125.2
> nslookup -qtype=ns t-systems.at. 81.91.161.98
> nslookup -qtype=ns t-systems.at. 87.233.175.130
> nslookup -qtype=ns t-systems.at. 192.76.243.2
> nslookup -qtype=ns t-systems.at. 195.66.241.82
> nslookup -qtype=ns t-systems.at. 204.152.184.202
> nslookup -qtype=ns t-systems.at. 206.65.170.101
> nslookup -qtype=ns t-systems.at. 210.81.13.181
>
> nsbatchfilename.bat >t-systemsNS.txt
>
> nslookup -qtype=a ns1.t-systems.at. 193.171.255.2
> nslookup -qtype=a ns1.t-systems.at. 192.92.125.2
> nslookup -qtype=a ns1.t-systems.at. 81.91.161.98
> nslookup -qtype=a ns1.t-systems.at. 87.233.175.130
> nslookup -qtype=a ns1.t-systems.at. 192.76.243.2
> nslookup -qtype=a ns1.t-systems.at. 195.66.241.82
> nslookup -qtype=a ns1.t-systems.at. 204.152.184.202
> nslookup -qtype=a ns1.t-systems.at. 206.65.170.101
> nslookup -qtype=a ns1.t-systems.at. 210.81.13.181
>
> Alookupbatch.bat >t-systemsA.txt
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>