cancel
Showing results for 
Search instead for 
Did you mean: 

Active Directory Domain not resolving on wired connections

incito
Newbie
Posts: 3
Registered: 29-01-2014

Active Directory Domain not resolving on wired connections

I am having problems resolving my local servers domain controllers domain name from any wired connections to our Plusnet Technicolor TG582n router.
I have a windows server 2012 on my local network serving DHCP, DNS, Active Directory.
I have dissabled DHCP on the router and all client machines are correctly recieving their IPs from the server not the router.
All client machines are configured to use the server as the DNS server not the router.
However when i try to join the domain from any of the client machines that are wired to the router, it fails to resolve the domain name. Doing an NS lookup on the domain name from the client machine shows that they are using the routers DNS to try and resolve this which im not sure why as the network cards on the machines are set up to use the server as the DNS server not the router.
If however i connect wirelessly to the network, then i can join the domain successfully and resolve the domain name.
Does anyone have any ideas why this is or is there a way to turn off the DNS from teh router which is overriding the client machine configurations?
Thanks
5 REPLIES
Community Veteran
Posts: 26,543
Thanks: 786
Fixes: 9
Registered: 10-04-2007

Re: Active Directory Domain not resolving on wired connections

Could you post an
ipconfig /all 
from one of the failing PCs.
jelv (a.k.a Spoon Whittler)
   Why I have left Plusnet (warning: long post!)   
Broadband: Andrews & Arnold Home::1 (FTTC 80/20)
Line rental: Pulse 8 Home Line Rental (£13/month)
Mobile: iD mobile (£4/month)
incito
Newbie
Posts: 3
Registered: 29-01-2014

Re: Active Directory Domain not resolving on wired connections

C:\Users\Incito>ipconfig /all
Windows IP Configuration
  Host Name . . . . . . . . . . . . : INCITO-003
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : INCITO.LOCAL
Ethernet adapter Ethernet:
  Connection-specific DNS Suffix  . : INCITO.LOCAL
  Description . . . . . . . . . . . : Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30)
  Physical Address. . . . . . . . . : 50-E5-49-19-9F-F8
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::dda2:c11c:361e:c669%3(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : 29 January 2014 12:15:11
  Lease Expires . . . . . . . . . . : 06 February 2014 12:15:10
  Default Gateway . . . . . . . . . : 192.168.1.254
  DHCP Server . . . . . . . . . . . : 192.168.1.83
  DHCPv6 IAID . . . . . . . . . . . : 55633225
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6E-F2-9A-50-E5-49-19-9F-F8
  DNS Servers . . . . . . . . . . . : fe80::9e97:26ff:fe0b:a8e1%3
                                      192.168.1.83
  NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:200f:145f:3f57:fe98(Preferred)
  Link-local IPv6 Address . . . . . : fe80::200f:145f:3f57:fe98%5(Preferred)
  Default Gateway . . . . . . . . . : ::
  DHCPv6 IAID . . . . . . . . . . . : 134217728
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-6E-F2-9A-50-E5-49-19-9F-F8
  NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.INCITO.LOCAL:
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : INCITO.LOCAL
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

C:\Users\Incito>nslookup incito.local
Server:  dsldevice.lan
Address:  fe80::9e97:26ff:fe0b:a8e1
*** dsldevice.lan can't find incito.local: Non-existent domain
C:\Users\Incito>
Community Veteran
Posts: 26,543
Thanks: 786
Fixes: 9
Registered: 10-04-2007

Re: Active Directory Domain not resolving on wired connections

That looks like it might be a IPv4/IPv6 issue.
Is your server allocating IPv6 addresses? What happens if you go in to the properties of the Local Area Connection and change the IPv6 Properties to specify the server's IPv6 address as the DNS server?
Alternatively, you could try disabling IPv6 on the Pc to see if that sorts it out.
jelv (a.k.a Spoon Whittler)
   Why I have left Plusnet (warning: long post!)   
Broadband: Andrews & Arnold Home::1 (FTTC 80/20)
Line rental: Pulse 8 Home Line Rental (£13/month)
Mobile: iD mobile (£4/month)
pwatson
Rising Star
Posts: 2,468
Thanks: 8
Fixes: 1
Registered: 26-11-2012

Re: Active Directory Domain not resolving on wired connections

What's the IPv6 address of the server PC?  It looks like the client PC is possibly set to use the router DNS via IPv6 and the server via IPv4?
incito
Newbie
Posts: 3
Registered: 29-01-2014

Re: Active Directory Domain not resolving on wired connections

I disabled IPv6 on the client machines and it now resolves correctly, so it looks like that was the problem.
Thanks for all the help