Question about Name Resolution and DNS 2

[mrdenny]

I've got a VPN Server setup in the 2k3 domain. No DHCP on the network at this point. The VPN works fine, but name resolution isn't working correctly.

When I've VPNed in if I do an nslookup it goes to the DNS servers setup for my NIC (which I get through dhcp from my Linksys router) then it does to my DNS servers which are on the VPN connection.

This works fine for looking up yahoo or microsoft. The problem is when I need to lookup internal servers IPs. Since our domain is a non-registered domain (ie. mydomain.int) it can't be found on the public DNS servers that I use from my ISP.

Any ideas?

TIA.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[aftertaf]

a bit lost here... you have an internal DNS server, right? but don't you use it to resolve internal IPs and to forward other requests to your ISP DNS servers??


Aftertaf

"Solutions are not the answer." - Richard Nixon

 

[mrdenny]

I'll try to explain better.
I've got an internal DNS server for AD.
My internal domain name is company.int.
When at the office everything works fine.
When I VPN into my 2k3 VPN server my pc is using my home ISP DNS Servers first (Cox.net). Because the domain doesn't exist I get a message back from the Cox DNS server saying domain doesn't exist.

What I need to know is how do I get the DNS for the VPN connection to be checked first.

Does that explain it better?

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[wdoellefeld]

What are you using for VPN?

FRCP

http://www.frcp.net

 

[Tinman0330]

Hope this helps..

cox.net must have a dns entry directing comany.int to the public ip of company.int. Your home computer must be using cox.net as the primary dns. Have you tested vpn internally?

Or you could just vpn to the public ip of company.int. when connected dns entries on company.int will apply to your home computer.

I am currently doing the same thing you are. I use the second option but not for long...Just got a registered name! It's less than $10 a year so it's worth it! Hope this helped...

 

[Tinman0330]

sorry I don't think I read correctly... I think you already new all of that. Well about seeing the vpn's dns first; when i vpn to my other lan my computer starts using the vpn's dns automatically. I never changed anything...It just worked....

I know "It just worked" is not a solution, but is it possible that you are using that dns but the entries are wrong?

maybe this one will help!
if I am misunderstanding you again you have permission to yell at me! ... haha

 

[mrdenny]

ok, I swear it wasn't working before, but now it is.

New question though. If I ping server1.company.int it works fine. If I ping server1 is doesn't come back with anything.

Ideas?

I'm assuming I'm missing some stupid setting somewhere.

Please keep in mind at the moment we don't have a DHCP server setup. We have an IP range entered into the RRAS setup for the VPN. Saddly this means that I can't edit the DHCP settings.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[Tinman0330]

How are your DNS entries for that Comp setup?

Create a new (A Host) assigning server1 to the appropriate internal IP address. Should work!

 

[mrdenny]

DNS is dynamic update. All the servers have A records.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[Tinman0330]

Although it is dynamic you can still add records manually. Server1 is on a static ip I hope? If not let me know.

Create a new (A Record) with the following

Parent: company.int

Host: server1

IpAddress: The static ip of server1

If the servers are not on static it will cause alot of problems.

Hope it was helpfull! Will check back in a few

 

[aftertaf]

have you setup any suffixes on the tcp connection for the pc that VPNs in, or on the VPN server?

if the fqdn resolves, then it IS working, but try an nslookup for the server host name and the server fqdn, see what it returns you.

Aftertaf

"Solutions are not the answer." - Richard Nixon

 

[mrdenny]

I think it is a domain suffix setting problem.

Apparently without a DHCP server that setting doesn't get pushed out to the VPN clients from the VPN server like the DNS Settings do.

I guess that will just have to wait until we switch from public IP to private IP and get the DHCP server setup.

Thanks for the help.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)