15th August 13:00
When I take out an irrelevant listening IP, my DNS breaks.
My DNS server has two separate IP addresses tied to the same adapter. One
of them is an IP I have mapped to the outside world. The other is strictly
for my primary internal DNS server.
I noticed the other day that I had both IP addresses listed on the
Interfaces tab under properties. I took the external IP out of the list.
Nobody, to my knowledge, is pointing to this external IP for DNS lookups.
All of my clients are configured to use the internal address.
The next day after I made the change, I got errors about failed zone
transfers from my secondary DNS server. After a minute of looking around, I
went to the monitoring tab and tried some test lookups. The recursive
queries were passing and the simple queries were failing. I did the same
thing on my primary server and both tests failed! I restarted the DNS
service on my secondary and both test lookups started working again, but
when I restarted the DNS service on my primary both test lookups were still
failing. I finally figured out that if I put my external IP back into the
listening list that the problem finally goes away.
Here are some more details:
- Running Win2k SP3 on both servers
- The external IP is actually an internal IP that is mapped to external (or
real-world) IP via NAT
I wonder why that IP address has to be in the DNS config for things to work
right. Any help you could offer would be much appreciated.
18th August 09:42
Kevin Vaughn <email@example.com> posted their concerns
Then Kevin made his reply below:
Can you post an ipconfig /all you could just have a gateway problem run
netdiag /v /fix
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
When responding to posts, please "Reply to Group" or
"Reply All" via your newsreader so that others may learn
and benefit from your issue
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
Keep a back up of your OE settings and folders with
29th August 12:34
Anytime there is a dual NIC setup with DNS involved, takes a little care on
the config to get it to work correctly.
Run what Kevin suggested. Also, do you use a forwarder? Use a forwarder.
If forwarding is grayed out, delete your root zone.
On both NIC properties, do they both point ONLY to this DNS server? Make
both NICs IP Properties only point to the internal IP.
Listeners just says it will listen to requests on that interface (IP). It
really shouldn't have anything to do with "breaking" DNS. As for zone
transfers, what IP is set as the Master IP on the machine holding the
Testing for queries, either authorative or recursive hopefully means that
both NICs point to itself and forwarders are enabled.
Also, in Network and Dialup Settings, Adv menu, Adv settings, make sure the
internal interface is at the TOP of the binding order and not the bottom.
That's important for the machine to always check with the internal card
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory