DNS & DC

http://www.winnetmag.com/Windows/Article/ArticleID/39651/39651.html
Try this.

Also, have your tryed setting the external DNS IPs on the server connection?

run netdiag /fix

Tried netdiag /fix

this is what I received.  I think I have things setup in DNS incorrectly but not sure how to fix it....

[Warning] cannot find a primary authoriative DNS server for the name server.weston. [rcode_server_failure] the name server.weston. may not be registered in DNS

Failed to fix: DC DNS entry weston. re-registeration on DNS server 192.168.0.3 failed

netdiag failed to re-register missing DNS entries for theis DC on DNS server 192.168.0.3
no DNS servers have the DNS records for this DC registered.

I also already checked the queue folder for bad emails and there aren't any in that folder.

Check for the following dns srv records in your dns! There must be all of them! Check this link:
http://www.petri.co.il/active_directory_srv_records.htm

Instead of netdiag /fix, try also dcdiag /fix.

Cheers.

first off, the server needs to have the internal dns server in its first dns spot.  that is usually its self if the server is also the dns server..  ie if the server is 192.168.1.101 then the first dns entry on the server would be the same.  the seccond and third dns entrys can be your real dns servers on internet land.  this is also true on the workstations.  the first would be the server (192.168.1.101 in my example) the seccond and third wouldl be the true one.  when you run netdiag again you should get a pass on itself (registration wise), but a failure on the true dns server (one on internet )  ignore that one.

seccond you may need to do the followin to re-register the dns crap on the server.  try it without dooing this, but you may need to.  

ipconfig /flushdns
ipconfig /registerdns
net stop netlogon
net start netlogon

you didnt mention if the netdiag came back with a failure on the dns portion, but im guessing it did.  if this dosent fix the netdiag failure we go to the next step.  also, when the server boots, does it take a long time on the "prepairing network connections"?

-dp

THis is how I have everything set up..... I'm not using DHCP everything is static on the network

ip 192.168.0.3
default gateway 192.168.0.1
preferred DNS 192.168.0.3
Alternate DNS 192.168.0.2  --------- this is the ip address of our second server

computer name server.weston
domain weston

I created forward and reverse lookups
standard primary
name = weston
            weston.dns
primary server = server.weston.
responsible person = admin.weston.

name server = server.weston 192.168.0.3

allow zone transfers to any server

main dns server is listening on all ip addresses
enabled forwarders to ip address 4.2.2.2

(did i set this up correctly)

I do a nslookup and get this error
can't find server name for address 192.168.0.3: non-existent domain
can't find server name for address 192.168.0.2: no response from server

default servers are not available
default server: unknown
address: 192.168.0.3

if I do a ls weston

ls weston
[unknown]
weston.        NS        server = server.weston
server          A          192.168.0.3


My internet works for now, but i'm having email problems getting errors unable to biind to dns of destination....

If I do a netdiag /v I get a dns error  (DNS entries for this DC are not registered correctly on DNS server 192.168.0.3)
no DNS servers have the DNS records for this DC registered


Thats the whole problem and all the setting I have currently....
Thanks

your correct on your first dns entry, thats your dns server (itself) the seccond one should be your real dns server (i.e. 207.155.183.72).  if that still gives you errors, you may have to do the following again....
ipconfig /flushdns
ipconfig /registerdns
net stop netlogon
net start netlogon

if no go then, toasting the dns and re adding it will surely fix you up.  below is the simiplified path...  \


good luck...


Just don't restart your DC during this please.

•      Delete your zone off the DNS server that you picked.
•      If the zone is AD integrated, make it a Primary
•      Goto winnt\system32\dns) and delete your zone.dns files and delete the one in the backup folder too
•      Delete the NETLOGON.DNS and NETLOGON.DNB files from winnt\system32\config
•      In the reg, HKLM\system\CurrentControlSet\Services\DNS\Zones, delete your zone's
•      folder
•      Reinstall DNS
•      Reinstall your current service pack.
•      Now recreate the zone in DNS
•      Enable Dynamic Updates to "YES" and not to Secure just yet.
•      ipconfig /flushdns
•      ipconfig /registerdns1
•      Stop and Restart NETLOGON (net stop netlogon – net start netlogon)

dan

You mention using ipconfig/flushdns

I'm not runing DHCP I believe that is used only when using DHCP

Everything is static on our network

if i'm incorrect let me know thanks

no, the flush is for the dns, not dhcp.  when you do a registerdns it re-registeres it self anyway.  

release renew is dncp crap.

-dp

good luck

Your server should not be server.weston.  as you stated (or was the trailing period meant as punctiuation to your sentance?) there should be a TLD listed. personally i use .local which would make your DC server.weston.local

can't find server name for address 192.168.0.3: non-existent domain       > This error has to do with a failure in reverse DNS of your 1st server
can't find server name for address 192.168.0.2: no response from server > This error says that your 2nd server isn't running DNS
responsible person = admin.weston.                                                      > This isn't valid. The 1st . is an @ from the email of the responsible person: admin@weston.
                                                                                                          > isn't a valid e-mail address. not critical but shows underlying problems.


I'd say your problems stem from failure during the DCPROMO process. when the domain controller was promoted from a member server to a DC it was most likely configured to point to somewhere else for its DNS services and thus didn't make the registration for advanced windows services in its own DNS records. this is also why the clients are unable to find a domain controller to process their logons from your previous thread. Additionally your domain name doesn't comply with standards, it is missing the TLD information after the last period. that's definately not helping you either. I'd say some rather drastic measures should be taken, depending on your environment and what maintenance windows are available and how long they are you should pursue fixing your domain name first. I can't say that that is what is causing your problems because i've not ever made a domain without a TLD of some sort - like I said, I usually use .local

http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx is the link to microsoft's How-to on renaming the domain.

I agree with the fact that things were set up incorrectly initally, is it possible to rename everything with an already established network without running into other problems

also that link is for windows server 2003 i'm running server 2000  will the same steps apply?

Thanks

Sorry i thought you'd said 2003 DC somewhere. You can't rename a 2000 domain. unfortunately. Your problem just compounded by about 3 fold. Give me and the rest a little bit to ponder how to fix this without just scrapping the whole domain and moving all the client PCs to a new domain (2003 SBS server costs less than $2K including hardware...) and setting your current servers up as members of that new SBS 2003 domain.

Ok Thanks for your help