Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS resolution failure

Status
Not open for further replies.

ncvandy

MIS
Jul 10, 2001
53
US
We are currently a NT 4, sp6 domain, xxx.com. In preparation to changing the domain to win 2k I have been trying to set up a DNS server (primary zone) on a win2k member server. The network setup is as following:

1. DNS service and our company website are both outsourced.
2. We run our own internal e-mail (exch 5.5) with external email outsourced.
3. Our internal network uses the same registered domain name (xxx.com) that resolves back to the outsourced DNS servers. The internal network uses a private address scheme. (I know it would be easier to use a non-registered internal name but political considerations prevent it).

So far I have done the following:

- deleted the '.' root zone and set up forwarders to resolve external names.
- hard-coded a and mapped it to the external Internet address
- created mx records that point to the mail servers

With the above I can send mail and browse the net from a client station that I set up. I can also resolve clients that I have created host records for. What I cannot do is resolve the domain name, i.e. xxx.com. Everything else seems to work fine.
If I use nslookup on xxx.com I get
server: dnstest.xxx.com
address: 192.168.16.254
name: xxx.com (with no address resolution)

Pinging xxx.com I get: unknown host xxx.com

How do I make my server resolve to the address that I would get if I used my outsourced servers. I cannot seem to make an alias work for this. I would like to get this solved before I move on to testing dynamic updates.
I have searched the other posts on DNS and did not see a solution to my problem. Any help that you can give me on this is greatly appreciated. I have been beating my head on this one for a couple of days with no success.

Thanks in advance,
Jim
 
ignore above, found the solution and i'm up and running. Jim

Elegant solutions are nice, but right now I'll settle for whatever works.
 
please post your solution so others might benefit from your experience.
 
What was your solution? I'm currently in the same situation as you.

 
Sorry for the delay in reposting folks, my solution was to open up 'name servers tab' under the foward lookup zone properties and add my domain name as a name server, i.e.
xxx.com 216.x.x.x. After I did this all resolutions worked properly.

One thing that is not listed above but is necessary for the client machines to connect to the outside world is setting up the external servers as fowarders on the local DNS.
Jim

Elegant solutions are nice, but right now I'll settle for whatever works.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top