Server 2003 DNS Problems -- Internet connection

[phuschnickens]

Server 2003 is DC running AD, DNS, DHCP. The server is able to pass internet connection to other computers, but the server itself has no connection to the internet unless I add my gateway (smoothwall) as an alternate dns server in TCP/IP Properties.

Any ideas?

Thank you.
phu

EDIT: I confirmed that it does have an internet connection but just cannot resolve ip addresses and some extra info... it's not setup as a root server and I do have forwarding enabled in DNS (208.67.222.222, 208.67.220.220).

[kryyst]

You need to have it use itself as primary DNS and then have another DNS as its forwarding DNS server otherwise it can't resolve outside its own network.

[phuschnickens]

Okay... I think that's what I have if I understand correctly... please see attached

[Kwitko]

That looks right.:thumbup

[phuschnickens]

That looks right.:thumbup

Well i guess that's good... but it still doesn't work right :confused2

[kryyst]

Yep looks right. Only things I typically do would be adding 127.0.0.1 a 2ndary dns to your dns settings in your network properties. Also in your dns server properties makes sure that under the interfaces tab it's set to listen on all network devices.

Then you know reboot the server if you haven't done so after making any changes. Also do a couple ipconfig /flushdns if you haven't.

[phuschnickens]

well... i'll give it a shot again when i go home.. with the exception of putting localhost in as the alternate dns, i've restarted quite a bit and used ipconfig /flushdns ... also cleared the cache via dnsmgmt.msc...

[kryyst]

Check the interfaces thing that would cause a break where the DNS server can't listen in on its own interface.

Also check to see if the DNS server can resolve any names for internal devices.

[phuschnickens]

yo.. haven't been home yet, but I was just thinking (usually where the trouble starts) that I have the following set in dhcp under scope options

router 10.0.0.1
dns server 10.0.0.2, 10.0.0.1
lpr servers 10.0.0.3, 10.0.0.4, 10.0.0.5
dns domain name jpresidence.com

Correct me if I'm wrong, but I'm thinking it probably makes a lot more sense to have all of these settings under server options ... like that could explain why the server itself has no internet connection (b/c it's not in the scope of ip addresses that have the "correct" settings) ... although, while I type I theorize that the server should really only get its own internet connection from its own TCP/IP properties, non? I suspect that it shouldn't have to get the info through the dhcp properties.

[Kwitko]

If you're still stuck, check out Daniel Petri's (http://petri.co.il) site for all things Windows admin. He has some great tutorials on setting up DNS in an AD environment.

By the way, what is your FQDN? Generally it's a good idea to use a name that won't conflict with "outside" names. Many people use the companyname.local naming scheme to avoid conflicts.

[Kwitko]

I hope you're not setting the DNS server to use DHCP.

[phuschnickens]

? no it's still static

10.0.0.2
255.255.255.0
10.0.0.1

just adjusting the dhcp properties... moving the settings from scope options to server options

[phuschnickens]

Daniel Petri's (http://petri.co.il) site

That's actually where i learned practically anything i know about this stuff.. but i'll look more closely

and i think i know what you're asking ... FQDN is jpresidence.com

[phuschnickens]

the server CAN resolve internal network devices and the interfaces thing was already set correctly (listening on all ip addresses)

[phuschnickens]

is it okay to add my smoothwall ip address as a forwarder? b/c this configuration works... by simply adding 10.0.0.1 as the first ip to forward to, i have internet connex on my server..

please opine. thx

[kryyst]

yeah nothing wrong with that your smoothwall will resolve so that's all it needs.

[phuschnickens]

yeah nothing wrong with that your smoothwall will resolve so that's all it needs.

beautiful