Windows dns forward lookup zone not updating should i trust my instincts dating

I would take any errors at this point just from a troubleshooting standpoint.

Also, I need to see why a secondary NIC IP that I deleted from the copper.local forward lookup zone and set the interface to not register in DNS still shows up in the secondary copper.local zone on the Boalsburg server after a successful zone transfer. I'm sure whatever it is, I'll get bit by it some day.

That change was replicated to the other copper.local domain controller. I'd be looking at the VPN configuration between sites now and verifying personally that the crypto maps and firewall rules actually do allow all traffic. And of course, the obvious launching of the DNS management console as Run As Administrator. I would also be using something like wireshark to see wtf is being passed to and fro. Posts in this and the Server Room forum have saved my bacon many a time. I'd be looking at the VPN configuration between sites now and verifying personally that the crypto maps and firewall rules actually do allow all traffic.

One thing to note, if there is any filtering, is that zone transfers (AFXR/IXFR) with windows do NOT use UDP/53. So if your network/VPN admin is saying 'oh yeah, we allow DNS' he may be only allowing port 53. One thing to note, if there is any filtering, is that zone transfers (AFXR/IXFR) with windows do NOT use UDP/53. So if your network/VPN admin is saying 'oh yeah, we allow DNS' he may be only allowing port 53.

I don't actually see any error messages associated with this, either in DNS or general System logs.

The only events I see are Parkserv transferring an updated zone version for copper.local to Boalsburg and then I see the Boalburg server confirming that it updated the zone information for the copper.local domain - nothing about the blackberry.local domain.

If anyone would like I could post the sanitized configs on both ASA's. That change was replicated to the other copper.local domain controller."This turned out to be the source of the issue.

The 192.168.1.50 address is a virtual interface for a single Hyper-V guest on a secondary physical interface - oh yes they're rocking Hyper-V on a DC.

I reason I could still see the pings from 'PARKSERV' in the ASA logs was that the 'PARKSERV' was a named network object that included both IP addresses as the hosts.

However, when I attempt to create the blackberry.local forward lookup zone on Parkserv I get to the "Master DNS Server" page of the wizard and after I enter the IP address of Boalsburg (192.168.251.1) it fails.

It attempts to resolve/validate the DNS server, but the FQDN just gets resolved to the Netbios name BOALSBURG and under 'Validated' it just says 'A timeout has occurred' - WINS is enabled on the 2003 server and I assume that's why I'm at least getting something under FQDN.

Search for windows dns forward lookup zone not updating:

windows dns forward lookup zone not updating-65

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “windows dns forward lookup zone not updating”

  1. I'm looking forward to continued support from Dina and SHEpherd Consulting. Not only did I feel comfortable but I received practical advice. I have and will continue to recommend these services to my friends and family, Nekeidra was amazing to work with.

  2. Dave says, "Personal finance is 80% behavior and only 20% head knowledge." Even though your choices landed you in a pile of debt, you have the power to work your way out! The solution isn’t a quick fix, and it won’t come in the form of a better interest rate, another loan, or debt settlement.