Getting Back To A Single Forward Lookup Zone

During our long migration from NT to Windows 2003 we ended up with 2 DNS forward lookup zones, fbc.ca and fbc.internal.  I think I recall the reason we did that was because our registered internet domain is fbc.ca and I didnt want to have it as a DNS FLZ.

Our web site is www.fbc.ca and has a ip address in our FLZ's to point to it so I dont see any reason to keep fbc.internal as a FLZ in DNS. Is there any reason that I cant just have one single DNS FLZ as fbc.ca, deleting fbc.internal ?
tmccabeAsked:
Who is Participating?
 
JamesDSConnect With a Mentor Commented:
tmccabe
well, I failed so miserably on the last one, I thought I owed you one :)

Actually, I am in the UK, so this is hometime for me

Cheers

JamesDS
0
 
JamesDSCommented:
tmccabe
If your AD Domain is called fbc.internal then you should keep it. Having AD register it's records into another DNS Domain nasty and not recommended.

If the Authority for your EXTERNAL domain (FBC.CA) is not you, then you could set forwarders on the AD DNS Server to piont to your ISPs DNS servers and get rid of the FBC.CA zone instead.

Cheers

JamesDS
0
 
JamesDSCommented:
tmccabe
I ran NSLOOKUP on your external domain:

fbc.ca  nameserver = ns1.nucleus.com
fbc.ca  nameserver = ns.nucleus.com
ns.nucleus.com  internet address = 66.18.192.250
ns1.nucleus.com internet address = 66.18.192.251

FBC.C resolves to: 207.34.101.232

which suggests that you are NOT the authority for your DNS domain and therefore forwarders should work fine.

Cheers

JamesDS
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

 
tmccabeAuthor Commented:
James-do you ever do any work or just wait around for my questions ? : )
0
 
tmccabeAuthor Commented:
because our web site is www.fbc.ca I had to add an entry in DNS to point to it so our internal users can get to it.
That A record in DNS is inside the fbc.ca FLZ. So you say I should point my forwarders to the external ISP name servers, kill the fbc.ca FLZ and stay with the single flz of fbc.internal. Is that correct ?
0
 
JamesDSCommented:
tmccabe
It depends on your AD and the dns authority for your external domain.

If the ONLY thing in the FBC.CA zone is the WWW entry (or all entries point to external ip addresses) and your AD is using the .internal FLZ then you can indeed use forwaders.

If you are definitely NOT the authority (IE the DNS servers ns.nucleus.com and ns1.nucleus.com are not the external addresses of your internal DNS server) then forwaders to your ISPs DNS servers will work fine.

You will need to know the IP addresses of your ISP DNS servers (call support or look on their website)

If you don't like the result of this after you have made the change then you can re-create the zone from the original zone file in the \system32\DNS folder on your DNS server as windows doesn't delete old zone files - but you have to make sure the zone isn't AD integrated before you delete it.

Cheers

JamesDS
0
 
tmccabeAuthor Commented:
so how would I add a www entry in a my fbc.internal flz - it will want to list itself as www.fbc.internal
0
 
JamesDSCommented:
tmccabe
The point is, with forwarders you shouldn't need the www entry anywhere as it will already be on the DNS server that is authoritative for the external domain.

Cheers

JamesDS
0
 
tmccabeAuthor Commented:
ah ! of course ! the learning never stops does it
0
 
JamesDSCommented:
tmccabe
hell no !

:)

Cheers

JamesDS
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.