DNS resolution

[wafer157]

Hello,
We are running AD and DNS on a server 2000 box. We are attempting to access a portal hosted on another domain. When I do an nslookup I get the following.

username.domain>nslookup portal.domain.com
*** Can't find server name for address 10.10.10.1: Non-existent domain
Server: freud.mec.edu
Address: 216.20.63.145

Name: portal.domain.com
Address: 216.20.10.16


If I use both the ISP DNS addresses I get out to the site without a problem. However, we do need to use an internal IP for our DNS.

How can I add the portal to our DNS and make it work? Thanks for any ideas or thoughts.

 

[ShackDaddy]

That NSLOOKUP sample that you pasted in doesn't actually show any significant errors. It just said it doesn't know the name of YOUR local DNS server. It resolved the portal.domain.com address just fine. Why do you think you need to have it in your internal DNS? Are your users having trouble accessing it?

Is your domain connected to that remote domain's network via a private WAN link, or do you connect across the internet without a VPN? If you use the public internet, you should just use the public IP.

ShackDaddy

 

[wafer157]

ShackDaddy,
Whne I do a ping on our domain it points to another server on the network and not the DNS server. The sever it points to does not have DNS installed. So when I do the NSlookup it can not find the server the portal appears to be pointing at. I need to learn how or figure out how I can have our domain address point to the correct IP or the ip I want since the portal is looking for that internal IP.

I have tried the IP address in a browser, but it still does not allow the service to work. I have also added an A record in DNS to insure the portal is replicating.

Additionally, on our DNS server - if I change the DNS to include both our ISP addresses and not our internal IP we get to the portal without a problem.

I am not an expert on DNS and appreciate any suggestions.
Thanks

 

[ShackDaddy]

Ok, I need a bit more information. Is the 216.20 network your internal lan ip space? Is it NATted? Or is that the external networ? And how does the internal DNS space differ from the external? IE, external is "domain.com" and internal is "domain.int" or "intdomain.com". Or are they the same? Seems like they might be the same if when you put in the FQDN (Fully Qualified Domain Name) of "portal.domain.com" you get an internal server. Or are you just trying to connect to "portal"?

So when you look at your internal DNS, you can't find a record that would be responsible for sending your request to the internal server instead of the external one? And when you created an A record, where did you create it, and what was the name of the zone that you created it in? If the record is there, and you are able to see it by running NSLOOKUP on the server, then your clients who are pointed at your server should be able to use it.

If you can answer the questions I've asked, we can resolve this.

ShackDaddy

 

[wafer157]

Hello Shack Daddy,
I have figured it out. Once I added an A record and a PTR record into my DNS the site came up. The ISP still needs to resolve our login issues to the portal, but that is on their end.

I want to thank you for all information. It was very helpful in giving me ideas and areas to look for.
Thanks,
Wafer157