Networks

Ask something
Discussion Locked

DNS

0 helpful
3 replies

by quintar51

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

A friend of mine and I are trying to settle an argument.

I have 'mydomain.com' registered with a hosting company, zoneedit.com.

Now I want to setup DNS internally but I want to seperate the namespace, for example, 'corp.mydomain.com' will be my internal zone.

My friend claims that I'll need to first setup a DNS server with an external zone of 'mydomain.com', have records of WWW and MX pointing to my public IP, 216.x.x.x. Then, I setup another DNS server, with a zone for 'corp.mydomain.com' and only have records for WWW and MX but they point to my internal IP, 192.x.x.x.

I say I only need to setup one DNS server, for 'corp.mydomain.com', with records that point to my internal IPs. My external zone is already hosted with Zoneedit.com, so there's no need to setup another DNS server with the same zone.

who's right?

3 replies

by greybeard770

You are both right, depending on the interaction between the internal and external DNS servers.

It has become popular to have an external DNS server for the whole world and an internal DNS server for the organization. You would make them both the SOA (start of authority) for the domain but not allow them to communicate. That way you don't need a seperate namespace and the extra typing that goes with it. The only real downside is that you have to update both resources if a public addresschanges.

It sounds like if you do what your friend is saying that your internal DNS server records would be available through the external DNS server. You probably don't want that.

This discussion is closed to new replies.