Archer D9 (New) DHCP/DNS not working together..
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer D9 (New) DHCP/DNS not working together..
Model :
Hardware Version : Not Clear
Firmware Version : Latest,
ISP :
I just brought an archer d9, seeing good reviews of this device. Unfortunatly, its making me very unhappy..
Now - I am not an amiture working networks or such by any means so..
Setup the device, internets just fine nice and fast. Setup DHCP with the same net range, noticed that the one important thing is missing - being able to specify host names for mac address, this is a step back for me, anyway continued on..
Now, my network is a number of devices, both wired and un-wired, things like unix desktops and raspberry pi's to the latest sony android TV's, so interoperability is important, thus having DHCP/DNS working properly is important. So
Heres my problem..
The DHCP server is not properly registering the clients into the (internnal) DNS server, thus They can not be looked up..
When doing a lookup on the dns server it comes as refused.
Here is an example, I renew my dhcp and then using nslookup, switch to the server and look my self up..
[CODE] sudo dhclient -vsudo: unable to resolve host gonzalas
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/virbr0-nic/52:54:00:72:ae:e4
Sending on LPF/virbr0-nic/52:54:00:72:ae:e4
Listening on LPF/virbr0/52:54:00:72:ae:e4
Sending on LPF/virbr0/52:54:00:72:ae:e4
Listening on LPF/eth0/94:de:80:b9:bc:75
Sending on LPF/eth0/94:de:80:b9:bc:75
Sending on Socket/fallback
DHCPDISCOVER on virbr0-nic to 255.255.255.255 port 67 interval 3 (xid=0x67089e28)
DHCPDISCOVER on virbr0 to 255.255.255.255 port 67 interval 3 (xid=0x2267fc62)
DHCPREQUEST of 192.168.2.100 on eth0 to 255.255.255.255 port 67 (xid=0x408b18ca)
DHCPNAK from 192.168.2.1 (xid=0xca188b40)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xe3a2611b)
DHCPDISCOVER on virbr0-nic to 255.255.255.255 port 67 interval 5 (xid=0x67089e28)
DHCPDISCOVER on virbr0 to 255.255.255.255 port 67 interval 7 (xid=0x2267fc62)
DHCPREQUEST of 192.168.2.102 on eth0 to 255.255.255.255 port 67 (xid=0x1b61a2e3)
DHCPOFFER of 192.168.2.102 from 192.168.2.1
DHCPACK of 192.168.2.102 from 192.168.2.1
bound to 192.168.2.102 -- renewal in 38086 seconds.
[/CODE]
my hostname is gonzalas
[CODE]
$ nslookup
> server 192.168.2.1
Default server: 192.168.2.1
Address: 192.168.2.1#53
> gonzalas
Server: 192.168.2.1
Address: 192.168.2.1#53
** server can't find gonzalas.local: REFUSED
>
[/CODE]
this is basic network 101 that it should WORK!!!! I am seriously considering returning this device..
Hardware Version : Not Clear
Firmware Version : Latest,
ISP :
I just brought an archer d9, seeing good reviews of this device. Unfortunatly, its making me very unhappy..
Now - I am not an amiture working networks or such by any means so..
Setup the device, internets just fine nice and fast. Setup DHCP with the same net range, noticed that the one important thing is missing - being able to specify host names for mac address, this is a step back for me, anyway continued on..
Now, my network is a number of devices, both wired and un-wired, things like unix desktops and raspberry pi's to the latest sony android TV's, so interoperability is important, thus having DHCP/DNS working properly is important. So
Heres my problem..
The DHCP server is not properly registering the clients into the (internnal) DNS server, thus They can not be looked up..
When doing a lookup on the dns server it comes as refused.
Here is an example, I renew my dhcp and then using nslookup, switch to the server and look my self up..
[CODE] sudo dhclient -vsudo: unable to resolve host gonzalas
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/virbr0-nic/52:54:00:72:ae:e4
Sending on LPF/virbr0-nic/52:54:00:72:ae:e4
Listening on LPF/virbr0/52:54:00:72:ae:e4
Sending on LPF/virbr0/52:54:00:72:ae:e4
Listening on LPF/eth0/94:de:80:b9:bc:75
Sending on LPF/eth0/94:de:80:b9:bc:75
Sending on Socket/fallback
DHCPDISCOVER on virbr0-nic to 255.255.255.255 port 67 interval 3 (xid=0x67089e28)
DHCPDISCOVER on virbr0 to 255.255.255.255 port 67 interval 3 (xid=0x2267fc62)
DHCPREQUEST of 192.168.2.100 on eth0 to 255.255.255.255 port 67 (xid=0x408b18ca)
DHCPNAK from 192.168.2.1 (xid=0xca188b40)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xe3a2611b)
DHCPDISCOVER on virbr0-nic to 255.255.255.255 port 67 interval 5 (xid=0x67089e28)
DHCPDISCOVER on virbr0 to 255.255.255.255 port 67 interval 7 (xid=0x2267fc62)
DHCPREQUEST of 192.168.2.102 on eth0 to 255.255.255.255 port 67 (xid=0x1b61a2e3)
DHCPOFFER of 192.168.2.102 from 192.168.2.1
DHCPACK of 192.168.2.102 from 192.168.2.1
bound to 192.168.2.102 -- renewal in 38086 seconds.
[/CODE]
my hostname is gonzalas
[CODE]
$ nslookup
> server 192.168.2.1
Default server: 192.168.2.1
Address: 192.168.2.1#53
> gonzalas
Server: 192.168.2.1
Address: 192.168.2.1#53
** server can't find gonzalas.local: REFUSED
>
[/CODE]
this is basic network 101 that it should WORK!!!! I am seriously considering returning this device..