If you tell the test host to use 192.168.63.11 as its DNS server, can nslookup then do a reverse lookup of 192.168.63.1 (the router's internal IP address)? If not, then that is probably your problem, and you fix it by adding appropriate information to your LAN-authoritative DNS records on 192.168.63.11 (an entry similar to whatever one lets it respond to a reverse lookup of 192.168.63.11 with the FQN mlsad2.mydomain.com). If yes, then I don't (yet) have a suggestion as to what might be causing the problem.
At 03:43 PM 11/7/2003 -0500, ALParada wrote:
See below.[...]
If I do an nslookup with 192.168.63.11 configured as primary I get:[...]
C:\Documents and Settings\aparada>nslookup Default Server: mlsad2.mydomain.com Address: 192.168.63.11
192.168.63.11 is my primary dns server. Yes it's a W2K Server, sorry.
If I change my primary dns to 192.168.63.1 which is the loc of LRP I get:
C:\Documents and Settings\aparada>nslookup *** Can't find server name for address 192.168.63.1: Non-existent domain Default Server: mlsad3.med-lab.com Address: 192.168.63.13
It obviously goes to the secondary 192.168.63.13
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
