Question Locked

DNS Newbie: Forward Lookup Zones On Non-Web Servers

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

I've got a decent grasp on DNS, but have a situation I'm a little confused on currently.

I'm working on an office network consisting of a Windows 2000 domain controller, Windows 2003/Exchange 2003 mail server, and several workstations. Our firewall is a SonicWall.

The company's websites are all hosted off-site by a company that handles all related DNS. We're about to switch hosting companies for our off-site websites, thus IP addresses will be changing. I've got the DNS ready to go with the new hosting company, but it's the in-office set-up that I'm worried about. See, on the in-office domain controller there are Forward Lookup Zones created for some, not all, of the domains that are hosted off-site. That being said, any DNS changes done to those domains off-site, have to be duplicated here in the office.

My question is this... are these Forward Lookup Zones even necessary? They don't exist for all the domains hosted off-site by the company, and they don't exist for all of the domains we handle mail for here in the office. Each workstation in the office is set to use the domain controller as it's sole DNS server, and the SonicWall firewall is set up to use DHCP, with it's DNS servers as 1) the domain controller again, and 2, 3) our ISP's DNS servers. Correct me if I'm wrong, please, but with workstations being set to look at the domain controller ONLY for DNS, I'm assuming it still rolls over to the DNS set up in the SonicWall (the domain controller again, then two of our ISP's DNS servers) for any requests not filled by the domain controller? Thus, if I deleted these Forward Lookup Zones in-office, requests for those websites should, like all others, go out to our ISP's DNS servers? No?

4 replies

by cg it

I believe you have 2 issues. First one being public web servers. Second your private network.

for public web server issues:
public web sites require authoritative name servers to resolve WhoIS queries. If your DNS server is an authoritative name server for any of the domains, meaning it will answer public WhoIS queries for the domain names, then you can't get rid of DNS records for any of those domain names. IF your DNS server is not the authoritative name server for the domain names, then having records for them just takes up space and uses system resourses and possibly cause query resolution problems.

For private network issues:
Since you run Exchange Server 2003 I'm assuming you have an Active Directory based private network. That being the case, DNS must be present and functioning for the private network domain namespace for Active Directory to work. If you delete DNS records for the private network, you'll break Active Directory and probably break you mail server as well.

ISPs DNS servers are only unsed for internet connectivity. your sonicwall will have your ISP DNS servers listed on the WAN link.

Private DNS servers that can't resolve domain name queries forward those requests to Internet DNS servers which will forward to root hint servers if they can't answer the query.

by ckowalski

PUBLIC WEB SERVER ISSUES:

The authoritative name servers for our domains, which are again, hosted off-site, are the name servers of our hosting company.

PRIVATE WEB SERVER ISSUES:

I'm assuming Exchange just needs the Forward Lookup Zones for machinename.domainname that I see built in our in-office DNS? I wouldn't be touching those. The two records in question are for some of our off-site hosted .com domains. The records have the standard SOA records (mapped to the in-house machinename.domainname, MX records (to our in-house mail server IP address), and then the off-site IP address of our website.

by cg it

not our place to say delete the records. That's something you have to decide yourself. All we can do is provide suggestions to questions, links to information and so forth.

for DNS an analogy is useful. Think of DNS as your house address. you can have multiple names delivered to the same address. but try to have your name delivered to multiple addresses. Doesn't work very well.

This discussion is closed to new replies.