asked on

DNS Setting for Domain controller

Have a small domain and needed a hurry up domain controller installed.

Running well enough but routinely run into issues with public and domain name resolution.

I'm sure I never set the forwarding for the public DNS on the controller right. Any good checklist reviews for verifying my set up and what i may have done wrong/missed?

This is a Windowss 2008 server...

gurutc

Hi,

Which computers are having the public/private issues? The client pcs? the server? Are you using DHCP coming from the Domain Controller?

- gurutc

VirtualKansas

ASKER

The client PC's. It's been nearly a year since I set up this network, so not positive where DHCP is, but it appears its not on the DC.

This is a really strange network because we have field offices that are tunnel VPN'ed to HQ and really strange in that no one is really ever in the HQ office. So field offices come & go and there is a lot of tunnel and other VPN that consumes these services.

VirtualKansas

ASKER

I think I may simply failed to take the time to set up forwarders in the DNS of the DC's for public name resolution. Chicken & egg problem; field offices got set up before there was ever a domain.

gurutc

deal, nothing configured on the adapters for public resolution, right?

sounds like you're ciphered.

- gurutc

VirtualKansas

ASKER

OK; I'm at HQ office in proximity of a back up DC. The primary believe it or not is in a field office. The back up DC is set for primary DNS as a loop back and secondary as the PDC. No public DNS on this adapter.

VirtualKansas

ASKER

OK; checked PDC and same. 1st lookup is self, 2nd is another DC.

gurutc

yes sometimes that'll do the trick if you've got a public DNS anywhere.

- gurutc

VirtualKansas

ASKER

don't think i have a public dns anywhere

VirtualKansas

ASKER

so kind of jack of all master of none, here; do i need to add a forwarder for public dns? is that my loose end?

VirtualKansas