Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, June 25, 2014 10:05 AM
Dear all
I have a strange(?) problem with a DNS Stubzone.
My Setup:
My Domain: a.bla.com (Win2k8R2)
Other Domain: b.bla.com (Win2k12R2)
file.b.bla.com - 192.168.2.50
www.b.bla.com - 192.168.2.51
I created in the DNS Servers of both Domains a DNS Stub Zone to the other Domain.
Now i am sitting in Domain a.bla.com:
nslookup file.b.bla.com --> Works, i get 192.168.2.50 as answer
nslookup www.b.bla.com --> can't find www.b.bla.com: Non-existent domain
If i do nslookup www.b.bla.com in the b.bla.com Domain it works as it should.
I dont understand what is wrong and why it is not working with www.b.bla.com.
Thanks for any hints.
JBAB
All replies (2)
Thursday, June 26, 2014 11:19 AM ✅Answered
Hi,
First, Try the steps below on both DNS server:
- Run a cmd, execute “ipconfig /flushdns” and “Dnscmd /clearcache”
- Run nslookup both server, check whether the problem is resolved.
If it doesn’t work, it means that there is something wrong with the DNS configuration.
When a DNS client performs a recursive query operation on a DNS server hosting a stub zone, the DNS server uses the resource records in the stub zone to resolve the query. The DNS server sends an iterative query to the authoritative DNS servers specified in the NS resource records of the stub zone as if it were using NS resource records in its cache.
If the DNS server cannot find the authoritative DNS servers in its stub zone, the DNS server hosting the stub zone attempts standard recursion using its root hints.
Check that is there any error or warning related DNS in the event viewer?
If it is possible, could you run the nslookup on the DNS server in debug mode, then post the debug information?
- Run a cmd, execute “nslookup”
- Execute “set d2”
Hope this helps.
Steven Lee
TechNet Community Support
Friday, June 27, 2014 4:49 AM
Hi Steven
Thanks for the suggestions.
I could (hopefully) fix it with flushing the DNS Server Cache on both DNS in Domain A. Now it works also with www.b.bla.com
Thanks :)