• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 457
  • Last Modified:

Set up Public DNS

We have  internal DNS zones, some of them ar AD Integrated and some are Primary/Secondary zones.
Example
AA.com
BB.com
CC.DD.com
FF.com
GG.HH.com

I want public users to be resolved to the same zones:
AA.com
BB.com
CC.DD.com
FF.com
GG.HH.com

But without having them create records in DNS.
I thought about creating 2 DNS servers Primary and Secondary and put them in the DMZ, I am not sure if they need to be member servers or not joined to the domain at all.
Any suggestions?

Thanks





0
jskfan
Asked:
jskfan
  • 3
  • 3
  • 2
2 Solutions
 
ibiadmin6Commented:
Public DNS zones should be on a different server than your internal private zones!

You should not expose your internal zones to the internet!

That said the internal zones should be private ip address ranges which are not routable on the internet. So type or Nat'ing should be required using firewalls to resolve internal DNS from the Internet.
0
 
jskfanAuthor Commented:
ibiadmin6:

I looked at this link:
http://www.isaserver.org/tutorials/You_Need_to_Create_a_Split_DNS.html

I don't know why it's so complicated compared to what you have suggested.
0
 
Chris DentPowerShell DeveloperCommented:

There are a few reasons you should use Split Brain rather than just making those zones public:

1. AD Intregrated Zones make really crappy public zones. They have invalid SOA records, generally invalid NS records, and tend to contain a lot of private data that really shouldn't be publicly available.

They're fine for internal use, that's what they were built for.

2. If you use your DNS servers to resolve external names as well as authoritative domains you have no way of stopping someone out on the Internet using it for that. At best it means you might have to put up with external people using your DNS server as a resolver. At worst it opens you up to attack.

This is more of a limitation in MS DNS. BIND does allow you to differentiate based on the source of the request.

The disadvantage of Split Brain is clear, you have to maintain two copies of the same zone. But sometimes there's not much of a way around that.

Chris
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
ibiadmin6Commented:
I agree and it is confusing in the beginning but will make sense. The comment i made above was using split DNS as we do currently.

It is easier to maintain if the internal namespace is a different name than the external namespace also. Ours is not unfortunately.
0
 
jskfanAuthor Commented:
so I can put the following zones in both internal and external DNS servers:
AA.com
BB.com
CC.DD.com
FF.com
GG.HH.com


With the Registrar I will Registrar all the above Zones point to the same public IP ex: 64.64.64.64

in the firewall NAT (  will translate the Public IP 64.64.64.64 to the IP address of the DNS server in the DMZ)
in the DNS inside the DMZ I will create the zones and inside each zone I will create records pointing to web, FTP servers, etc..)

Regarding the internal DNS, I will have nothing special to do, leave AD integrated zones.

Is this correct?



0
 
Chris DentPowerShell DeveloperCommented:

If the Internal (AD) DNS servers are remaining separate from the public system then no changes are required  there.

Chris
0
 
ibiadmin6Commented:
1. At the registrar you point your domains DNS servers to your new external DNS servers. This would typically be a by domain setting where your domains are registered. Beware this takes 24 hours or more to complete etc.

2. I advise two External DNS and are recommended for failover, and actually required for external DNS server hosting by the RFC's.
0
 
jskfanAuthor Commented:
<<<<1. At the registrar you point your domains DNS servers to your new external DNS servers. This would typically be a by domain setting where your domains are registered. Beware this takes 24 hours or more to complete etc.>>>>

the external dns server is in the DMZ and it has a private IP address.
I thought at the registrar, I will buy a public IP (64.64.64.64)  that points to our domain name ex: xyz.com
and our firewall external NIC will have the same IP (64.64.64.64), and the firewall will NAT this public IP to the internal IP address of the DNS in the DMZ ex:10.10.10.10.

Correct?
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now