srv record isnt created

  • Thread starter Thread starter Ric
  • Start date Start date
R

Ric

I used dcpromo to create an AD with first DC and use the
wizard to create DNS service.

After everything done, I check the DNS, under the zone
creates, there is soa, ns and host record, but NO srv
subfolder found.

I try to create the srv manually but can only create _tcp
and _udp subfolders.

1) the srv should be created automatically, what's
possibly wrong on this process for missing srv record?

2) how to create the srv record manaully??

Regards

Ric
 
In
Ric said:
I used dcpromo to create an AD with first DC and use the
wizard to create DNS service.

After everything done, I check the DNS, under the zone
creates, there is soa, ns and host record, but NO srv
subfolder found.

I try to create the srv manually but can only create _tcp
and _udp subfolders.

1) the srv should be created automatically, what's
possibly wrong on this process for missing srv record?

2) how to create the srv record manaully??

Regards

Ric

They are normally done automatically. Look at this repost from a previous
post just the other day that someone else had the same problem:
===========================
These folders are registered by the netlogon service. If they are not
registering, then there is something else going on or a DNS
misconfiguration or both. For proper registration, follow these guidelines:

1. Always only use your internal DNS server in your IP properties of all
internal machines (DCs and clients alike). This means no ISP's DNS server
addresses. For efficient Internet resolution, configure a Forwarder. If the
Forwarding option is grayed out, delete the Root zone. Follow this to show
you how to do both:
http://support.microsoft.com/?id=300202

2. The Primary DNS suffix should be set the same as the DNS domain name of
your domain. Netlogon uses that name to register.

3. The name of the zone in DNS must be spelled the same as the Primary DNS
Suffix on your machines.

4. The Active DIrectory DNS domain name (as seen in ADUC) must be the
spelled the same as the Primary DNS Suffix and the zone name in DNS.

5. You don't have a single label domain name. It should be in the form of
domain.com and not just "domain".

6. Updates are set to at least YES in the zone's properties.
===========================

Hope that helps.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
thx Ace.

But i know it should be created automatically, but now
it's not....what would be the remedy other than demote and
promote the DC again?

Ric
 
In
Ric said:
thx Ace.

But i know it should be created automatically, but now
it's not....what would be the remedy other than demote and
promote the DC again?

Ric


If this is the case Ric, you won;t even be able to demote it without forcing
it since the SRVs don't exist and that's what everything in AD looks for to
function. You may just reinstall it, make the same configuration and be in
the same spot again. I'm really trying to help you out, but need some info,
such as if the guidelines helped. Also, please post an unedited ipconfig
/all for us to get a better view of your configuration too. That will give
us a good start.

Getting aback to the guidelines, did you follow those 6 guidelines? Does
everything match up? Please, I would like you to comments on them so I know
if you followed them. Was there anything amiss based on the guidelines? Are
you using your ISP's DNS in your IP properties? Is your domain a single
label name? Updates set to yes? Zone name spelled exactly the same in these
3 places: Primary DNS Suffix, AD name and the zone name? etc. Updates set to
yes?? These are all the basics. If all this is good, then it just works and
they reg automatically.

Here are the guidelines again. Please do comment on each one individually by
responding to each one inline. This will really help us in determining where
the problem is to get you going again.

1. Always only use your internal DNS server in your IP properties of all
internal machines (DCs and clients alike). This means no ISP's DNS server
addresses. For efficient Internet resolution, configure a Forwarder. If the
Forwarding option is grayed out, delete the Root zone. Follow this to show
you how to do both:
http://support.microsoft.com/?id=300202

2. The Primary DNS suffix should be set the same as the DNS domain name of
your domain. Netlogon uses that name to register.

3. The name of the zone in DNS must be spelled the same as the Primary DNS
Suffix on your machines.

4. The Active DIrectory DNS domain name (as seen in ADUC) must be the
spelled the same as the Primary DNS Suffix and the zone name in DNS.

5. You don't have a single label domain name. It should be in the form of
domain.com and not just "domain".

6. Updates are set to at least YES in the zone's properties.
--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
thx again Ace

I really appreciate your kindness and knowledgible reply
which come with all necessary details....

Actually i have been working on this matter couples hours
checking everything including those you listed and also
some online checklist ...

Finally I used another server and do the same process
again ( strat from DCPROMO..) actually i m not new in this
process...

Very surprising the same result, no srv record
again...then i re do the check...try to remove the dns
domain and re create..nothing work..

when i check ipcofig/all.......haha...the point is
here............the primary dns server is wrongfully
pointed to the default gateway..

now passing thru this process, I learn a lot ...the point
is, I think I m familiar with the process , so ignore some
minor details....


Ric
 
Well, glad to hear you discovered it was the wrong DNS address listed. When
you previously posted, I didn't know if you went thru checking the details
or not, hence why I responded so. Get alot of posters giving minimal details
which makes it hard to fathom what's going. Forgive me if it seemed to
obnoxious, but I was trying to push a point with not knowing whether you
checked or even familiar with the process. Glad to see you are familiar,
makes things easier.

If you have any other probs, please do post back.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top