DNS server 2008 not responding new DC
-
Saturday, November 17, 2012 11:06 PM
I just built the first 2008R2 DC for my domain and verified that AD and replication is working fine. However the DNS is not responding to queries. The only DNS that is working in my domain is my old 2003 DC. I have verified that forwarders are setup to my ISP's DNS server. I have run a dnscmd and a netstat -an, results below. I noticed that on the netstat it is listening on 127.0.0.1:53 not the ip of the machine 192.168.10.183. Can anyone help me with this issue. I cannot figure out why it is not responding. All the zones and records are there. Please help.
C:\Users\jimt>dnscmd cifilesvr2 /info
Query result:
Server info
server name = CIFILESVR2.cinet.instruments.com
version = 1DB10106 (6.1 build 7601)
DS container = cn=MicrosoftDNS,cn=System,DC=cinet,DC=instrum
ents,DC=com
forest name = cinet.instruments.com
domain name = cinet.instruments.com
builtin forest partition = ForestDnsZones.cinet.instruments.com
builtin domain partition = DomainDnsZones.cinet.instruments.com
read only DC = 0
last scavenge cycle = not since restart (0)
Configuration:
dwLogLevel = 00000000
dwDebugLevel = 00000000
dwRpcProtocol = 00000005
dwNameCheckFlag = 00000002
cAddressAnswerLimit = 0
dwRecursionRetry = 3
dwRecursionTimeout = 8
dwDsPollingInterval = 180
Configuration Flags:
fBootMethod = 3
fAdminConfigured = 1
fAllowUpdate = 1
fDsAvailable = 1
fAutoReverseZones = 1
fAutoCacheUpdate = 0
fSlave = 0
fNoRecursion = 0
fRoundRobin = 1
fStrictFileParsing = 0
fLooseWildcarding = 0
fBindSecondaries = 0
fWriteAuthorityNs = 0
fLocalNetPriority = 1
Aging Configuration:
ScavengingInterval = 0
DefaultAgingState = 0
DefaultRefreshInterval = 168
DefaultNoRefreshInterval = 168
ServerAddresses:Ptr = 00000000002D4C90
MaxCount = 0
AddrCount = 0ListenAddresses:
NULL IP Array.
Forwarders:Ptr = 00000000002D7A70
MaxCount = 2
AddrCount = 2
Addr[0] => af=2, salen=16, [sub=0, flag=00000000] p=13568, addr=
64.126.4.212
Addr[1] => af=2, salen=16, [sub=0, flag=00000000] p=13568, addr=
64.126.4.216forward timeout = 3
slave = 0
Command completed successfully.
C:\Users\jimt>netstat -an | findstr /i ":53[^0-9].*LIST :53[^0-9].*\*:\*"
TCP 127.0.0.1:53 0.0.0.0:0 LISTENING
TCP [::1]:53 [::]:0 LISTENING
UDP 127.0.0.1:53 *:*
UDP [::1]:53 *:*C:\Users\jimt>
Jim Thomas
All Replies
-
Sunday, November 18, 2012 2:18 AM
Binding order was out of order. Went to the advanced options under network connections, and changed the binding order. DNS server is now responding fine.Jim Thomas
- Marked As Answer by jthomas777 Sunday, November 18, 2012 2:18 AM

