DNS failure in SBS 2008

I have a brand new SBS 2008 server that is having some DNS problems that I have been unable to resolve.

Symptoms:  
Domain member PCs cannot ping the server by its FQDN, and a ping -a against the server IP returns no server name.  

An nslookup on the local domain name returns an error stating "Can't find server name fro address 192.168.1.2: Timed Out

In the DNS event log on the server itself I have multiple event ID 800's stating "The zone domain.local is configured to accept updates but the A record for the primary server in the zone's SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot  be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates"

An nslookup on the server itself returns
C:\Users\Administrator>nslookup domain.local
Server:  UnKnown
Address:  ::1

Name:    domain.local
Address:  192.168.1.2

On the server a ping against server.domain.local returns the IPv6 address.


At this point I've verified that the forward and reverse lookup zones are both created and that the SOA and NS records for both are correct.  The SOA is server.domain.local, and an A record exists resolving that to 192.168.1.2.  The PTR record for that entry is also in existence.  I've also run the Fix My Network Wizard, and the only DNS related issue it shows is that there is a forwarder configured.  Any help on this would be greatly appreciated.  Thanks!
JenlorAsked:
Who is Participating?
 
JenlorConnect With a Mentor Author Commented:
Thanks to all for the help.  I was able to resolve the issue by manually recreating both the forward and reverse lookup zones, establishing the correct SOA and NS entries, and then restarting the DNS Server service.  Nslookups on the client PCs now return the proper information, the machines can ping the server by its FQDN, and the client machines are successfully registering in DNS.
0
 
Darius GhassemCommented:
Make sure you are only pointing to the server to itself for DNS only.
0
 
giltjrCommented:
What is  the host name you have on your SOA record?

Do you actually have a A record for that name?
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
JenlorAuthor Commented:
ipconfig /all on the server shows only it's IPv4 and V6 addresses as DNS servers.
0
 
Darius GhassemCommented:
When you run dcdiag what errors do you get? What zones do you have aviable in DNS?
0
 
JenlorAuthor Commented:
The host name under Primary Server in the SOA properties for the domain.local domain is server.domain.local.  There is an A record in the domain.local forward lookup zone resolving server.domain.local to 192.168.1.2.  In the reverse lookup zone 1.168.192.in-addr.arpa there is a PTR record pointing 192.168.1.2 to server.domain.local.
0
 
Darius GhassemCommented:
Post ipconfig /all for server and client. Make sure clients are pointing to this SBS server only for DNS.
0
 
JenlorAuthor Commented:
All tests passed in a dcdiag.  Zones available are:

forward:
_msdcs.domain.local
domain.local

reverse:
1.168.192.in-addr.arpa
0
 
JenlorAuthor Commented:
All clients are configured via DHCP and are looking only to 192.168.1.2 (server IP).
0
 
Darius GhassemCommented:
Do you have 2 NICs? Disable the second NIC.
0
 
giltjrCommented:
From the server itself can you do nslookup against itself?
0
 
JenlorAuthor Commented:
All NICs but the one in use are already disabled.  I've considered disabling IPv6 (and doing it the right way), but I'd rather not go that route if I don't have to.
0
 
Nicholas IlerIT Technical EngineerCommented:
Hi,
  • Did you set static properties on your SBS 2008 IPv4 NIC and set primary DNS to 127.0.0.1?
  • Did you set member systems primary DNS to 192.168.1.2? (Group Policy is great for this)
  • Do you see automatic DNS entries for member systems in your DNS?
  • Do you get a ping response back when you ping IP's?
Nick
0
 
JenlorAuthor Commented:
nslookup domain.local done on the server itself returns:

Server:  Unknown
Address:  ::!

Name:  domain.local
Address:  192.168.1.2
0
 
JenlorAuthor Commented:
Nick,

1) Primary DNS on the server NIC is set to 192.168.1.2
2) Member systems primary DNS is set to 192.168.1.2 (via DHCP)
3) DNS entries are not being registered for member systems
4) Pinging any IP that is in use from the server or any workstation is successful
0
 
Nicholas IlerIT Technical EngineerCommented:
When you setup the DNS server did you set it to use IPv6?
If so then you may need to re-install your DNS server with IPv4.  I have setup and managed Windows Server 2003-2008 domains and always set the DNS to use IPv4.  
Nick
0
 
JenlorAuthor Commented:
In the DNS server properties it's set to listen on both the IPv4 and IPv6 addresses.  Is that where you're talking about for the DNS set up?
0
 
Todd GerbertIT ConsultantCommented:
Are your DNS zones configured to allow updates?
Do you have reverse lookup zones?
0
 
Nicholas IlerIT Technical EngineerCommented:
I have not run SBS server.  Did the DNS and Domain Controller roles install automatically or did you configure after OS install?  
When I setup Enterprise server I get options at the beginning of setting up the Domain Controller role.  It will install the DNS role along with the Domain role.  During this install there is a question which involved a selection of IPv4 or IPv6.  
Nick
0
 
JenlorAuthor Commented:
Nick,
  The SBS 2008 install handled the DNS role setup.

0
 
Nicholas IlerIT Technical EngineerCommented:
Just thought of something.  You don't happen to have a router on your network with DHCP and DNS enabled do you?
This may cause your DNS not to fill up and will cause other strange problems.  If you do try disabling DHCP and DNS on the router.  It may require other settings as well but I have my Domain Controller handle all DHCP and DNS request inside and forward all other request to my ISP's DNS.
Nick
0
 
Hypercat (Deb)Commented:
I had the same problem with one of the SBS 2008 servers I have set up. It was a situation where the workstations had previously been connected to an older SBS 2003 server and I was in the process of replacing it with a new SBS 2008 server (not a migration). It was pretty weird, but all I did was disable IPv6, make sure that all of my workstations had updated their IP addresses (you could force this with ipconfig /renew or a reboot if you don't have too many workstations), and then re-enabled IPv6.  I still don't know why this actually happened, but the workstations were XP and I guessed that perhaps they were somehow having problems communicating with the DNS and/or DHCP services on the server because IPv6 was running. Once their connections got established, the problem has not recurred.
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.