Unable to Resolve Hostname via VPN Connection - Page 2

Quote:

Originally Posted by mybeat 

You need to add BPGC.local to list of your DNS suffix search list. it's not shown in ipconfig /all output.
DNS server accepts queries from you, this is seen in seconds nslookup output

Quote:

Originally Posted by tompsonn 


Its a no-no because if Windows switches to it for whatever reason (local DNS becoming unavailable), you won't be able to resolve local host names. Even if the primary local DNS comes back up, Windows likely won't switch back.
As mentioned above, nslookup appears happy so the DNS server is accepting queries properly. Again, as mentioned above, you're missing the DNS suffix - it needs to be added to the VPN connection list.

Thanks for your patience guys, I'm new to the whole DNS suffix setting -- I'm still having a little trouble.

The setting keeps reverting. I think I may not be entering the proper string. 

Here is a video that conveys the issue better than I could explain:

Quote:

Originally Posted by mybeat 

That is wierd, can you add dns suffix to your "Local area #2" nic just to test if the same behaviour remains?

That did the trick - I am now able to resolve hostnames.

When I added it to LAN #2, it retained the setting. It also appeared in BPGC VPN settings. Is it a global setting?

Side Topic:

Is including a DNS Suffix in the configuration settings standard operating procedure for creating a Windows VPN connection, or is this work around to solve a problem with my server configuration?

I've got the same problem on a different computer.

Do I need to open a port for DHCP on my gateway firewall at my office? I'm guessing no... But want to check.

It's strange that both computers failed to register a DNS suffix. Both computer's ipconfig state "DHCP Enabled: No". 

If DHCP is disabled, how is it getting an IP address within the DHCP pool?

@mybeast: I'm familiar with what WireShark is, but never had the opportunity to learn how to use it. How do I apply the DHCP filter for the NIC?

Wow, you explained that perfectly. I had one of those "ah-ha!" moments reading your explanation and everything clicked.

The only thing I don't understand is why the connection-specific DNS suffix does not automatically configure - on any machine.

I can't resolve hostnames on any remote computer, on any remote network  (unless setting the suffix).

• Localnet DHCP is handled by an Airport Extreme.
• Domain DHCP is handled by the Domain Controller (SBS08)
• VPN is RAS (SBS08)

Now, forgive me if I am being a complete rook here - but...

Would disabling "Obtain DNS server address automatically" and setting my own (of 10.10.0.10/8.8.8.8) be causing the issue (as you mentioned earlier)?

I set DNS to auto on LAN 2 and DNS to 8.8.8.8/8.8.4.4 in my Airport Extreme (per your recommendation) and everything seems to be working the way it should.  

Is this the way I should be configuring my remote locations? If so, I think you guys solved this and we can put this thread out of it's misery.